- Hands-on systems and middleware development
- Strong C++17 (or Rust) in systems context
- Experience on Linux/QNX or equivalent POSIX OS
- Exposure to automotive / safety-critical / deterministic systems
- Senior-level technical ownership and architectural reasoning
Kindly avoid sharing application-only or framework-driven profiles, as they will not progress further in our evaluation.
Additional Details
What we build
We develop a safety-critical middleware based on Eclipse S-CORE. We actively contribute upstream and build a commercial distribution on top. The platform includes core system capabilities such as communication (IPC, ABI), lifecycle management, diagnostics, orchestration, logging and persistency, networking and time synchronization, and security.
The system is interconnected and technically demanding. Decisions in one area affect others. This role requires someone who is comfortable operating in that kind of environment.
What we are looking for
Strong technical depth.
You understand systems, not just components. Concurrency, memory behaviour, determinism, interface stability and performance trade-offs are familiar territory.
Architectural judgement.
You can compare approaches, explain trade-offs clearly, and avoid overengineering. You think about maintainability and failure modes, not only feature completeness.
Hands-on execution.
This is not an abstract architecture role. You will read and write production code, review complex changes, and step into debugging when things do not behave as expected.
Cross-domain thinking.
You likely have a primary area of strength, but you are able to reason across boundaries. You understand how communication, lifecycle, diagnostics or security interact and where risks hide.
Safety awareness.
You recognize how design decisions affect robustness and system behaviour. You do not need to be a certification expert, but you need to take system integrity seriously.
Open-source maturity.
We work upstream. That means discussing design decisions publicly, reviewing contributions, and aligning rather than forking whenever possible.
What you will do
- Take ownership of a significant technical area (feature or cross-module scope)
- Shape architecture decisions and document the reasoning behind them
- Drive implementation, not just design
- Support upstream discussions and contributions
- Mentor engineers where needed, without turning into a people manager
- Reduce long-term technical friction rather than adding short-term patches
Experience we value
We care more about demonstrated capability than years on paper. Relevant signals include:
- Deep hands-on experience in C++17 or Rust in systems or middleware contexts
- Track record of designing and delivering non-trivial technical solutions
- Ability to debug complex, non-obvious failures
- Experience in distributed systems, safety-relevant or deterministic environments
- Open-source contribution history is a plus
- Clear and direct communication when discussing technical trade-offs
I hope you find the Job Description as per your interest.
Kindly share your acknowledgment on the same.