Robotic Service System Engineer NeuraGym (Human)

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.

How you work

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 escalate 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.

The three critical skills

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:

1. End-to-end system thinking. 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.

2. Structured troubleshooting. 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.

3. Linux, network and IT skills. 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 mission & challenges

Your responsibilities, in order of priority:

1. Root cause analysis

• Analyse faults across mechanics, electronics, software and the cell environment, and narrow them down to the root cause

• Read logs, telemetry and sensor data, and reproduce failures in a controlled way

• Fix software, configuration, calibration and network issues within the first-line scope

2. Escalation and documentation

• Write clean, reproducible tickets with logs, steps and expected versus observed behaviour, and escalate design issues directly to the Business Unit

• Keep the robot lifecycle board and the failure case library up to date

3. Team and service standard

• Coach the Robotics Service Technicians in diagnosis and commissioning

• Help build the troubleshooting routines, the status information in the UI and the service playbook, together with the Robots & Cell Infrastructure team

What we are looking for

Must-have:

• Degree or equivalent experience in robotics, mechatronics, electrical engineering, computer science or a comparable field

• Experience in systematic fault finding on robots, automation or complex mechatronic systems

• Solid skills in Linux, networking and scripting (for example Python or Bash)

• Ability to read logs and sensor data and to separate symptom from cause

• Clear written English for tickets and documentation

Nice to have:

• Experience with ROS 2, robot calibration or motion control

• Experience with virtualization, containers and GPU drivers

• Experience with humanoid or mobile robots, or with running vehicle and machine fleets

• Knowledge of safety concepts for collaborative robots

• German language skills