Robotics software engineering
ROS / ROS 2, navigation, manipulation, motion planning, behavior trees, system architecture, and the unglamorous reliability work that keeps a fleet alive.
Specialties
A focused practice. Software, perception, autonomy, robot learning, controls, and the product and leadership seats that ship those systems. If the title is sloppy, send the stack anyway.
ROS / ROS 2, navigation, manipulation, motion planning, behavior trees, system architecture, and the unglamorous reliability work that keeps a fleet alive.
Classical vision and learned perception. Depth, lidar, multimodal fusion, tracking, scene understanding, and models that have to run on a budget.
Decision stacks for AMRs, vehicles, drones, and mobile manipulators. Prediction, planning, mapping, and the integration tax nobody puts in the job post.
Imitation learning, RL on hardware, foundation-model adaptation, data engines, and ML engineers who have argued with a real robot at 2 a.m.
Servo loops, firmware, real-time systems, actuators, and the hardware-aware engineers who keep software honest.
Robotics PMs, solutions / field application engineers, deployment leads, and the directors who can hire and still read a ROS graph.
Send the stack and the problem. Titles in this market are sloppy. The work is not.