Principal Software Engineer (Robot Software)

Join our team as a Principal Software Engineer - Robot Software. In this high-visibility role, you will influence the roadmap for our Embodied AI platform and mentor the next generation of technical leaders. You will be responsible for the architectural integrity, scalability, and performance of the software stacks that power our vehicles. Your success will be defined by the business success built upon your technical roadmaps, the team's success, and the adoption and impact of your processes and guidance.

• Partner with leadership to define a 12-24 month technical roadmap, aligning and enhancing existing systems to meet customer demands.
• Lead the design of complex, cross-functional systems, ensuring seamless integration of the "Robot" layer with broader Embodied AI algorithms.
• Set the bar for code quality, testing rigor, and observability, leading design reviews for critical components of the stack and championing centralized, reusable solutions.
• Problem Solving: Ability to debug "impossible" problems across the boundary of hardware and software
• Languages: Mastery of C++ (17/20) with a focus on memory management and concurrency. Proficiency in Python
• Architectural Depth: Proven track record of shipping complex autonomous systems, distributed systems, or safety-critical embedded software
• Leadership: Exceptional communication skills; ability to explain complex technical trade-offs to non-technical stakeholders
• Safety Above All: Understands that in the world of self-driving, "moving fast and breaking things" isn't an option
• Domain Expertise: Deep experience in Robotics Middleware (ROS2, Cyber RT, or custom IPCs) and Real-Time Systems
• We understand that everyone has a unique set of skills and experiences and that not everyone will meet all of the requirements listed above. If you’re passionate about self-driving cars and think you have what it takes to make a positive impact on the world, we encourage you to apply
• Anticipates Failure: Thinks three steps ahead e.g. about how a change in one sub-system might break the integration of a parallel roadmap six months from now
• Simplify Complexity: Can take a messy, monolithic codebase and guide the team toward a clean, modular architecture without stopping feature development