I’ve spent over a decade embedded as the talent partner for a robotics company. Not as an outside agency sending CVs. Not as a marketplace recruiter racing to fill roles. As someone who sits inside the business, understands the engineering culture, and builds the team from the ground up.
And here’s what I’ve learned: the reason most robotics startups struggle to hire engineers has almost nothing to do with the talent shortage everyone keeps talking about. The problem is how you’re hiring.The Talent Isn’t Missing. You’re Looking in the Wrong Places.
Every robotics founder I speak to says the same thing: ‘We can’t find good engineers.’ But when I ask where they’re looking, the answer is almost always LinkedIn job posts, generic recruitment agencies, and the same handful of job boards that every other company is using. Here’s the reality. The best robotics engineers – the ones who can work across mechanical, electrical, and software disciplines – aren’t scrolling job boards. They’re heads-down building things. They’re active in ROS communities, presenting at ICRA, contributing to open-source projects, and talking to each other in niche Slack channels and Discord servers you’ve never heard of. If your entire hiring strategy is ‘post and pray,’ you’re competing with Google, Boston Dynamics, and every well-funded startup on the planet for the same tiny pool of active candidates. You’ll lose that fight every time.Your Job Description Is Putting People Off
I review robotics job descriptions every week, and most of them read like a wish list written by someone who’s never actually worked with hardware engineers. ‘Must have 5+ years in ROS, proficiency in C++ and Python, experience with computer vision, SLAM, motion planning, and embedded systems. PhD preferred.’ That’s not a job description. That’s a description of three different engineers. The founder wants a unicorn because they don’t understand how robotics teams actually work. Good robotics engineers are specialists who collaborate. They’re not generalists who do everything. When I work with robotics founders, the first thing we do is break down what they actually need versus what they think they need. Often, the right first hire isn’t the senior robotics engineer they’ve been searching for. It’s a strong embedded systems developer who can grow into the team as it scales.You’re Selling the Wrong Things
Big tech can offer six-figure salaries, equity packages, and brand-name prestige. If you’re trying to compete on those terms, you’ve already lost. But here’s what the best robotics engineers actually care about – and what most startups forget to mention in their job posts and conversations:- They want to touch real hardware. Many engineers at big tech companies spend years optimising simulations without ever seeing their work in the physical world. If your startup has robots doing real things in real environments, that’s incredibly compelling. Say it.
- They want ownership. At a large company, an engineer owns a small module in a massive system. At your startup, they could own entire subsystems. That autonomy is worth more than a 10% salary bump to the right person.
- They want to see impact quickly. If your robot is going to be deployed in the real world within 12 months rather than sitting in a research lab for five years, lead with that. Engineers who want to build things that matter will find this irresistible.
Chemistry Matters More Than Credentials in Hardware Teams
This is something I’ve observed across 27 years in recruitment, and it’s especially true in robotics: the teams that succeed aren’t the ones with the most impressive CVs. They’re the ones with the best chemistry. Hardware is unforgiving. When you’re debugging a robot that won’t behave the way the simulation said it would, you need engineers who can communicate clearly, handle stress without blame, and collaborate across disciplines. A brilliant engineer who can’t work with the firmware team or dismisses the mechanical constraints will slow you down more than a good engineer who fits your culture. After 10 years embedded with one robotics company, I can tell you that the hires that lasted and thrived were the ones where we assessed for team fit alongside technical capability. The hires that failed – and I’ve seen plenty – were almost always technically excellent people who simply didn’t mesh with how the team worked. That’s why I developed the Chemistry First methodology. Credentials get you interviews. Chemistry gets you results.What Actually Works: A Different Approach to Robotics Hiring
If I were advising a robotics startup founder today – and I frequently am – here’s what I’d tell them to change immediately. First, stop posting generic job descriptions and start telling your engineering story. What problem is your robot solving? What’s the technical challenge that makes this interesting? Engineers want puzzles, not bullet points. Second, go where the engineers are. ROS Discourse, robotics meetups in Austin, Boston, and San Francisco, academic conferences, open-source communities. Build relationships before you have a role to fill. The best hires come from networks, not job boards. Third, assess for team chemistry as rigorously as you assess for technical skills. I use a framework called ALIGN – Alignment, Learning Style, Integrity, Growth, Navigating Conflict – that systematically evaluates how a candidate will work within your existing team, not just whether they can solve technical problems in isolation. Fourth, move fast once you find the right person. Robotics engineers have options. If your process takes six weeks and four interview rounds, they’ll accept an offer from someone else while you’re still scheduling the panel.The Bottom Line
The robotics talent market is competitive, but it’s not impossible. The founders who consistently hire well are the ones who stop treating recruitment like a transaction and start treating it like a relationship. Your next great engineer isn’t waiting on a job board. They’re building something fascinating and they’ll only move for an opportunity that’s genuinely compelling – delivered by someone who understands their world. That’s what I do. After 27 years in recruitment and a decade embedded with a robotics company, I help founders build engineering teams that actually work together – not just teams that look good on paper. Not sure if your hiring approach is working? Book a Hiring Health Check – a 60-minute diagnostic where I’ll review your current hiring process and tell you exactly what to fix. No fluff, no sales pitch. Just honest advice from someone who’s been in the trenches.Helen Sanders is the founder of HFBAC (Hiring For and Building Awesome Companies), where she helps bootstrapped startups and growing companies build founding teams using her Chemistry First methodology. With 27 years in recruitment and a decade embedded with a leading robotics company, Helen bring a unique combination of technical understanding and people expertise to every hire. She’s also the BBC’s first female football commentator – proof that chemistry, not credentials, makes winning teams.


