> Markdown version of [/jobs/ext/399151-robot-client-sdk-engineer-human](https://www.wearedevelopers.com/jobs/ext/399151-robot-client-sdk-engineer-human). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Robot Client SDK Engineer (human)

- **Company:** Neura Robotics GmbH
- **Location:** Bielefeld, Germany
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), C++ (Programming Language), Client Server Models, Continuous Integration, Java Native Interface, Python (Programming Language), Apache Maven, Prometheus, Software Engineering, Systems Integration, Management of Software Versions, Data Logging, Doxygen, Backend, Sphinx, Build Tools, Graphql, Api Design
- **Published:** June 18, 2026
- **Apply:** https://de.indeed.com/viewjob?jk=d143df769e3674a5

## About the Role

Do you have experience in gRPC?, * 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

## Description

* 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


## Related Videos

- [Robots are coming into the wild! Full-Stack Robotics Engineers, be ready!](https://www.wearedevelopers.com/videos/479-robots-are-coming-into-the-wild-full-stack-robotics-engineers-be-ready)
- [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock)
- [Continuous Documentation for Your Code](https://www.wearedevelopers.com/videos/798-continuous-documentation-for-your-code)
- [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library)
- [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape)
- [Supercharge Agentic AI Apps: A DevEx-Driven Approach to Cloud-Native Scaffolding](https://www.wearedevelopers.com/videos/1604-supercharge-agentic-ai-apps-a-devex-driven-approach-to-cloud-native-scaffolding)

## Related Articles

- [Everything a Developer Needs to Know About MCP with Neo4j](https://www.wearedevelopers.com/magazine/604-everything-a-developer-needs-to-know-about-mcp-with-neo4j)
- [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)
- [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)
- [Dev Digest 108 - Git off my cloud!](https://www.wearedevelopers.com/magazine/407-dev-digest-108-git-off-my-cloud)