Short Profile
Software and Systems Engineer / Software Architect with more than 25 years of experience in automotive, medical technology, industry, printing systems and robotics. Specialized in layered, reusable architectures with low coupling and high cohesion, as well as the targeted application of design patterns such as Facade, Proxy, Observer and Factory Methods. Multitasking · Multithreading · Concurrency · Synchronization · Inter-Process / Inter-Thread Communication · Real-Time Systems Software & Systems Architecture · Technical Leadership · Mentoring · Code & Architecture Reviews · ASPICE Audit Representation · Architecture Compliance · End-to-End Traceability · Coding & Architecture Guidelines through ASPICE reviews and ISO compliance, with measurable reductions in development effort and Time-to-Market by up to 70%.
Strengths & Focus
- Architectures with 70%+ reuse , clear modularity with low coupling and high cohesion.
- Audit-proven: ASPICE reviews & ISO compliance, clear guidelines and coding standards.
- End-to-end mindset: from µC drivers and inter-processor communication to product and series maturity.
- High-performance diagnostic and data paths for real-time and non-real-time systems.
- UML/SysML with Enterprise Architect, bidirectional traceability; AUTOSAR integration via the Facade Pattern.
Footprints in Everyday Life
Many of my systems are in production today – charging electric vehicles, controlling motors and sensors, operating in high-performance printers, visualizing information in vehicles, or supporting laboratories and clinics. Not all of them carry a visible label – but they work precisely and reliably where it matters.
My Engineering Philosophy
During more than twenty-five years in software development, I have had the opportunity to work across a wide range of industries – from semiconductor manufacturing and railway technology to medical technology, industrial automation, renewable energy, measurement technology and automotive.
Although technologies, programming languages and development environments have continuously changed over the years, my technical approach has essentially remained the same.
I am interested in understanding complex systems, identifying architectural boundaries and developing reusable software components that simplify future development rather than merely solving the current problem.
For me, software architecture is not about making systems more complicated. Software architecture means making complex systems easier to understand, maintain and extend over the long term.
When I join a new project, my first goal is not to start writing code immediately. First, I want to understand how the system works, what constraints exist, and which architecture will enable future engineers to develop it more efficiently.
In my experience, good software is not measured by the amount of code written, but by how naturally it can still be understood, maintained and further developed years later.