Contoro
Robotics Engineer, Autonomy
About this role
Contoro Robotics seeks a Robotics Engineer to develop autonomous software for warehouse unloading robots. You'll work on motion planning, grasp algorithms, and behavior systems for production-deployed manipulators handling heavy boxes in real-world logistics environments.
What you'll do
- Develop and improve motion planning modules including grasp planning, trajectory generation, and collision avoidance
- Build and refine behavior trees governing autonomous unloading cycles, pick selection, and error recovery
- Optimize pick success rates and cycle times through software enhancements
- Diagnose and resolve production issues via log analysis and telemetry data
- Write automated tests for motion planning and autonomy logic
- Collaborate with perception, hardware, and optimization teams on system integration
What they're looking for
- C++ and Python for production robotics
- ROS and motion planning frameworks (MoveIt)
- Kinematics and inverse kinematics
- Behavior trees or state machines
- Collision avoidance algorithms
- Linux development environments
- Production system debugging
- Robotic manipulator control
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Contoro
Contoro builds autonomous warehouse automation robots that unload boxes from trailers and containers using computer vision, motion planning, and robotic manipulation. The company is hiring robotics engineers, software engineers, data engineers, and ML specialists to develop perception systems, autonomous control software, analytics infrastructure, and motion planning algorithms for production robot fleets.
View all jobs at ContoroLikely interview questions
- Walk us through your experience developing software for deployed robotic systems in production. What was the most complex autonomy challenge you debugged, and how did you approach it?
- Describe your experience with motion planning frameworks like MoveIt or ROS. Have you worked on grasp planning or collision avoidance modules, and what were the key trade-offs you optimized for?