Loading
Write ROS 2 code that ships through a safety review.
Robotics software engineers write the perception, planning, and control code for robots — manipulators, mobile robots, cobots. You speak ROS 2 fluently, write code against safety-rated control systems, and produce risk-assessment packages a customer can audit. The role bridges machine-learning (perception), control engineering (motion), and safety engineering (ISO 10218 risk assessments).
“You start by reviewing yesterday's PFL force measurements from the contact-points matrix on a customer cell — one quasi-static reading is 5% above the Annex A threshold for sternum contact. You investigate, find the end-effector geometry has a sharper edge than the design intent, and write the deviation report. Mid-day, you debug a TF2 chain that's making MoveIt fail intermittently. After lunch, you review a junior engineer's R15.06 risk-assessment package and walk them through what's missing in the cybersecurity section.”
Recommended curriculum path
Write ROS 2 code that ships through a safety review.
9 required
17 required
28 required
When you complete this track, you'll have built:
ISO
Safety requirements for robot systems in industrial environments (Part 1). Absorbed ISO/TS 15066 in 2025.
ANSI / A3 (US)
US national adoption of ISO 10218. The risk-assessment package's anchor.
ANSI / A3
Testing methodology for power-and-force-limited (PFL) collaborative robots.
Southwest Research Institute / ARM Institute
The canonical public training for ROS in industrial settings. Free.
IEC
Functional safety of E/E/PE systems. Parent standard of ISO 13849 + IEC 62061.
Roles you can grow into from here.