This role is designed for a versatile robotics engineer who can work across our entire software stack and make it better. This is a deliberately broad role. One week, you might be standing up a new piece of middleware infrastructure; the next, porting a perception component onto an accelerated runtime; the next, automating a calibration workflow that used to consume a day of manual effort. The unifying thread is not a single domain, but range: the ability to drop into an unfamiliar corner of the system, understand it quickly, and leave it better than you found it. Robotics software cannot be written well in isolation from the machine it runs on. We expect you to be comfortable working hands-on with real hardware, bringing up, instrumenting, testing, and debugging your software against the physical system rather than only in simulation. Much of that happens in the field. This role carries real ownership of work at our flight tests, where software meets reality at full speed and the most stubborn problems surface. You do not need to be a mechanical or electrical designer, but you do need the practical fluency to work through problems that span the hardware and software boundary, where the toughest robotics bugs tend to live. Just as important is perspective. We want someone who will look critically at how our systems are built, software and hardware alike, and surface the improvements we have not thought to make ourselves. A sharp, motivated engineer with fresh eyes often sees what a team too close to its own work has stopped noticing, and we want to hear it. This is a generalist role by design. Depth in a robotics specialty such as state estimation, controls, or perception is a welcome bonus, but it is not what we are screening for. We are looking for breadth, sound engineering judgment, and the drive to make a complex robotic system work better wherever you are pointed.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Mid Level