20 beste Stellen als hardware engineer in metzingen, bw – aktuell auf Personalsuche

Robotics Middleware Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- C++
Direkt bewerben
Linux Infrastructure Engineer (Mensch)
Neura Robotics —Metzingen
- Vollzeit
- Informatik
- Englisch
- Analysefähigkeit
Direkt bewerben
Automation Engineer (m/w/d)
Bw Papersystems —Nürtingen
- Vollzeit
- Englisch
- Microsoft Office
- Master
Hardware Architect - Cognitive Robotics (human)
Neura Robotics —Metzingen
- Vollzeit
- Doktorat
- Master
- Elektrotechnik
Direkt bewerben
System Engineer (Mensch)
Neura Robotics —Metzingen
- Vollzeit
- Doktorat
- Master
- Analysefähigkeit
Direkt bewerben
Robotic Foundation Model Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- Azure
- Informatik
- Englisch
Direkt bewerben
Service Engineer (Mensch)
Neura Robotics —Metzingen
- Vollzeit
- Wartung
- Englisch
- Microsoft Office
- Weiterbildungsprogramme
Direkt bewerben
Cybersecurity Engineer - Cloud, Ops (Mensch)
Neura Robotics —Metzingen
- Vollzeit
- Informatik
- AWS
- C++
Direkt bewerben
Engineering Data & Change Management Specialist (Mensch)
Neura Robotics GmbH —Metzingen
- Vollzeit
- Oracle
- ERP-Systeme
- Englisch
- Mitarbeiter-Rabatt
- Flexible Arbeitszeiten
System Integration Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- Doktorat
- Master
- C++
Direkt bewerben
RT & Kernel Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- C++
- Bachelor
- Ohne Hochschulabschluss
- Flexible Arbeitszeiten
Direkt bewerben
Senior Mechanical Engineer (m/f/d)
Sereact —Stuttgart
- Vollzeit
- AutoCAD
- CAD
- Master
- Mitgliedschaft im Fitnessstudio
- Flexible Arbeitszeiten
Firmware Engineer — Dexterous Hand Systems (Mensch)
Neura Robotics GmbH —Metzingen
- Vollzeit
- Mitarbeiter-Rabatt
- Flexible Arbeitszeiten
Robot Platform Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- C++
Direkt bewerben
Functional Safety Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- Doktorat
- Master
Direkt bewerben
Hardware Architect - Cognitive Robotics (Mensch)
Neura Robotics —Metzingen
- Vollzeit
- Doktorat
- Englisch
- Master
Direkt bewerben
Locomotion & Whole-Body Control Engineer (human)
Neura Robotics —Metzingen
- Vollzeit
- Doktorat
- Master
- C++
Direkt bewerben
AV Engineer 3 - Stuttgart, Germany
M.C. Dean, Inc —Stuttgart
- Vollzeit
- AutoCAD
- Microsoft Office
- Präsentationserfahrung
PMU Digital Verification
Apple —Nabern
- Python
RT & Kernel Engineer (Mensch)
Neura Robotics —Metzingen
- Vollzeit
- C++
- Bachelor
- Ohne Hochschulabschluss
- Flexible Arbeitszeiten
Direkt bewerben

Ich möchte aktuelle Job-E-Mails für Stellen als hardware engineer in metzingen, bw erhalten

Wenn Sie sich bei Ihrem Konto anmelden, stimmen Sie den Nutzungsbedingungen, den Richtlinien zur Verwendung von Cookies sowie der Datenschutzerklärung von SimplyHired zu.

Weitere Job-Standorte erkunden

hardware engineer jobs near metzingen, bw

Jobs als Security Engineer in Metzingen

Jobs als Architekt in Metzingen

Jobs als System Engineer in Konstanz

Jobs als Principal Software Engineer in München

Jobs als System Engineer in München

Jobs als System Engineer in Bamberg

Jobs als System Engineer in Kempten (allgäu)

