Staff Engineer — Embedded Systems & Middleware

Staff / Principal Software Engineer

Safety-Critical Middleware (C++17 / Rust)

We are looking for one strong individual contributor who can raise the technical level of a safety-critical middleware platform. This is not a headcount-driven hire. It is a deliberate search for someone who can shape architecture, write solid code, and make decisions that still make sense two years from now.

 

 

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

 

Why this role matters

One strong engineer at this level can influence the technical direction of the platform, reduce future maintenance costs, and strengthen our upstream position. We are intentionally prioritizing quality and long-term impact over short-term cost efficiency.