15 Years Building Platforms That Scale

The Short Version

I'm a Principal Software Engineer and Solution Architect. I work alongside CTOs and C-level leaders to define the big picture and roadmap, then make sure it actually gets built. My focus is taking products from ideation to something that scales. Microfrontend governance, build pipeline performance, cross-platform architecture, and the decisions that determine whether 200 developers can ship independently or spend their weeks in coordination meetings.

My work spans automotive, telecommunications, smart energy, and manufacturing. The common thread: large organisations with complex platforms that need to ship faster without breaking what already works.

I'm based in Germany and have worked with teams across Europe and the US.

What I've Learned

Most architecture problems aren't technology problems. They're ownership problems. Unclear module boundaries, shared dependencies nobody wants to maintain, build systems that punish teams for deploying independently. Fix the ownership model and the architecture follows.

The most valuable skill I bring isn't choosing between frameworks or designing a micro-frontend shell. It's walking into a platform with 200 active contributors, understanding where the friction is within a week, and making decisions that hold up six months later.

I speak the same language as UX designers, product managers, and engineers. That's rare, and it matters. Most architecture problems live at the seams between these disciplines. Being fluent in all three means I can bridge gaps that others don't even see.

I've shipped enough wrong decisions to know the difference between a conviction and a guess. When I'm certain, I'll say so. When I'm not, I'll say that too.

How I Got Here

I started as an IT apprentice at Hewlett-Packard, then studied computer science at Hochschule Furtwangen. My first professional years were at frog (global design consultancy), Jung von Matt/Neckar (creative studio), and Intuity Media Lab (innovation studio), building platforms for clients like Walter AG and Mercedes-Benz. Those three companies shaped my critical thinking, cross-discipline collaboration, and hands-on approach. That's where I learned that the real challenge isn't writing good code. It's making good code survive contact with ten teams and three continents.

I went independent because the problems I'm best at solving sit where UX meets product meets engineering. The architecture decisions that affect user experience. The technical constraints that shape product strategy. The build systems that determine team velocity. These problems cut across organisational boundaries. Fixing them from inside one team isn't enough. You need someone who can work across all of them.