Production engineering, end to end.

I build software for teams that need the backend to stay understandable after the launch week.

That has meant operational monitoring software for industrial IoT machines, a clinical imaging data platform, and more recent mobile-commerce work where cart, checkout, CMS, and loyalty behaviour had to stay consistent across markets. The common thread is not the industry. It is the need for systems that behave predictably under real operational constraints.

How I work

I am most useful where architecture and delivery meet. I like defining boundaries early: which service owns a rule, where authorisation is enforced, what gets versioned, and which parts of the system are allowed to fail noisy instead of silent. The case studies on this site are structured around those calls on purpose.

I spend most of my time in TypeScript/Node.js and Python, with PostgreSQL, AWS, queues, and production diagnostics close behind them. I still work across the full stack when the product needs it, but the center of gravity is backend design, APIs, data flow, and operability.

Working together

I work with product teams through fixed-scope technical reviews, delivery and recovery sprints, focused MVPs, and longer independent delivery partnerships. I am based in Munich and work hybrid in the region or remotely across European time zones, with selected US engagements where working hours overlap. What stays constant across all of it is the goal: leaving systems more legible, measurable, and supportable than I found them.