Senior Robotic Systems Integration Engineer
How do you deploy humanoids at scale when each one still needs an engineer beside it?
That’s the next problem for this robotics startup.
The team has built the core capabilities. Robots are moving into real customer environments. Now the work is making those behaviours reliable enough to repeat, understanding why they fail, and building a way to deploy them without sending the engineering team along every time.
You’ll own that transition.
The engineering challenge
A behaviour works in testing. You release it. In the field, the robot stops short of where it should.
You’ll need to work out whether the problem sits in perception, planning, control or the way those pieces interact. More importantly, you’ll make sure the next run captures enough evidence to find the answer.
Working alongside ML and robotics engineers, you’ll take new capabilities through testing and into deployment. Your decisions will shape what gets released, what needs more work, and what the team fixes next.
What you’ll own
-
Define release criteria and repeatable tests that show how a behaviour performs and where it breaks.
-
Get hands-on with the codebase and hardware to diagnose failures across the robotics stack.
-
Build logging and review tools that let engineers investigate field issues without standing beside the robot.
-
Turn failed runs into clear engineering priorities, then work with the original developers to ship improvements.
-
Develop the metrics and deployment practices needed to track performance and roll out changes across a growing fleet.
There’s plenty still to build. You’ll have room to shape the approach, including the judgement to start with a useful manual process and automate it once you understand what works.
What you’ll bring
You’ve worked on real robotic systems and followed problems across hardware and software. You can read the code, question the behaviour, and keep investigating until you have a useful explanation.
ROS 2, perception, planning and control should be familiar ground. So should working through bag files and logs to understand what actually happened.
Experience with field deployments, fleet operations or rolling out robot updates would be especially useful. If your deployment experience is smaller, we’ll want to understand how you’d make it repeatable as the fleet grows.
You might come from a startup, a larger robotics business or a research team that puts systems into the field. What matters is what you’ve personally built, debugged and taken responsibility for.
Why join now?
You’ll join while the team is establishing how its robots will operate beyond closely supervised deployments. The testing and release decisions you make now will influence how the product scales.
It’s a small team working closely with physical hardware, so expect to be in the office most days, with occasional flexibility. You’ll have direct access to the engineers building the capabilities and the opportunity to see your changes tested on the robot.
Interested?
Apply directly to hear more.