Software in safety- and security-critical domains has to be right the first time. Late architectural changes, compliance gaps or security flaws are expensive, and they are often discovered only when a release is close.

I help teams avoid that with independent reviews and practical, hands-on guidance. My advice is based on more than ten years of building production software in automotive, embedded, banking and energy, from Level 3 automated driving software for the BMW iX to secure client-server systems in the energy sector.

What I can help with

  • Architecture reviews: assessing structure, module boundaries, interfaces and data flow; identifying scalability, maintainability and performance risks; and delivering prioritised recommendations, supported by UML models where useful.
  • Code quality and static analysis: building a realistic MISRA C/C++ compliance strategy, triaging Coverity and other static analysis findings, handling deviations properly and integrating analysis into your CI pipeline.
  • Security-critical software: designing secure client-server communication with TLS/SSL, certificate authorities and certificate chains, and reviewing security concepts for embedded products such as Root of Trust solutions.
  • Automotive development processes: aligning software engineering with Automotive SPICE (SWE.2 to SWE.5), including detailed design, unit test specifications and component and integration testing.
  • Engineering workflows: setting up or improving CI/CD pipelines, code review practices, version control strategies and documentation standards that teams actually follow.
  • AI-assisted development: introducing tools such as Claude and GitHub Copilot in a responsible way, with clear workflows, review guardrails and realistic expectations.
  • Team enablement: mentoring engineers, running design reviews and helping teams adopt new practices sustainably.

Standards I work with: Automotive SPICE (SYS & SWE process groups), ISO 26262, MISRA C:2012

How I work

  1. Discovery call: a short conversation to understand your product, goals, constraints and timeline.
  2. Assessment: a focused review of the code, architecture or processes in scope, together with interviews with the people who work with them every day.
  3. Recommendations: a concise report with findings ranked by impact and effort, and concrete next steps instead of generic advice.
  4. Support (optional): hands-on help implementing the changes, from pairing with your engineers to taking ownership of specific improvements.

Typical engagements

  • An independent architecture or code review before a major release or audit
  • Getting an embedded project ready for MISRA C/C++ compliance
  • Designing and implementing a secure communication layer
  • Acting as a technical advisor for a small team over several months

Why work with me

  • Proven in production: software I designed runs in series vehicles such as the Audi e-tron and BMW iX.
  • Innovation track record: inventor of a camera calibration method granted as a patent in Europe, the US, Japan and China.
  • Leadership experience: led an embedded software team and acted as the main technical contact for customers.
  • Cross-industry perspective: lessons from automotive, semiconductor, banking and energy, applied where they fit.

Let’s talk

Have a project that needs a second opinion or a steady technical hand? Tell me about it and I will get back to you.