A complete application in a minute
Tailored resume and cover letter, ready to send.
Neura Robotics seeks a Robotics Service Technician Lead to diagnose faults across hardware, software and network layers in robot cells. You will coach technicians, document findings, and drive first-line fixes to maintain production uptime.
You will work closely with the Robots & Cell Infrastructure teams to build troubleshooting routines and scalable service playbooks for current and future robot generations.
The technical backbone of the gym service team
When a cell is not producing or an episode is broken, you find out why. The failure often shows up in the data but starts in hardware or in the network, and you are the person who tells which layer it is.
You fix what can be fixed on site and hand over everything else to the BU with a clean, reproducible ticket. You also help build the troubleshooting routines and the service playbook that will scale to every gym and, later, to customer robots.
You are part of the gym service team (Level 1.2) and lead the Robotics Service Technicians in daily work: they report to you and you coach them in diagnosis. The Robots & Cell Infrastructure team supports you with blueprints, standard processes and training, and you elevate design issues directly to the Business Unit product engineering team. You also learn with the NEURA service engineers, so that field findings improve the next robot generation.
Every engineer in the team needs breadth across the whole system and depth in at least one domain. These three skills are the core of the profile:
You understand the full data path: sensor or robot, cell PC, network, server VM, Data Engine, storage. You can tell at which layer a problem sits when an episode is broken or the cell is not producing. Typical gym failures such as frame drops, timestamp offsets and calibration drift show up in the data but often start in hardware or the network.
You work from hypotheses, not guesswork. You run targeted interface tests, swap parts in a controlled way and separate the workaround from the root cause. This is the core of Level 1.
Often underrated in hardware profiles. Without journalctl, ip, ssh and docker, half of all faults cannot be resolved.
We test these skills in the interview with a hands-on task: find a planted fault on a robot cell, from symptom to root cause and ticket.
Your responsibilities, in order of priority: