NEURA Robotics
Robot Client SDK Engineer (Mensch)
Metzingen / Riederich
hirly Pro
Get in front of the people hiring at NEURA Robotics
- Reach the hiring manager at NEURA Robotics on LinkedIn, from your own account
- hirly applies to this job for you, with unlimited applications
- A resume and cover letter written for this job, unlimited
- The hiring manager and recruiter at NEURA Robotics, with contact details
$49 a month · ₹1,999 for 30 days in India · cancel any time
Get past the screening software and onto a recruiter's desk
hirly rewrites your resume for this job — matching the keywords and skills in the posting, moving your most relevant experience to the top, and writing a cover letter to fit. About 30 seconds.
- Keywords matched to this posting
- Fit score before you apply
- Cover letter included
Matched against 2.8M live jobs from 220,000+ employers in 200+ countries.
Tailor my resume for this job →Apply from your AI assistant
Connect hirly to Claude or ChatGPT and ask it to apply to this job. hirly tailors your resume, fills the employer’s form and asks before sending.
Some employer sites stop an application at a CAPTCHA or sign-in and hand it back with a link. Applying needs a paid plan. Works with any assistant that supports MCP.
hirly's read of this role
- Seniority
- Mid level
- Country
- DE
- Work mode
- On-site / unstated
- First seen by hirly
- 28 Sept 2026
Derived automatically from the posting. Upload your resume above to see how the role scores against it.
the posting
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
Listed on hirly, a job board. hirly is not the employer: NEURA Robotics is hiring for this role.
Similar jobs
- SDK Engineer - PythonSupabase · Remote, GlobalFirst seen 31d agoremote
- Robot Client SDK Engineer (human)Neura Robotics · Metzingen / RiederichFirst seen 50d ago
- Security SDK EngineerAppsflyer · KyivFirst seen 75d agoremote
- Senior iOS SDK Engineer, Objective-CVerve · Bangalore, IndiaFirst seen 33d ago
- Senior Mobile SDK EngineerTransmitsecurity · Tel Aviv-Yafo, Gush Dan, IsraelFirst seen 76d agoremote
Browse similar roles
Want this one?
Upload your resume and hirly rewrites it for this job and writes the cover letter — in about thirty seconds, before you sign up.
Tailor my resume for this job