Controls Engineer (Robotics)

Job description

Job responsibilities

• Own the safety-critical control code for our arms: Limits, stop behavior, collision response, and the monitoring around the control loop
• Work on the control loop itself: Timing, stability, and failure modes, from the motion command down to the drives
• Organize the code so it can be trusted: Keep the safety-critical parts small, separated, tested, and reviewable, and set the rules for how other code touches them
• Build hardware-in-the-loop testing: A bench and a continuous-integration path that run the control code against real arms and real safety hardware
• Keep the evidence current: Stopping-time measurements and the tests behind the safety argument, updated whenever the code or the hardware changes
• Document the design: Decisions, limits, and the reasons for them, in a form other engineers follow

Job requirements

• Real-time control experience on physical systems: Robot arms, vehicles, aircraft, or similar. You have written control code that moved hardware and handled its failures
• Experience in a mission-critical codebase: You have written and organized a large amount of code where mistakes had physical consequences, and you know what that requires of structure, testing, and review
• Comfortable with the physics: Dynamics, torque, inertia, stopping distances, contact. You can reason about what the arm will do
• Strong systems software: C++ and Python or similar, real-time behavior on Linux, and safety-critical code kept separate from the rest
• Experience with hardware-in-the-loop testing: You have built or used a rig that put real hardware in the loop with software under test