305-306-4829 Send Us Your Open Role
Roles
Leadership Search
Tech stacks
Industries
Hiring situations
How we workAbout
How we workAll roles A to ZLeadership SearchSalary guideJobsCandidatesSend Us Your Open Role

Robotics Software Engineer Recruiters

No postings. No stacks of resumes. No chasing. You interview a short list.

No upfront fee. You pay only if you hire.

Need someone now? Call 305-306-4829.

This is what we do all day: recruit technology and IT professionals.

Robotics Software Engineers design intelligent behavior that governs autonomous hardware.

No upfront fee. You pay only if you hire.

Send Us Your Open Role

Two short steps. Role and work email first. Phone is optional.

Who do you need?

Looking for a job? Join our talent network.

Optional details
Specialty and timing, optional
How soon?

No upfront fee. You pay only if you hire. We offer a candidate replacement guarantee on standard search agreements. The applicable period and exact terms are set out in the signed client recruiting agreement.

  • No upfront fee
  • Pay only if you hire
  • Technology only
  • We reach engineers who aren't on job boards
  • Replacement guarantee on standard searches

Need someone now? Call 305-306-4829.

Autonomy EngineerPerception EngineerRobotics EngineerAutonomy EngineerPerception EngineerRobotics Engineer

What this hire really comes down to

Robotics Software Engineers design intelligent behavior that governs autonomous hardware. You bridge the gap between abstract sensor data and concrete physical movement, working with kinematics, path planning, and vision. Your work is central to systems that perceive and interact with an unpredictable world. You manage the balance between sensor processing and motor control, developing algorithms in C++ or Python to build modular architectures for safe navigation.

In this field, you contribute to simulation and integration frameworks that drive modern autonomous systems. You spend time designing state estimation modules, motion planners, and perception pipelines that operate in real time. Your scope includes heavy use of robotics middleware and simulation environments to test algorithmic changes before deployment. Your focus is on fine-tuning control loops and creating extensible, simulation-validated codebases that support long-term autonomous operations.

What we check before you see anyone

  • ROS 2 Proficiency

    We evaluate your hands-on experience with ROS 2, specifically regarding node management, messaging, and quality-of-service settings. The candidate needs to explain how you have designed a distributed system using discovery mechanisms and custom message types. Candidates must demonstrate an understanding of how to manage the lifecycle of a robot application and how to debug communication bottlenecks within a networked robot cluster.

  • C++ and Python Skill

    Their ability to uses the performance of C++ alongside the rapid development cycle of Python is essential. We check for your experience in writing performance-critical C++ code for real-time control while using Python for higher-level logic, scripting, or data analysis. We look for evidence of how you manage the integration between these languages without introducing latency in the robot's core processing loops.

  • Motion Planning

    We assess your background in implementing motion planning algorithms that work through around static and dynamic obstacles. You need to explain how you have used global and local planners to ensure safe trajectories. We look for familiarity with search-based or sampling-based planners and the candidate's ability to adapt those algorithms to the specific physical constraints and kinematic limits of the robot platform you are working on.

  • Perception Integration

    Your experience in perception is verified by how you process sensor data to map the environment or identify objects. We look for familiarity with point cloud processing, computer vision libraries, or feature extraction methods. The candidate needs to discuss how you have fused data from multiple sensor types to achieve reliable state estimation even in adverse environmental conditions or noisy sensor inputs.

  • Simulation Capability

    Simulation is central to modern robotics. We evaluate your expertise in environments like Gazebo or Isaac Sim, checking for the candidate's ability to create high-fidelity scenarios for testing algorithms. Candidates must show they can bridge the gap between simulation and the real world, ensuring that behaviors validated in a virtual space translate effectively to physical robots without requiring constant tweaking of parameters.

  • Kinematics Understanding

    We check for a fundamental understanding of forward and inverse kinematics as applied to multi-degree-of-freedom systems. You need to demonstrate how you handle Jacobian matrices or workspace constraints when directing robot movement. We are looking for engineers who can translate high-level navigation goals into specific actuator commands while maintaining stability and precision in the robot's end effector or drive base.

Where we find them

We recruit primarily from autonomy-focused organizations, advanced research universities, and participants in competitive robotics events. Our sources include developers who have spent years building custom perception pipelines and motion planning stacks for drones, warehouse automation, or collaborative robots. These engineers often come from backgrounds where they balanced academic precision with the practical demands of hardware testing. We seek talent with a record of contributing to modular, extensible robotics software.

We also focus on engineers with extensive experience in the open-source community, particularly those who have mastered the intricacies of modern robotics middleware. We look for individuals who built expertise in diverse simulation environments, enabling them to rapid-prototype behaviors before putting hardware at risk. By engaging with teams that prioritize safe autonomy, we ensure our candidates are adept at handling the unpredictable challenges of the real world for navigation.

