.jpeg)
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
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
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
Skills Required
- Proficient in at least two languages among Python, C++, Java (idiomatic async patterns and packaging).
- Hands-on experience with gRPC ecosystem and protoc/buf-based client generation (grpc-python, grpc-java, grpc-cpp).
- Experience publishing multi-language packages and CI pipelines (manylinux pip wheels, PyPI, Conan/vcpkg, Maven Central).
- API design and compatibility expertise: semantic versioning, deprecation policy, client-server compatibility testing.
- Observability and telemetry experience: OpenTelemetry tracing, structured logging, Prometheus metrics across languages.
- Documentation tooling and delivery: Sphinx, Doxygen, Javadoc; auto-generated docs and example synchronization.
- Experience shipping client libraries used by external or internal customers (production-grade SDKs).
- Familiarity with language binding techniques (PyBind11, JNI, SWIG, cppyy).
- Familiarity with robotics or industrial control (latency/timing semantics).
- Authored OpenTelemetry instrumentation libraries or equivalent cross-language telemetry work.
- Working knowledge of ROS 2 client library design (rclpy / rclcpp).
- Experience creating SDK reference apps, onboarding materials, and developer examples or tutorials.
What We Do
NEURA Robotics is a German high-tech company founded in 2019 in Metzingen near Stuttgart with the vision to revolutionize the world of robotics. More than 180 team members from over 30 countries are working on advanced technologies in the fields of environmental perception, drive and control technology, material science, mechanical design, and artificial intelligence. We are expanding the cognitive capabilities of robots and make breakthrough advances in a variety of areas to bring robots and humans closer together, making many areas of work more attractive, creative, and social again. That's why everything we do runs under the guiding principle "we serve humanity". In a very short period of time, NEURA Robotics has developed robots and technologies that are characterized above all by their outstanding performance as well as safe and human-centred way of working. In this way, a wide variety of application fields can be covered, from intelligent production to medical technology. All major robot components are developed and designed in-house. Imprint: https://www.neura-robotics.com/legal Privacy: https://www.neura-robotics.com/privacy
