Staff Engineer, Robot Systems & Integration

Your mission & challenges

• Own the RT scheduling policy that all software in this cluster must respect: priority assignment standards, memory locking requirements, and interrupt latency contracts for 1 kHz control loops and 500 Hz state estimation.
• Own the co-review protocol at the boundary between RT OS scheduling and the EtherCAT master — any board support package change must pass a joint latency budget review before merge; you own this process alongside the Robot Communication cluster lead.
• Ensure the unified compute platform engineers have clear RT OS architecture guidance and that every robot platform profile's timing budget is validated after each hardware revision.
• Own the motion planning pipeline architectural direction: planner selection criteria, planning stack configuration standards, and atomic skill primitive API design and evolution across all robot platforms.
• Enforce the shared skill primitive library: patterns surfaced from product-specific stream work must go through design review before being forked platform-specifically; you enforce this at code review.
• Define the server/protocol boundary in industrial integration: the protocol stack belongs to the Robot Communication cluster; the server layer — command dispatch, state machine integration, hardware interfaces — belongs here; you arbitrate when server architecture and protocol constraints conflict.
• Own the end-effector server architecture: gripper lifecycle management, tool change sequencing, and the hardware interface contracts that motion planning and the operational state machine depend on.
• Lead quarterly cluster knowledge days: peer-to-peer problem exchange where every engineer brings one unsolved and one solved problem; output is a shared library ticket or design document, never slides.
• Write design documents that reduce knowledge concentration; mentor Senior engineers toward Staff level; drive cluster hiring sourcing.

What we can look forward to

• Robot systems integration depth (at least two of the following, in depth): Embedded Linux systems integration at the RT level (Yocto BSP development, RT kernel tuning, RT scheduling design, WCET analysis), ROS2 hardware interface architecture, motion planning pipeline for production manipulation, industrial device integration at the server layer, real-time skill execution or soft-RT scheduling.
• Systems integration breadth: sufficient understanding across the full stack to review MRs and arbitrate design decisions spanning OS, middleware, motion planning, and device integration domains simultaneously.
• Demonstrated experience debugging cross-layer failures at the OS–middleware–hardware boundary.
• C++17/20 systems programming: lock-free patterns, RAII, RT-safe memory management, 1 kHz control loop discipline.
• Staff-level leadership: demonstrated cross-team architectural impact, RFC or design document leadership with cross-team reach, mentoring track record, 8+ years of hands-on engineering experience.

Nice to have

• RT OS kernel-level experience combined with ROS2 or other middleware depth.
• Experience shipping a motion planning pipeline from development through to production on a manipulator or mobile manipulator.
• Industrial functional safety background at the software architecture level.
• Real-time execution engine implementation experience.
• Open-source contributions to robot systems infrastructure such as ros2_control, MoveIt2, Nav2, Xenomai.

What you can look forward to

• Become part of an agile company, actively shape topics and benefit from flat hierarchies in a highly motivated team.
• Enjoy an attractive salary, flexible working hours and 30 days of vacation.
• The freedom to contribute your own ideas and drive them forward.
• Celebrate successes together with company events.
• Take advantage of our corporate benefits program.
• And even more fun with great colleagues.