Jobs als Data Engineer in Frankfurt Am Main

Jobs als Security Mitarbeiter, Geldtransport in Hannover

Jobs als Requirements Engineer in Köln

Jobs als Security Engineer in Koblenz

Jobs als Cyber Security in München

Jobs als Security Engineer in Nordrhein Westfalen

Jobs als Security Engineer in Hamburg

Jobs als Software Architect in München

Jobs als Enterprise Architect in Berlin

Jobs als Hardware Architect in München

Jobs als Hardware Design Engineer in München

Jobs als Computer Hardware in Hannover

Jobs als Controls Engineer in Nordrhein Westfalen

Robotics Middleware Engineer (human)

Neura Robotics -
Metzingen

Direkt bewerben

Details zur Stelle

Vollzeit

Qualifikationen

QoS
C++
C
Eclipse

Vollständige Stellenbeschreibung

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.

What we can look forward to

C++ depth with real-time-safe patterns — lock-free queues, zero-copy semantics, allocation discipline, RT-safe logging.
Operational understanding of how middleware QoS settings behave at the wire-protocol level — not just configuration syntax. Comfortable reasoning about reliability, durability, history depth, fragmentation, discovery, and the failure modes each produces under load.
Production experience integrating middleware into a real-time robot control loop with deterministic timing requirements.
Production hands-on in AT LEAST ONE of the four core middleware paradigms (treated as parallel valid entry paths): (a) ROS 2 with ros2_control hardware interface authoring and lifecycle node design (Jazzy or Humble); (b) OROCOS RTT — component authoring, port-based composition, hard-RT deployment; (c) Apex.OS / Apex.Middleware — deterministic deployment, especially in automotive or industrial SIL contexts; (d) direct DDS implementation work — FastDDS, Cyclone DDS, or RTI Connext at the configuration-and-tuning level (not consumer-of-defaults), including QoS profile design for production deployments.

Nice to Have

Hands-on across MORE THAN ONE of the four paradigms above — multi-middleware experience is the role's distinguishing competence, not a baseline requirement.
Eclipse Zenoh for fleet-scale distributed messaging or edge scenarios.
Iceoryx or alternative zero-copy IPC integration.
Multi-middleware bridging patterns: ros1_bridge, OROCOS-ROS2 component bridging, or custom abstraction layers.
DDS Security plug-ins (authentication, access control, cryptographic transformation) for SIL-grade deployments.
Open-source contributions to any of the major middleware ecosystems (ROS 2 core, OROCOS Toolchain, Apex.OS, eProsima FastDDS, Eclipse Cyclone DDS, RTI Connext community).

Direkt bewerben

Erweiterte Suche

hardware engineer Jobs in metzingen, bw

Robotics Middleware Engineer (human)

Linux Infrastructure Engineer (Mensch)

Automation Engineer (m/w/d)

Hardware Architect - Cognitive Robotics (human)

System Engineer (Mensch)

Robotic Foundation Model Engineer (human)

Service Engineer (Mensch)

Cybersecurity Engineer - Cloud, Ops (Mensch)

Engineering Data & Change Management Specialist (Mensch)

System Integration Engineer (human)

RT & Kernel Engineer (human)

Senior Mechanical Engineer (m/f/d)

Firmware Engineer — Dexterous Hand Systems (Mensch)

Robot Platform Engineer (human)

Functional Safety Engineer (human)

Hardware Architect - Cognitive Robotics (Mensch)

Locomotion & Whole-Body Control Engineer (human)

AV Engineer 3 - Stuttgart, Germany

PMU Digital Verification

RT & Kernel Engineer (Mensch)

Ich möchte aktuelle Job-E-Mails für Stellen als hardware engineer in metzingen, bw erhalten

Related Searches

Weitere Job-Standorte erkunden

Your Mission & Challenges

What we can look forward to

Nice to Have

Tools für Jobsuchende

Arbeitgebertools

Durchsuchen

Bleiben Sie in Kontakt