Robotics Embedded Software Engineer
✓
Which company are you aiming at?
To generate precise rejection-prevention feedback and application strategy, tell us where you're targeting.
2
Send your application
You need an account so we know where to send the feedback.
The job description
Tech stack. C/C++, ROS 2, micro-ROS, ARM Cortex-M/A, CAN, EtherCAT, IMU/encoder interfaces, real-time control loops, Gazebo/simulation
About the role
You will join a humanoid robotics company building the embedded nervous system of its robots: joint controllers, sensor interfaces, and the real-time bridge to the autonomy stack. The embedded team turns high-level motion commands into precise, safe physical behavior. This role matters because a robot that cannot trust its own joints cannot walk, and the gap between a simulation demo and a robot that works all day is closed in firmware.
What you will achieve
- Ship embedded joint-controller firmware for a 20+ degree-of-freedom platform, holding torque control loops at 8 kHz with verified stability margins across the full joint range, documented in the control design report
- Drive sensor fusion interface reliability (IMU, joint encoders, force-torque) so state estimation receives timestamp-synchronized data with under 100 microseconds of jitter
- Reduce actuator fault recovery time from seconds to milliseconds by building deterministic fault detection and safe-state transitions in firmware, validated by fault-injection testing
- Build the micro-ROS bridge between embedded nodes and the autonomy stack, sustaining 1 kHz bidirectional messaging without packet loss over 24-hour soak tests
- Own hardware-in-the-loop validation for new actuator revisions, catching control regressions before they reach the full robot and cutting integration surprises by half, as tracked in the integration defect log
What you will bring
Must-haves
- 2-5 years writing embedded firmware for robots, drones, or other mechatronic systems with real actuators and real inertia
- Strong C/C++ with real-time control experience such as PID, feedforward, or model-based control running on real hardware
- Familiarity with ROS 2 concepts and the embedded boundary, including micro-ROS, custom transports, or DDS at the edge
- Hands-on experience with motor drivers and encoders: FOC, current sensing, and commutation tuning on the bench
- Knowledge of deterministic fieldbuses such as CAN, CAN FD, or EtherCAT for distributed control
- Experience with IMU bring-up: calibration procedures, filtering, and timestamp synchronization across sensors
- A builder's instinct: you have made something move and debugged it systematically when it did not
Nice-to-haves
- Experience with functional safety in robotics such as safe torque off and monitored standstill
- Familiarity with whole-body control or impedance control concepts from research or prior products
- Simulation-to-hardware correlation experience with tools such as Gazebo or Isaac Sim
Apple
NVIDIA
Tesla
Qualcomm
Bosch
Garmin