freehire launches on Product Hunt on 26 August.

Follow →

RSE-3 - Lead Robotics Software Engineer

Summary

Lead a team of robotics engineers to design, deploy, and maintain core navigation, SLAM, and state-machine software for autonomous mobile robots (AMRs) in production environments using C++, Python, ROS/ROS2, and Linux.

Key Responsibility #1:


Own the architecture and technical direction of core MAG AMR software systems — navigation, SLAM, or state machine — from design through production deployment.

Key Responsibility #2:

Provide technical leadership across teams — mentoring engineers, driving design reviews, and being the escalation point for the hardest runtime and field issues.

  • Set Technical direction and architecture for the MAG AMR software stack — navigation, SLAM, and state machine design.
  • Lead, mentor, and grow a team of robotics software engineers, including hiring and performance conversations
  • Break down roadmap priorities into workable technical plans and assign ownership across the team
  • Stay hands-on with the hardest problems — algorithm design, tricky bugs, and system-level tradeoffs
  • Coordinate with cross-country teams — hardware, product, and other regional engineering pods — to keep releases moving
  • Keep security and code quality standards enforced through regular reviews and vulnerability assessments
  • Optimize navigation algorithms — improved planning, path tracking, and motion control
  • Run a high bar on code review and engineering practice across the team, not just your own commits
  • Represent the software team in planning and roadmap discussions with leadership
  • Write and maintain clear, thorough documentation of the codebase and development activities
  • Support on-site robot deployments and field testing when required
  • Partner with the product team to keep user documentation accurate and current

Qualifications:

  • Bachelor's or Master's degree in Computer Science, Computer Engineering, Mechatronics, or equivalent
  • 5+ years building production robotics software, with strong C++ and Python
  • Deep, hands-on experience with ROS / ROS2, and real ownership of navigation or SLAM systems in the past
  • Comfortable on Ubuntu / Linux development environments
  • Experience leading or informally mentoring other engineers — technical leads count, not just people managers
  • Sharp problem-solving instincts: you identify root causes, not just symptoms
  • Self-starter who runs independently and learns fast on the job
  • Bonus: end-to-end system knowledge spanning mechanical, electrical, and software

Benefits:

  • Competitive salary
  • Comprehensive health benefits package
  • Hustle of a young startup – always something to do and something to improve Work with robots in real-life use cases running 24/7 with 99% up time
  • Opportunities for professional development and growth into leadership roles
  • Collaborative and inclusive work environment


What Does Success Look Like for This Role

Make sure the impact of the role on the team and the company is very visible here

3 months:

• You know the MAG AMR codebase, tooling, and CI/CD pipeline well enough to review anyone's work in it

• You've built working relationships with your team and understand each person's strengths

• Actively contributing to code reviews with useful, constructive feedback

• You've shipped or unblocked at least one meaningful fix or feature yourself

6 months:

• Your team is shipping navigation, SLAM, or state-machine work you've planned and structured

• There's a measurable improvement to navigation or localisation on a live deployment under your direction

• You're the first call when something breaks on a deployment, and you resolve it without escalating further

• Cross-team collaborator — hardware, software, and product teams rely on your input

12 months:

• You're driving architectural decisions for core AMR software components, not just reviewing them

• Your team has shipped algorithms that are running reliably in production at scale

• Engineers on your team are growing — you've mentored at least one into a more senior role

• You're trusted to represent the software team's priorities and tradeoffs in roadmap conversations


See also