Skip to main content

SpaceX

Software Engineer (Flight Reliability)

Starbase, TXmidAdded today

About this role

SpaceX seeks a Software Engineer for Flight Reliability to develop mission-critical applications supporting launch vehicle production, flight operations, and Starlink infrastructure. You'll own full-stack projects with direct impact on launch success, working collaboratively to solve complex technical problems at scale.

What you'll do

  • Develop highly reliable, mission-critical software used across SpaceX operations
  • Design and build new applications to improve SpaceX operational efficiency
  • Create prototypes to validate design concepts and measure technical constraints
  • Take end-to-end ownership of software engineering and product development
  • Analyze user problems deeply to architect efficient solutions
  • Participate in team architecture reviews, design discussions, and code reviews

What they're looking for

  • Full-stack software development
  • Object-oriented programming (Python, C#.NET, Go, Scala, or Java)
  • Single-page application development (Angular or React)
  • Version control and CI/CD practices
  • Software systems design and architecture
  • Application performance profiling and optimization
  • Docker containerization
  • Database design (PostgreSQL or SQL Server)
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

  • Describe your experience building and maintaining full-stack applications in production environments.
  • Tell us about a time you owned a challenging software problem end-to-end—what was your approach to architecture and design?