Mistakes we see

  • Treating a credential as the answer

    Do not let ros 2 proficiency become a keyword filter. Candidates must demonstrate an understanding of how to manage the lifecycle of a robot application and how to debug communication bottlenecks within a networked robot cluster.

  • Leaving the actual scope out

    Put the responsibility for c++ and python skill in the brief, including who helps the hire and who decides. Their ability to uses the performance of C++ alongside the rapid development cycle of Python is essential.

  • Waiting until the offer to discuss the work

    Discuss what the person will own in motion planning before the interview loop. We look for familiarity with search-based or sampling-based planners and the candidate's ability to adapt those algorithms to the specific physical constraints and kinematic limits of the robot platform you are working on.

The search in three steps

  1. Agree the brief

    Our process begins with an in-depth review of your experience building autonomous systems, focusing on your specific contributions to perception, planning, or control. Your hire will discuss the architecture of a robot system you have developed, detailing how you managed data flow and state consistency across nodes. We value evidence of the candidate's ability to troubleshoot complex issues where sensor noise or physical constraints led to unexpected behaviors for the autonomous platform.

  2. Find and speak with people

    The subsequent phase involves a technical assessment where you solve problems related to simulation fidelity or control loop optimization. Your hire will work through a scenario involving a simulated robot work through a dynamic environment to demonstrate the candidate's understanding of planning and perception trade-offs. We finalize the process by ensuring your approach to modularity and safety aligns with our design principles, aiming to identify engineers who thrive on complexity.

  3. Introduce the people who fit

    We send a written brief on each person you meet, including why the work fits and the questions still worth asking about kinematics understanding. You decide who to interview. We help with the conversations through the offer.

Questions about this search

When will we see a shortlist?

We agree the search plan after checking your requirements for ros 2 proficiency and c++ and python skill, rather than promising a date before the brief is clear. We evaluate your hands-on experience with ROS 2, specifically regarding node management, messaging, and quality-of-service settings.

What if a candidate gets a counteroffer?

We ask what would make someone leave work involving ros 2 proficiency, and what could make them stay. Before you invest in interviews, we discuss whether your offer changes the problem they want to leave, including the responsibility for kinematics understanding.

Should this role be remote or on site?

Experience with ros 2 proficiency and c++ and python skill does not settle the location question. Tell us what access and supervision the work needs, including who owns decisions about kinematics understanding, so we approach people who can accept the arrangement.

How will you check fit before we interview?

We evaluate your hands-on experience with ROS 2, specifically regarding node management, messaging, and quality-of-service settings. The candidate needs to explain how you have designed a distributed system using discovery mechanisms and custom message types. Their ability to uses the performance of C++ alongside the rapid development cycle of Python is essential.

How does the fee work?

No upfront fee. You pay only if you hire. Agree the fee and the responsibilities covering ros 2 proficiency and c++ and python skill in the recruiting agreement before the search proceeds.

What if the hire does not work out?

We offer a candidate replacement guarantee on standard search agreements. The applicable period and exact terms are set out in the signed client recruiting agreement. Make sure the agreed scope includes what you expect of kinematics understanding, rather than leaving that discussion until after the start.

Send Us Your Open Role

Two short steps. Role and work email first. Phone is optional.

Who do you need?

Looking for a job? Join our talent network.

Optional details
Specialty and timing, optional
How soon?

No upfront fee. You pay only if you hire. We offer a candidate replacement guarantee on standard search agreements. The applicable period and exact terms are set out in the signed client recruiting agreement.

Pay snapshot

Robotics Software Engineer

$135,980

Median as published, released May 15, 2026. Matched to Software Developers (SOC 15-1252).

BLS reports Software Developers as a broader occupation. It does not separate Robotics Software Engineer, technology stack, seniority, certifications or employer sector. These figures are not a title-specific offer range.

Source: BLS OEWS May 2025.

See the salary guide

How a search runs

The Six-Step Search

  1. 1Search Calibration

    A call about the work. You get a written search profile.

  2. 2Market Mapping

    We identify the employer backgrounds that fit. You see where we will look.

  3. 3Professional Contact Intelligence

    We identify individual people, not job board applicants.

  4. 4Persistent Personalized Outreach

    Personal outreach and direct follow-through. You get search updates.

  5. 5Live Candidate Qualification

    A recruiter checks stack, scope and motivation in conversation.

  6. 6Candidate Intelligence and Process Support

    You receive a written brief on every person you meet.

Send Us Your Open Role

Working with Technology Headhunters

What don't you do in a permanent search?

We do not bill by the hour for permanent search or charge a retainer unless one is agreed. We do not treat reposting your job advertisement as headhunting.

Send Your RoleCall
Get a free talent snapshotGet a free job description review