Propulsion Design Reliability Engineer

About this role

Vast seeks a Propulsion Design Reliability Engineer to ensure Haven-1's propulsion system is designed and validated for safe, reliable human spaceflight. You'll integrate reliability engineering into the design process, lead FMEA efforts, oversee verification and validation, and guide teams from detailed design through testing and operational readiness.

What you'll do

• Lead Failure Modes and Effects Analysis (FMEA) and drive design reliability integration for propulsion systems
• Guide test plan definition and review verification & validation data to prevent failures before manufacturing
• Conduct technical reviews of mechanical designs, manufacturing drawings, and test campaigns at design gates
• Develop propulsion engineering standards, design guides, and review frameworks for the organization
• Architect design criteria and verification approaches supporting Haven-1's propulsion architecture
• Collaborate with hardware teams to ensure build practices align with design intent and analyze field data for robustness improvements

What they're looking for

• Propulsion system design and analysis
• Failure Modes and Effects Analysis (FMEA)
• Mechanical design and thermal/vibration/combustion analysis
• Test planning and verification & validation methodology
• Human-rated spacecraft reliability standards
• Technical review and design governance
• Cross-functional team leadership
• Engineering standards and documentation development

Benefits

• Work on humanity's first commercial human-rated space station
• Lead cutting-edge propulsion design for next-generation space infrastructure
• Collaborate with talented aerospace professionals
• Full-time, exempt position
• Located in Long Beach, California
• Opportunity to shape engineering standards and best practices at scale

Likely interview questions

• Describe your experience developing and implementing FMEA for critical propulsion or aerospace systems—what was your role in translating findings into design changes?
• How have you balanced rapid development timelines with the rigor required for human-rated systems?