When no one agrees on the architecture and every sprint makes it worse, I help CTOs find clarity and get teams building again.
Principal Software Engineer and Solution Architect. I work alongside CTOs and engineering leaders to take products from ideation to production scale. Then I make sure the team can run without me.
I plan my own departure from day one. Success means the team can execute independently, whether that takes months or years to achieve.
What I Do
I help define the big picture and strategy alongside CTOs and engineering leaders, then roll up my sleeves and make it real. Architecture reviews, technical governance, platform decisions, and product direction. With 15+ years building platforms for companies like Siemens, Deutsche Telekom, and Mercedes-Benz, I can tell you which decisions will save you months and which ones will cost you years.
Diagnostic Clarity
The first week is spent understanding what's broken and why. I read the code, talk to the engineers, map the delivery pipeline, and tell you what I find. Root causes are often different from initial symptoms, which is why the diagnostic matters.
Architectural Decisions
Enterprise teams get stuck because architectural decisions require cross-team alignment, and it's often unclear who should make the final call on irreversible choices. I bring opinionated, battle-tested judgment. You get a clear path forward with trade-offs understood, not just a menu of options.
Planned Exit
Success means the interesting problems are solved and the team can execute without me. I train and enable the people I work with, build patterns that outlast my engagement, document the decisions that matter, and hand off to a team that's stronger than when I arrived.
What You Get in Week 1
The first week isn't just observation—it produces tangible output:
- A written assessment of where you are, what's broken, and what needs to happen next
- A clear breakdown of your upcoming decisions and what each choice will cost you
- An honest recommendation on whether I'm the right fit for the engagement (including when I'm not)
- If we move forward: a roadmap showing what gets built, in what order, and why
Week 1 ends with a clear picture of what's happening and a specific plan for what to do about it.