Skip to main content

Mach Industries

Firmware Engineer

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

About this role

Mach Industries is seeking a Firmware Engineer to contribute to the development of embedded systems for autonomous defense applications. The ideal candidate will have a strong background in embedded software, particularly within aerospace, and a commitment to quality and innovation.

What you'll do

  • Design firmware for embedded systems in weapon applications
  • Prototype and test firmware for system integration and performance
  • Implement control algorithms for system functionality
  • Collaborate with teams for seamless design integration
  • Ensure quality compliance of software designs
  • Maintain documentation of software protocols and designs

What they're looking for

  • C/C++/Rust programming skills
  • Experience with embedded systems
  • Proficiency in RTOS usage
  • Knowledge of hardware integration
  • Strong problem-solving abilities
  • Familiarity with software development life cycle
  • Understanding of communication protocols like SPI, I2C, UART
  • Ability to work on-site in Huntington Beach, CA
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 a specific embedded systems project you developed for aerospace applications. What was your role, and what challenges did you encounter with firmware reliability or real-time constraints?
  • Describe your experience with RTOS. Which RTOS have you worked with, and how did you handle task scheduling and synchronization in a time-critical embedded system?