NEURA Robotics
Robot Client SDK Engineer (human)
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.9M 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
Your Mission & Challenges
protoc + buf toolchain for client-side code generation; CI pipelines regenerate clients on every proto change
Python client SDK: idiomatic wrappers with context managers, async/await variants, IDE completion stubs, pip wheels published to internal PyPI
C++ client SDK: RAII channel lifecycle, async, language-idiomatic exception hierarchy, Conan/vcpkg packages
Java client SDK: builder patterns for requests, CompletableFuture, Maven Central artifacts
Channel lifecycle handling across languages: timeouts, deadline propagation, reconnection logic, TLS/mTLS configuration
gRPC status to language-idiomatic exception mapping: hierarchical exception types with semantically meaningful subclasses
Client/server version-skew compatibility tables—published policies on client-server version support, automated compatibility tests
Semantic versioning aligned with the platform architect, deprecation policy enforcement with linter warnings, migration guides
Simulation-mode toggle inside the client: same proto interface, simulation backend for offline app development
Observability hooks per language: structured logging, OpenTelemetry tracing context propagation, Prometheus client metrics
Reference example applications per language demonstrating canonical patterns: pick-and-place, mode switching, fault recovery, telemetry streaming
Auto-generated documentation per language: Sphinx (Python), Doxygen (C++), Javadoc (Java); examples kept in sync with API surface
Internal customer onboarding: skill bundles, evaluation harnesses, R&D notebooks, demo apps—all start from your reference template
RFC co-review with the Robot Platform Integration Engineer on every proto change
What we can look forward to
Developer experience with platform SDKs—has shipped client libraries used by external or internal customers.
Proficient in at least two: modern Python (typing, asyncio, pyproject.toml/wheels), modern C++ (17/20, async patterns, build systems), Java (CompletableFuture, Maven build).
Hands-on with gRPC ecosystem: protoc, buf, grpc-python, grpc-java, grpc-cpp—has implemented production clients.
Multi-language packaging: manylinux pip wheels, Conan or vcpkg recipes, Maven Central publishing—experienced with full CI pipelines.
API design fluency: gRPC/REST/GraphQL, semantic versioning, deprecation policy authorship, backwards-compatibility analysis.
Documentation tooling: Sphinx, Doxygen, MkDocs; capable of owning end-to-end documentation deliverables.
Cross-language async patterns: understands trade-offs among sync, async, and streaming gRPC across languages and their ergonomic differences
Nice to have
Familiarity with robotics or industrial control to discuss latency and timing semantics with robot platform engineers
Experience writing language bindings for a native library (PyBind11, JNI, SWIG, cppyy)
Authored OpenTelemetry instrumentation libraries across multiple languages
Working knowledge of ROS 2 client library design (rclpy / rclcpp)
Written a developer-portal API reference or SDK tutorial series for external developers
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 32d agoremote
- Robot Client SDK Engineer (Mensch)Neura Robotics · Metzingen / RiederichFirst seen 50d ago
- Security SDK EngineerAppsflyer · KyivFirst seen 75d agoremote
- Senior iOS SDK Engineer, Objective-CVerve · Bangalore, IndiaFirst seen 34d 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