Software Engineer - Robotics
Software Engineer - Robotics
Posted today
SENIORITY
Senior
About the role
- 7+ years of professional software development experience
- Strong full stack development experience across front-end and back-end systemsExperience developing and deploying software within a robotics company or robotics-focused environment
- Proficiency with Go, Python, TypeScript, or similar programming languages
- Experience building production front-end applications using React or a similar framework
- Experience designing and implementing APIs and software architecture
- Experience with robotics analytics, fleet monitoring, operational metrics, or real-time dashboards
- Experience with messaging and streaming systems, including queues, pub/sub, or WebSocketsExperience building and maintaining CI/CD pipelines using tools such as GitHub Actions or Jenkins
- Strong understanding of software engineering principles, clean code, SOLID design, and test-driven development
- Experience working with real-time telemetry, monitoring, and observability systems
- Strong debugging and problem-solving skills
- Excellent communication skills and ability to collaborate across software, hardware, and robotics teams
- Experience with ROS or ROS2Familiarity with robot autonomy frameworks, behavior trees, or state machines
- Experience with Behavior
- Tree. CPP, py_trees, or similar toolsExperience with MQTT, Open
- Telemetry, or real-time telemetry systemsExperience visualizing robotics data, telemetry, maps, or spatial information
- Familiarity with robot log analysis, data replay, ROS bags, or structured event logs
- Experience building teleoperation interfaces or remote robot supervision toolsExperience with low-latency video streaming
- Experience with simulation environments such as MuJoCo or Isaac SimExperience with software-in-the-loop testing
- Experience with edge computing, on-robot services, over-the-air deployments, or fleet orchestration
- Experience mentoring engineers or providing technical leadership
- Contributions to open-source projects
- Design, develop, and maintain software across the robotics technology stack
- Build and improve front-end applications for fleet monitoring, mission planning, teleoperation, and operational dashboards
- Develop back-end services, APIs, and tooling that connect robot systems, operators, and cloud infrastructure
- Implement and maintain behavior trees and decision-making logic that support robot autonomy
- Develop tools to author, visualize, test, and debug robot behaviors
- Build reliable data pipelines connecting sensors, software processes, and robotics systems
- Identify and resolve concurrency issues, race conditions, deadlocks, and system integration problems
- Develop operational metrics to track robot uptime, mission success, throughput, intervention rates, and fleet health
- Establish engineering standards for testing, CI/CD, monitoring, and observability
- Improve system reliability, debuggability, and performance across deployed robotics platforms
- Collaborate with robotics, hardware, perception, controls, data science, and field operations teams
- Mentor engineers and help establish best practices across the engineering organization
- Evaluate technical risks and architectural trade-offs and communicate recommendations to leadership
- Support software deployment, troubleshooting, and continuous improvement of robots operating in real-world environments
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
