Robotics Middleware Engineer

Your Mission & Challenges

• You will own the middleware integration layer for the NEURA Core Robot Software department, spanning the full robotics middleware spectrum with applications ranging from real-time control to fleet messaging. Production and cognitive robotics increasingly need multiple middleware paradigms running side-by-side.

• ROS 2 stack: End-to-end responsibility for the ROS 2 layer across all robot platforms: sensor driver nodes, ros2_control YAML composition, DDS QoS tuning, Nav2 configuration, launch system architecture, and the diagnostic framework. Different release versions starting from Humble and Jazzy are maintained for both long-term and short-term migration cycles.

• OROCOS RTT integration: Ownership of the port-based hard-RT component layer behind the dynamics and whole-body control solver pipelines, where execution needs to stay deterministic down to sub-millisecond precision — including an application and service interface which serves as a hardware abstraction layer.

• Apex.OS / Apex.Middleware: This covers the full path from a standard ROS 2 development setup to a safety-ready Apex.OS deployment. This involves applying Apex.OS with its ISO 26262 ASIL-D certification for providing a deterministic, safety-certifiable ROS 2 runtime for any product line that needs to meet functional safety requirements.

• DDS infrastructure: Depending on platform or customer context, different variants and versions of FastDDS, Cyclone DDS, and RTI Connext need to be integrated, extended or bridged. The depth requires understanding how QoS choices play out at the RTPS wire level, how network address schemes and discovery methods apply in real network conditions, and where fragmentation and reliability semantics matter in practice.

• Eclipse Zenoh: The integration of new Zenoh-driven systems in local or wide area networks involves bridging to an existing multi-middleware stack, verifying requirements, and establishing a stable integration.

• Zero-copy IPC: For single host contexts, use zero-copy transport via Iceoryx2, rmw_iceoryx2 for ROS 2, or any of the other middleware's shared memory transport as a means to establish inter-process communication (IPC), such as for 1 kHz real-time data exchange or bridging different software domains, avoiding any communication overhead.

• Managing cross-middleware interface coherence: Robot state and command contracts need to behave consistently across all middleware surfaces the stack exposes. Keeping those contracts aligned as the system evolves is an ongoing responsibility. This also involves harmonizing the use of timestamped sensor streams, multi-modal observations, port assignments, and topic type schemes across stacks so both the end-to-end data plane and the ecosystem remain coherent.