Principal, Robotics Software Engineer

- 10+ years of robotics software engineering with real shipped systems behind you

- Senior IC track record at robotics companies that actually shipped to customers or operators

- Deep ROS2 experience and the judgment to know when not to use it

- Track record building and operating CI/CD for robotics or hardware-in-the-loop

- Experience taking software through formal release, packaging, and deployment to end users

Where you probably come from: Senior IC at robotics companies that shipped, defense robotics groups, autonomy at automotive, or aerospace robotics programs that put software in front of operators.

We want to talk if: You've taken software from "works on the dev's machine" to "works in the field for a customer." You know the difference between a prototype that demos and a release that survives.

Not a fit if: You're a researcher who hasn't shipped, you're a people-manager without recent IC chops, or your robotics experience is benchmark-only.

- Built CI/CD for robotics or hardware-in-the-loop systems before

BS, MS, or PhD in CS, Robotics, EE, or equivalent. Track record matters more than degree.

- Extreme bias for action. You ship working code on real hardware, not slideware

- Clear communicator across software, hardware, and operator-facing surfaces

This role requires access to export-controlled information or items that require U.S. Person status. As defined by U.S. law, individuals who are any one of the following are considered to be a U.S.

Person: (1) U.S. citizens, (2) legal permanent residents (a.k.a. green card holders), and (3) certain protected classes of asylees and refugees, as defined in 8 U.S.C. 1324b(a)(3).