Senior Robotics Middleware Engineer - Humanoid (human)

Darum lohnt es sich

Enable reliable operation of control pipelines running from high-frequency actuator loops up to fleet-level software services. /p /li /ul h3bWhat we can look forward to /b /h3 ul lipStrong C++ expertise with real-time-safe software development practices, including lock-free programming, memory management, zero-copy communication, and deterministic execution. /p /li lipDeep understanding of Linux-based robotic systems and real-time middleware architectures. /p /li lipPractical experience integrating middleware into real-time robotics systems operating under strict latency and determinism requirements. /p /li lipStrong understanding of DDS concepts, including QoS policies, discovery mechanisms, reliability models, durability, history management, fragmentation, and network-level performance tuning. /p /li lipProduction experience in at least one of the following domains: /p ul liROS 2 architecture, ros2_control, lifecycle management, hardware interfaces, and system integration. /li liOROCOS RTT and hard real-time robotics software. /li liApex.OS / Apex.Middleware deployments in industrial or safety-critical environments. /li liDDS infrastructure development using FastDDS, Cyclone DDS, or RTI Connext. /li /ul /li lipExperience collaborating with controls, locomotion, manipulation, perception, and embedded software teams in complex robotic systems. /p /li lipSolid understanding of networking, Linux performance tuning, real-time kernels, profiling, debugging, and distributed systems. /p /li /ul h3bNice to Have /b /h3 ul liExperience developing software for humanoid robots, legged robots, or other complex floating-base robotic systems. /li liHands-on experience supporting locomotion, whole-body control, manipulation, perception, or state estimation pipelines. /li liExperience integrating communication frameworks into high-frequency control loops (500 Hz–1 kHz). /li liEclipse Zenoh for distributed robotics, teleoperation, or fleet-management applications. /li liIceoryx or other zero-copy IPC technologies. /li liExperience bridging multiple middleware ecosystems, including ROS 2, OROCOS RTT, DDS, and custom robotics frameworks. /li liDDS Security, authentication, encryption, and access-control mechanisms. /li liContributions to ROS 2, OROCOS, Zenoh, DDS implementations, or other robotics infrastructure projects. /li liExperience working on large-scale robotics software platforms with dozens of interacting subsystems and multidisciplinary teams. /li /ul /p #J-18808-Ljbffr ppYou will own the middleware integration layer for the b4NE-1 Humanoid Software Platform /b, ensuring reliable communication between perception, planning, locomotion, whole-body control, manipulation, state estimation, hardware interfaces, and fleet-level services.

The humanoid stack spans multiple middleware paradigms, ranging from hard real-time control loops to distributed cloud-connected robotics systems, all of which must operate seamlessly on a production humanoid robot. /p h3bYour Mission Challenges /b /h3 ul lipbROS 2 Platform Integration: /b own the ROS 2 infrastructure used across the 4NE-1 software stack, including sensor and actuator interfaces, state estimation pipelines, perception systems, locomotion, manipulation, diagnostics, and fleet connectivity.

Responsibilities include ROS 2 architecture, driver integration, ros2_control configuration, DDS tuning, launch system design, diagnostics, and migration across ROS 2 releases such as Humble and Jazzy. /p /li lipbOROCOS RTT Real-Time Integration: /b own the hard real-time middleware layer that powers humanoid locomotion, whole-body control, inverse dynamics, and low-level control pipelines.

This includes OROCOS RTT component architecture, deterministic execution, inter-process communication, and service abstractions used to bridge high-level software with safety-critical hardware interfaces. /p /li lipbApex.OS Functional Safety Deployment: /b develop the path from research-oriented ROS 2 software to safety-ready production deployments.

This includes integration of Apex.OS and Apex.Middleware where required, supporting deterministic execution and future safety-certifiable humanoid applications that must meet functional safety requirements. /p /li lipbDDS Communication Architecture: /b design and maintain the DDS communication infrastructure used throughout the humanoid platform.

Integrate, configure, and optimize FastDDS, Cyclone DDS, and RTI Connext deployments, ensuring reliable communication between distributed software components operating under strict timing constraints.

Understand and troubleshoot reliability, discovery, latency, fragmentation, and QoS behavior at the RTPS protocol level. /p /li lipbZenoh Distributed Robot Connectivity: /b drive the integration of Eclipse Zenoh for distributed robotics use cases, including remote operation, fleet supervision, cloud connectivity, teleoperation, data collection, and multi-robot communication.

Ensure reliable interoperability with existing ROS 2 and DDS-based systems. /p /li lipbZero-Copy High-Bandwidth Data Transport: /b develop low-latency data transport mechanisms for bandwidth-intensive humanoid workloads such as perception pipelines, whole-body state streaming, motion planning, simulation interfaces, and real-time control.

Leverage technologies such as Iceoryx2 and shared-memory DDS transports to eliminate unnecessary copies and minimize communication latency. /p /li lipbCross-Stack System Integration: /b ensure consistent communication contracts across the complete humanoid software stack.

State estimation, perception, motion planning, manipulation, locomotion, whole-body control, simulation, and hardware interfaces must share coherent message definitions, time synchronization strategies, coordinate frame conventions, and interface standards as the robot evolves. /p /li lipbReal-Time Performance Reliability: /b work closely with locomotion, controls, perception, and systems engineers to identify communication bottlenecks, deterministic execution issues, synchronization problems, and latency-related failures.