Skip to main content

SpaceX

New Graduate Engineer, Software (Starship)

Hawthorne, CA$125k–$150kentryAdded 3 days ago

About this role

SpaceX seeks a new graduate software engineer to develop flight control and simulation software for Starship, the world's most powerful reusable launch vehicle. You'll design reliable autonomous systems across all software layers—from firmware to application—while collaborating with hardware and software teams to advance humanity's mission to Mars.

What you'll do

  • Design, develop, and test flight control and simulation software for Starship systems
  • Own complete software development lifecycle including design, testing, and mission integration
  • Debug and implement software across application, OS, networking, firmware, and simulation layers
  • Collaborate with hardware and software engineering teams on launch and vehicle software
  • Solve previously unsolved technical problems under rapid development timelines
  • Validate autonomous systems through rigorous simulation and testing

What they're looking for

  • C++ or Rust programming
  • Systems-level software development
  • Autonomous systems design
  • Software testing and validation
  • Real-time systems
  • Flight software development
  • Problem-solving and debugging
  • Cross-functional collaboration
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

SpaceX

SpaceX develops advanced spacecraft and satellite systems, including the Starshield government satellite constellation and Starfall re-entry cargo capsule for global delivery. The company is hiring engineers in avionics integration, software test automation, mechanical design, and hardware reliability to validate flight-critical systems and ensure mission success.

Website
spacex.com
View all jobs at SpaceX

Likely interview questions

  • Walk us through a complex software debugging challenge you've faced—how did you approach it?
  • Tell us about a time you had to work across teams with different technical expertise. How did you communicate?