Senior Embedded Software Engineer

Required Qualifications

• Bachelor's in Electrical Engineering, Computer Science, or equivalent hands-on experience

• 8+ years of hands-on embedded software or firmware development, including ownership of the architecture for at least one product or subsystem that shipped and operated in the field

• Demonstrated technical leadership: leading small engineering teams, mentoring other engineers, and owning cross-discipline technical decisions

• Experience coordinating technical work across multiple teams (for example embedded, ground or cloud software, and integration/test), with a track record of aligning teams on shared interfaces and understanding how embedded design decisions affect the end-to-end system

• Systems-level thinking: you can trace how a change in firmware ripples through ground software, test, and operations, and you raise those impacts before they become surprises

• Strong C, and C++ where it fits, in resource-constrained and real-time environments

• Deep comfort working directly against hardware: reading schematics and datasheets, using JTAG debuggers, oscilloscopes, and logic analyzers, leading board bring-up, and reasoning about what the silicon is actually doing

• Production experience with both embedded Linux and bare-metal or RTOS firmware on microcontrollers

• Experience with, or a demonstrated ability to ramp quickly on, one or more of: Zynq UltraScale+ with Yocto-based embedded Linux, TI C2000 bare-metal firmware, and Verilog FPGA development for Xilinx and Microchip parts

• Experience building the tooling around embedded software: build systems, CI, hardware-in-the-loop test benches, and automated regression

• Hands-on experience driving development with AI coding agents, with the agent doing most of the day-to-day implementation. You should be able to show us work where you set the requirements, reviewed what the agent produced, and owned the result, tell us where you stopped trusting it and why, and describe how you would set up that workflow for a team

• Comfortable with ambiguity. Much of this work is new, specifications are incomplete, and the right answer is often found by building something and testing it

• Strong problem-solving and communication skills, with the ability to convey technical information and tradeoffs clearly to both technical and non-technical stakeholders

• Collaborative team player who thrives in a fast-paced, agile environment

• Authorized to work as a U.S. Person