Skip to main content

Mach Industries

Propulsion Test Engineer

Victorville, CA$80k–$170kfulltimemidAdded 1 month ago

About this role

Mach Industries is in search of a Propulsion Test Engineer to lead efforts in testing advanced propulsion systems for defense applications. This role involves designing test setups, executing testing campaigns, and analyzing performance data to ensure reliability under extreme conditions.

What you'll do

  • Design and maintain propulsion test stands and infrastructure
  • Lead test campaigns for various propulsion components and systems
  • Analyze test data for performance validation
  • Ensure safety compliance during hazardous operations

What they're looking for

  • 3+ years in propulsion or aerospace testing
  • Experience with mechanical and fluid systems
  • Ability to read technical drawings and schematics
  • Hands-on experience with shop and diagnostic tools
  • Strong troubleshooting and systems-thinking skills
  • Willingness to support extended hours and travel

Benefits

  • Opportunity to work in a fast-growing company
  • Contributions to national security initiatives
  • Potential for professional development and learning
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.

Mach Industries

Mach Industries is a defense technology startup developing autonomous defense systems and advanced propulsion technologies requiring precision manufacturing at scale. The company is hiring engineers across manufacturing (CNC tooling, automation), propulsion (controls), thermal management, and software to build mission-critical systems.

View all jobs at Mach Industries

Likely interview questions

  • Walk us through your experience with propulsion hardware or aerospace testing—what systems have you worked with, and what was your specific role in test execution?
  • Describe a time when you identified and resolved a critical issue during test operations. How did you troubleshoot it, and what was the outcome?