Anduril Industries
Firmware Engineer
About this role
Anduril Industries seeks a Firmware Engineer to develop low-level embedded software for defense platforms including microcontroller firmware, test procedures, and hardware-firmware integration. You'll work with senior engineers on products spanning prototype to production stages, leveraging C and debugging expertise in a fast-paced environment.
What you'll do
- Develop low-level firmware in C for microcontrollers across multiple defense product platforms
- Write and execute test procedures that verify firmware behavior against requirements
- Debug and troubleshoot issues spanning electrical, firmware, and software boundaries
- Support board bring-up and hardware-firmware integration with cross-functional teams
- Maintain requirements traceability to ensure test coverage for all requirements
- Contribute to projects at various stages from prototype through production
What they're looking for
- C firmware development for embedded systems
- Common bus protocols (SPI, I2C, UART, CAN)
- Board bring-up and hardware debugging
- Test procedure development and execution
- Microcontroller architecture (ARM, AVR, MSP430, or PIC preferred)
- Embedded systems problem-solving
- Requirements traceability and verification
- Cross-functional communication and collaboration
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.
Anduril Industries
Anduril Industries builds autonomous defense systems including underwater vehicles, unmanned aircraft, and electronic warfare platforms for the Department of Defense. The company is hiring across mechanical engineering, mission operations, software development, technical leadership, and advanced manufacturing roles to support the design, deployment, and production of these mission-critical systems.
- Website
- anduril.com
Likely interview questions
- Walk us through a recent firmware project where you debugged an issue at the hardware-firmware boundary—what tools and approach did you use?
- Describe your experience with board bring-up: what steps do you typically take to verify initial hardware-firmware integration?