Robotics is where OpenSourced started, and it is still one of our strongest desks. Robots are built by teams that combine software, electronics, mechanics and controls, so hiring for them has its own challenges.
Define the layer, not just the title
"Robotics engineer" can mean very different things. Be clear which part of the robot the person will own:
- Robotics software: ROS 2, C++ and Python, motion planning and simulation.
- Perception and AI: computer vision, sensor fusion, SLAM and robot learning.
- Controls: control theory, state estimation and motion control.
- Embedded and electronics: firmware, real-time systems, PCB design and FPGA.
- Mechanical and mechatronics: design, actuators and prototyping.
- Field and service: deployment, commissioning and support on site.
Look beyond robotics job titles
Strong candidates often come from adjacent fields: automotive and autonomous vehicles, aerospace and defence, games and simulation, industrial automation, and research labs. Many have the skills you need under a different job title.
Show them the robot
Engineers want to know what they'll be building and how far along it is. Videos, demos and a chance to meet the team in the lab are powerful parts of the process.
Plan for practicalities
- Lab and field work often means more time on site than in software roles. Be clear about it.
- Defence and security work may need security clearance or UK eligibility.
- Specialists are spread across the UK and Europe, so relocation support can widen your search.
Read more about our robotics recruitment, or tell us about your role.
