Robot Platform Engineer (human)

Atlas Metrics; München; Vor Ort; EUR 60.000 - 80.000; Vollzeit

Benefits dieser Stelle

Creative work culture

Flexible hours

30 vacation days

Competitive salary package

Exclusive employee discounts

Zusammenfassung

Atlas Metrics is seeking a Robot Platform Engineer to shape robotic solutions that redefine human-machine collaboration. Based in Munich, you will work within an agile software department on innovative projects using cutting-edge technology.

Your responsibilities include integrating robot abstraction layers, managing middleware wiring, and ensuring effective fault management. The role promises creative freedom, a competitive salary, and support for professional growth.

Qualifikationen

• Experience with ROS 2, OROCOS RTT, or other middleware.
• Familiarity with hierarchical state‑machine patterns.
• Intuition for hardware integration and timing assumptions.

Aufgaben

• Integrate robot abstraction layer code.
• Manage middleware wiring and state machine design.
• Ensure proper fault management and health monitoring.

Kenntnisse

Strong C++ – modern features (C++17 or later)

State-machine design experience for complex robotic systems

gRPC and protobuf

Robot abstraction layer experience

Experience bringing up a real robot platform end‑to‑end

Jobbeschreibung

Robot Platform Engineer (human)

Neura Robotics • Munich

Full-time • from today

Shape the Future of Human-Robot Collaboration

In the Software Department, you are shaping robotic solutions that redefine human-machine collaboration. You will work with cutting‑edge technology, setting industry‑changing standards. Not only will you help develop our solutions, but you will also set new trends and drive innovations forward. In an agile and interdisciplinary team, you will engage in exciting projects. With clear Scrum processes such as daily stand‑ups, sprint planning, and reviews, you remain flexible and efficient. Collaborating closely with other departments allows you to create software solutions that are both technically advanced and practically effective. Here, you will find an environment where creativity and technological excellence go hand in hand. If you are eager to turn ideas into reality and enjoy taking technology to the next level, the Software Development Team at NEURA offers the perfect challenge for you.

Your mission & challenges

• Robot abstraction integration: working in robot abstraction layer code – implementing the abstraction surface that maps your platform's hardware capabilities (joints, limbs, end-effectors, sensors) to the shared platform API.
• Middleware wiring for your platform: ROS 2 launch graph + ros2_control YAML + DDS QoS on platforms using the standard middleware path; OROCOS RTT component pipelines on platforms with hard‑RT control loops that exceed ROS 2 callback timing budgets; Apex.OS on SIL/PLd-certified configurations (Industrial MM). Sensor topic plumbing and ObsAssembler wiring regardless of middleware choice.
• Operational state machine: BOOT to HOMING to OPERATIONAL to FAULT to E‑STOP to RECOVERY for your specific platform, including all transition guards, entry/exit actions, and timeout handling.
• Mode switching: active controller selection, mode transition guards, safe mode entry/exit, gravity‑compensation‑only mode.
• Power‑on/off sequences: boot sequencing, drive enable/disable ordering, homing procedure orchestration, controlled shutdown.
• Watchdog and fault management: fault classification (recoverable vs safety‑critical), recovery action selection, escalation to E‑stop.
• Robot‑level health monitoring: aggregating diagnostics, joint state health, drive temperature, joint limit proximity, communication latency.
• gRPC server implementation: mode commands, state queries, fault acknowledgement, streaming joint state, operational state, diagnostics.
• Proto message co‑ownership for the robot control API with the Platform Architect and Robot Client SDK Engineer.
• Platform integration test suite: end‑to‑end CI test coverage in simulation (MuJoCo / Isaac Sim) and on real hardware.

What we can look forward to

• Strong C++ – modern features (C++17 or later), real‑time‑safe patterns, allocation discipline.
• State‑machine design experience for complex robotic systems: clean separation of states, transition guards, fault handling. Familiarity with hierarchical state‑machine patterns (Boost.SML, sc::statechart, BehaviorTree.CPP, or equivalent).
• gRPC and protobuf: API server implementation, streaming RPCs, backward‑compatible proto evolution.
• Robot abstraction layer experience from prior production work – expressed through any ONE of the following equivalent paths (no single framework is a hard gate): ros2_control hardware interfaces (Jazzy or Humble); MoveIt2 hardware interface authoring; OROCOS RTT components for hard‑RT control pipelines; Apex.OS deployment on a real platform; vendor SDKs such as Franka Control Interface, Universal Robots URX, KUKA Sunrise.OS, ABB EGM, or comparable; or proprietary in‑house robot abstraction layers from prior production work.
• Experience bringing up a real robot platform end‑to‑end – not only simulation. Hardware integration intuition: timing assumptions, sensor calibration discipline, fault scenario design.

Nice to Have

• Hands‑on with MORE THAN ONE of the robot abstraction layer paths above – multi‑stack experience speeds onboarding.
• ROS 2 (Jazzy or Humble) production hands‑on – currently the most common middleware path on NEURA platforms.
• OROCOS RTT exposure where the platform's hard‑RT requirements call for it.
• Apex.OS familiarity for the Industrial MM SIL‑certified configuration.
• Cluster‑specific depth – for the Mobile Manipulator anchor: Nav2 or equivalent AMR navigation stack, docking cycles, optional PROFINET familiarity; for the Legged anchor: floating‑base state estimation concepts, gait controller integration, fall detection patterns; for the Cobot anchor: ISO 10218 / ISO/TS 15066 collaborative‑robot mode design.
• Multi‑platform robot integration experience – having shipped state‑machine logic for two or more distinct robot platforms.
• Fault tree analysis (FTA) or FMEA for robotic state‑machine design.
• gRPC‑Gateway or REST/gRPC bridging for customer‑facing API surfaces.
• Note on internal stack familiarity: direct experience with NEURA's internal RAL is not required. The codebase is the entry point of the role, not the prerequisite.

What you can look forward to

Creative Freedom and Agility

Enjoy a dynamic, self‑reliant work culture with flat hierarchies, flexible hours, and 30 vacation days. Ideal for those seeking an inspiring professional setting, whether you're starting out or an experienced exec.

Passion for Winning

A passionate and highly skilled team of international experts aiming to redefine robot assistants.

Attractive Compensation

Enjoy a competitive salary package along with exclusive employee discounts.

One Team

Whether it's a summer party or company town hall meetings, we celebrate our successes together.

Professional Growth

Support for your personal and professional development.

Location

Munich – Obersendling district.