I build the infrastructure companies trust to run AI.
AI product engineering and infrastructure-as-code, for organizations that need real governance — not a demo.
origin
before code, systems.
before i wrote a line of code, i studied how institutions work — universities, companies, the informal rules that hold an organization together when nobody’s watching. that turned out to be the right training for what i do now.
these days the hardest part of any real ai adoption was never the model. it’s the governance around it — who’s allowed to use it, what data it can see, what happens when it’s wrong. that’s a sociology problem wearing an engineering costume, and it’s the one i’m best at.
signal history
before frameworks, and after.
i started building interfaces before "frontend framework" was even a settled term — jquery, hand-rolled state, css that fought you every step of the way. then came the framework decade: angular end to end, enough react and vue to be dangerous, ngrx and redux for state that needed real discipline, component libraries and design systems instead of one-off pages, and tests, performance and accessibility that had to hold up in production — not just look right in a demo. i designed as much as i coded too — years of hands-on figma and adobe xd work built the instinct for what belongs in front of a user, even though these days that means reading a spec fluently, not drawing one, because a technically correct interface nobody wants to use isn’t actually done.
that decade taught me the thing a lot of ai-first engineers skip: taste. knowing when a pattern is right for the people using it, not just correct on paper. now the tools have changed again — i build with ai assistance the way i once learned to build with frameworks, and the shift feels familiar rather than threatening, because i’ve already lived through one generational rewrite of how this work gets done.
the foundation
10 years of frontend, first.
Frontend & Product Engineering
A decade shipping production interfaces — Angular, React, Vue, state management that had to hold up, micro-frontend systems that scaled past one team, testing, performance and accessibility built in from the start — with the design sense to know what actually belongs in front of a user.
what he runs now
Four channels on top of it.
Systems Architecture
What you build AI on top of, if it’s going to hold up — system boundaries documented arc42-style, not diagrams that go stale after the workshop.
AI Product Engineering
Designing and shipping LLM-powered products — retrieval-grounded assistants and agentic workflows that get more accurate the more they’re used.
Infrastructure as Code
Provisioning and running the infrastructure AI products depend on — reproducible, auditable, built to survive an audit, not just a demo.
Governance & Sovereignty
Building the policy layer that lets a company set its own rules for AI instead of inheriting a provider’s.
system spec
Stack.
ai / llm
- LLM & agent integration
- Retrieval-augmented generation
- Self-learning vector retrieval (Postgres)
- Policy & compliance engines for LLMs
- Multi-provider model routing
infrastructure
- OpenTofu
- Bicep / ARM
- Docker
- Kubernetes
- CI/CD pipelines
- Azure
- Self-hosted infrastructure (own cloud, Germany)
- Software architecture & documentation (arc42)
frontend
- TypeScript / JavaScript
- React
- Angular
- Vue
- State management (NgRx, Redux, signals)
- Component architecture & design systems
- Micro-frontend architecture
- Testing (unit, integration, e2e)
- Performance (Core Web Vitals)
- Accessibility (WCAG 2.1 AA)
- Node.js
craft
- Design literacy (reads a Figma spec fluently)
- Technical leadership & mentoring
transmission log
Record.
Senior Software Engineer at Makonis
Responsible for front-end architecture and, increasingly, for the AI systems and infrastructure-as-code behind our products — including applied work on real-time governance and policy enforcement for LLMs. I mentor junior developers and work directly with clients, turning ambiguous requirements into production systems.
Full-Stack Engineer at Sascha Wolff
Front-end (mostly Angular) and back-end (Node.js, MongoDB) on a small, senior team — the training ground for owning a problem end-to-end instead of a single layer of the stack, across every stage of the product cycle.
Co-founder of BreakfastClub U.G.
Financed through a one-year scholarship by Forschungszentrum Jülich, we built an application connecting local companies with breakfast providers.
Co-founder of Kusuri Company
We adapted the PillPack model from the US for the German market. The proof-of-concept performed well; we ran into legal obstacles that ended the project.
Master of Arts in Sociology
Westfälische Wilhelms-Universität Münster. Analysis of the social structure of modern institutions and organizations. Worked as a research assistant to Dr. phil. Gallina Tasheva.
Bachelor of Arts in Politics and Society
Katholische Universität Eichstätt-Ingolstadt. Politics and society, focused on organizational and industrial sociology. Worked as a research assistant to Prof. Dr. Joost van Loon.
why work with him
you get someone who shipped production frontends for a decade, designed before he built, and spent the last few years turning ai from a novelty into infrastructure a real organization can trust — not three different people you’d have to hire separately.
He translates instead of picking one discipline and ignoring the rest. That’s the whole signal.