Technical Skills
Languages
AI-assisted Engineering
Tools & Infra
Methodologies
Experience
Specialist Software Development (Role: Tool Owner, ISO 26262)
01.2020 — PresentProduct responsibility for a code generation tool (Scala) for the Neue Klasse, comparable to an Area Product Owner. “Tool Owner” is an official add-on role within the ISO 26262 qualification. Gathering and aligning requirements from stakeholders of several teams, refining them with the team and prioritizing; architecture, budget, risk assessment, interface agreements with other tool owners and technical leadership of the team.
- Rebuild instead of extending the predecessor: Only the execution framework was kept; data model, checks and exporters were newly designed.
- Mandatory step in the merge gate of 5 ECU projects (+1 partially), used in 2 corporate divisions (Driver Experience, Powertrain).
- Input format for function developers designed by myself, including a generated JSON Schema; input and processing deliberately decoupled (backward and forward compatibility as an architectural decision).
- Approx. 75 technical and functional checks and 7 output formats; runtime per function typically under 1 minute (approx. 530 functions).
- Tool qualification according to ISO 26262 (TCL3): designed the test concept, implemented it with the team, responsible for the evidence; qualification anchored in the Definition of Done.
- Over EUR 3 million budget (2020 to today, cumulative) including a re-tender: statement of work, technical vendor evaluation, award recommendation to Procurement.
- Technical leadership of up to 6 people at 3 locations (today 3 + me); built up an offshore team in India and phased out the external vendor without interrupting operations or development.
- AI: Agent skills for the tool’s own input format; contribution to a corporate-wide initiative evaluating AI coding agents.
- Knowledge transfer: “GitHub for non-developers” training for managers (3 runs, approx. 50 participants); weekly community meeting with representatives of all ECU teams.
Scrum Master
10.2017 — 12.2019Scrum Master for a team of approx. 13 people (expert ordering platform). Introduced the classically structured team, which did not develop software itself, to an agile way of working; the purpose of the agile ceremonies was largely understood.
Software Engineer, Project Manager, Scrum Master, Java Trainer
12.2011 — 07.2017IT service provider; clients included Deutsche Rentenversicherung and DATEV.
- Developed batch applications for reports to the Deutsche Rentenversicherung, web-based Java full-stack applications for readable display of these and similar messages, and internal portal systems.
- Later project lead and Scrum Master in small teams (approx. 2 people including myself).
- Retraining COBOL developers as Java developers as a Java trainer: approx. 5 trainings, approx. 100-120 developers.
Student Research Assistant (HiWi)
05.2008 — 10.2011Department: Competence Center High Performance Computing Areas: scheduler for grid/cloud computing, consumer strategies in the smart grid.
Featured Projects
Code Generation Tool for ECU Software — Rebuild
Internal / ConfidentialProduct responsibility for a part of a code generation tool at BMW that connects MATLAB-based function development with the ECU: developers describe in JSON what would otherwise be hand-written integration code, and the tool generates the C skeleton and the A2L content per package. With the Neue Klasse and the addition of Powertrain development, the input format became far more complex, so the tool was rebuilt instead of extended: only the execution framework of the predecessor was kept.
I designed the input format for function developers myself, with a generated JSON Schema and a decoupled internal data model. Approx. 75 checks catch errors in the pull request instead of after a multi-hour build at the vehicle. Qualification according to ISO 26262 (TCL3) is part of the Definition of Done, so every software version is qualified. Runtime per function is typically under 1 minute (approx. 530 functions).
Mandatory step in the merge gate of 5 ECU projects (+1 partially), used in 2 corporate divisions. Approx. 75 checks, 7 output formats, qualified according to ISO 26262 (TCL3).
Offshore Build-up and Vendor Phase-out (2024–2026)
Internal / ConfidentialFurther development of the code generation tool ran through an external vendor in Munich (3-4 developers, later 2 plus a bridgehead). The goal was to switch to internal colleagues in India.
I started in early 2024 with one colleague; as performance did not materialize, the collaboration was ended. For the new staffing, the contact person in India pre-selected candidates and I conducted the decisive technical and personal interviews myself. Two colleagues were selected (on board since approx. early 2026); an experienced colleague mentors the second one on site because of the time difference. The new colleagues take on small and medium tasks, with reviews still done by me.
External vendor fully phased out; operation and development continued without interruption. Team today: 3 people + me (up to 6 people at 3 locations during the transition).
0x08.de Architecture (This Portfolio)
A highly optimized, serverless static site demonstrating modern web capabilities and architectural constraints.
Built with Astro and Tailwind CSS to guarantee maximum performance. The repository also acts as a public demonstration of a zero-JavaScript anti-scraper email solution and a localized, type-safe content management approach without a CMS.
Achieved 100/100 Lighthouse score while maintaining strict DSGVO (GDPR) compliance with zero third-party tracking.
Behind the Build
This portfolio is itself a technical demonstration — a live proof-of-concept for the engineering standards listed above.
Pure Static HTML
Zero client-side frameworks. Every page is pre-rendered at build time by Astro.
Zero External CDNs
No Google Fonts, no analytics scripts, no third-party network requests.
100/100 Lighthouse
Performance, Accessibility, Best Practices, SEO — all perfect scores.
DSGVO Compliant
No cookies, no tracking, no consent banners needed.