Technical design & architecture

Architecture decisions don't pay off in the demo. They pay off two years later, when a system scales, a new team takes it over, or another market gets added. I design architectures to hold up at that point: with clear ownership, documented patterns, and a structure built for the growth you can already see coming.

A design engagement usually starts with an assessment of existing systems and requirements, followed by working out the target architecture, including a scaling strategy, cost model, and security requirements. For LLM-based systems, that also means model selection, retrieval infrastructure, and operating cost, which I approach with the same rigour.

I've sharpened this approach across a range of projects. For Coca-Cola European Partners, I designed and developed a scalable B2B e-commerce platform rolled out across 12 European countries, providing a shared technical foundation while accommodating the individual requirements of local business units. For the REWE Group, I built a central frontend pattern library that standardized development across multiple digital products. And for tough solutions, I built the frontend of a central platform for interactive video streaming and live event formats that later served as the technological foundation for a subsequent implementation at Vodafone.

That experience of designing systems that hold up across countries, teams, and follow-on projects is what I now bring to the architecture of LLM and agent applications.