Feeny
Neura Robotics

Robot Client SDK Engineer (Mensch) at Neura Robotics (Metzingen, Germany / Riederich, Germany)

Neura Robotics· Metzingen, Germany / Riederich, Germany·

Role details

Work type
Onsite
Employment
Full-Time
Skills
PythonC++JavagRPCprotocbufasyncioConanvcpkgMavenSphinxDoxygen

Neura Robotics at a glance

German cognitive-robotics company building humanoid and collaborative robots that see, hear, feel, and learn to work alongside people.

NEURA Robotics designs cognitive robots (humanoids, collaborative arms, and mobile bases) plus the AI and platform that run them, all built in-house. Its flagship 4NE1 humanoid targets industrial workflows and everyday assistance, and the Neuraverse platform links deployed robots into a shared learning network.

~$1.7B+ raised · latest: Series C · up to $1.4B · June 2026 · backed by Tether, Amazon, NVIDIA, Qualcomm

Summary

Build and maintain client-side SDKs in Python, C++, and Java for gRPC-based robot communication. Implement code generation pipelines, handle channel lifecycles, and ensure observability and compatibility across multiple languages.

Job description

Deine Mission & Challenges

  • protoc + buf Toolchain für Client-seitige Code-Generierung; CI-Pipelines generieren Clients bei jeder Proto-Änderung neu
  • Python Client SDK: idiomatische Wrapper mit Context Managern, Async/Await-Varianten, IDE-Autocomplete-Stubs, pip Wheels fürs interne PyPI
  • C++ Client SDK: RAII Channel Lifecycle, Async, sprachtypische Exception-Hierarchie, Conan/vcpkg Packages
  • Java Client SDK: Builder-Patterns für Requests, CompletableFuture, Maven Central Artifacts
  • Channel Lifecycle Handling über alle Sprachen hinweg: Timeouts, Deadline-Propagation, Reconnect-Logik, TLS/mTLS Konfiguration
  • Mapping von gRPC Status auf sprachtypische Exceptions: hierarchische Exception-Typen mit semantisch sinnvollen Subklassen
  • Client/Server Version-Skew Compatibility Tables – definierte Policies zur Versionskompatibilität, automatische Kompatibilitätstests
  • Semantic Versioning abgestimmt mit dem Platform Architect, Durchsetzung von Deprecation-Policies via Linter-Warnings, Migration Guides
  • Simulation-Mode im Client: gleiche Proto-Schnittstelle, aber Simulation-Backend für Offline-Entwicklung
  • Observability Hooks pro Sprache: strukturiertes Logging, OpenTelemetry Tracing Context, Prometheus Metrics
  • Referenz-Beispiel-Apps pro Sprache mit Best Practices: Pick-and-Place, Mode Switching, Fault Recovery, Telemetrie-Streaming
  • Automatisch generierte Doku pro Sprache: Sphinx (Python), Doxygen (C++), Javadoc (Java); Beispiele immer synchron zur API
  • Onboarding für interne Nutzer: Skill Bundles, Evaluierungs-Frameworks, R&D Notebooks, Demo-Apps – alles basierend auf deinen Templates
  • RFC-Co-Review mit dem Robot Platform Integration Engineer bei jeder Proto-Änderung

Auf was können wir uns freuen

  • Erfahrung mit Developer Experience für Plattform-SDKs – hat Client-Libraries für interne oder externe Nutzer gebaut und ausgeliefert
  • Fit in mindestens zwei der folgenden: modernes Python (Typing, asyncio, pyproject/wheels), modernes C++ (17/20, Async, Build-Systeme), Java (CompletableFuture, Maven)
  • Hands-on im gRPC-Ökosystem: protoc, buf, grpc-python, grpc-java, grpc-cpp – Erfahrung mit produktiven Clients
  • Multi-Language Packaging: manylinux Wheels, Conan/vcpkg, Maven Central – inkl. kompletter CI-Pipelines
  • API-Design Verständnis: gRPC/REST/GraphQL, Semantic Versioning, Deprecation-Strategien, Backwards-Compatibility
  • Erfahrung mit Doku-Tools: Sphinx, Doxygen, MkDocs – End-to-End Ownership der Dokumentation
  • Verständnis von Async-Patterns über Sprachen hinweg: Sync vs Async vs Streaming gRPC und deren Unterschiede in der Nutzung

Nice to have

  • Verständnis von Robotik oder Industrial Control, um über Latenz- und Timing-Themen mit Platform Engineers zu sprechen
  • Erfahrung mit Language Bindings für native Libraries (PyBind11, JNI, SWIG, cppyy)
  • OpenTelemetry Instrumentation Libraries in mehreren Sprachen umgesetzt
  • Grundverständnis von ROS 2 Client Libraries (rclpy / rclcpp)
  • Developer-Portals, API-Docs oder SDK-Tutorials für externe Entwickler erstellt

Why work at Neura Robotics

  • Culture: "Passion for Winning" — achievement-driven, self-responsible culture with flat hierarchies. Values include trust, honesty, speed, and "We Are Human" (people at the heart of everything).
  • Flexibility: Flexible working hours, 30 days of vacation, and a hybrid-friendly environment.
  • Team: Over 1,400 employees from more than 45 countries — highly skilled, international team of experts.
  • Growth & Development: Support for personal and professional growth via Udemy training platform and more.
  • Compensation: Competitive salary package with exclusive employee discounts.
  • Perks: Summer parties, company town hall meetings, and regular team celebrations.
  • Impact: Opportunity to work on cutting-edge cognitive robotics and AI that directly addresses labor shortages and makes a meaningful societal impact.
  • Diversity: Explicitly welcomes applications from all backgrounds, emphasizing building a team that reflects the world.
  • Application Process: Fast — initial feedback within a few days, interviews scheduled within two weeks.

Application questions