Zone 5 Technologies
Embedded Software Engineer V/VI
About this role
Zone 5 Technologies seeks an experienced Embedded Software Engineer to design and implement software for unmanned aircraft systems, including microcontroller firmware, sensor integration, and flight-testing of autonomous platforms. This senior-level role involves leading new projects while debugging complex systems and collaborating across engineering teams.
What you'll do
- Design, code, and implement embedded software for microcontrollers on unmanned aircraft
- Conduct flight testing and validation of embedded systems in real-world environments
- Develop and test software for sensor and processor integration (autopilots, payloads, radios, etc.)
- Lead development planning and execution of new projects and programs
- Debug, troubleshoot, and isolate software issues in UAS platforms
- Collaborate with cross-functional engineering teams on autonomous solutions
What they're looking for
- Embedded C/C++ programming
- Microcontroller development and firmware
- UAS/UAV software systems
- Real-time systems and embedded OS
- Hardware integration and sensor communication
- Flight testing and validation
- Software debugging and diagnostics
- Technical leadership and project planning
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.
Zone 5 Technologies
Zone 5 Technologies designs and manufactures unmanned aircraft systems and UAVs, focusing on advanced avionics integration and autonomous flight technologies. The company is hiring Systems Integration & Test Engineers, Systems Engineers, and Continuous Improvement Engineers to develop Hardware-in-the-Loop environments, optimize manufacturing processes, and validate next-generation unmanned aircraft systems.
View all jobs at Zone 5 TechnologiesLikely interview questions
- Describe your experience developing firmware for embedded microcontrollers in aerospace or autonomous systems applications.
- Walk us through a complex embedded software issue you debugged in a flight or real-world environment—what was your approach?