Skip to main content

Mach Industries

Firmware Validation Engineer

Huntington Beach, CA$125k–$220kfulltimemidAdded 1 month ago

About this role

Mach Industries is seeking a Firmware Validation Engineer to ensure high-quality firmware for autonomous defense technology. The role involves testing individual components and systems, collaborating with various engineering teams, and improving validation tools.

What you'll do

  • Collaborate with Firmware and Avionics Engineers for firmware quality.
  • Design and execute comprehensive test specifications.
  • Develop Software-in-the-Loop (SITL) and Hardware-in-the-Loop (HITL) tests.
  • Execute tests and troubleshoot issues found during testing.
  • Investigate issues identified in test flight operations.
  • Enhance validation tools and processes.

What they're looking for

  • Degree in Electrical Engineering or related field.
  • Strong electrical engineering fundamentals.
  • Proficiency in Python and C.
  • Knowledge of C++ (preferred).
  • Experience with embedded GPU platforms.
  • Familiarity with Embedded Linux.
  • Experience with ARM systems.
  • Knowledge of defense industry firmware.

Benefits

  • Health insurance
  • Retirement plans
  • Professional development opportunities
  • Equity grants
  • [Unknown]
  • [Unknown]
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 designing and executing firmware validation test specifications, from the design phase through manufacturing. How do you approach testing both nominal and fault-injection scenarios?
  • Describe your experience with Software-in-the-Loop (SITL) and Hardware-in-the-Loop (HITL) simulation environments. What tools have you used, and how have you developed test scenarios in these frameworks?