First or lead engineer
Take a product from idea to production, and set up the architecture, tooling and team habits it will live with for years.
Senior software engineer. Usually the first or lead engineer on a product: I set up the architecture, keep it boring, and stay long enough to defend it.

ask
It knows my work, my terms and my limits, and it passes real enquiries straight to me.
An AI assistant answers from what Marc wrote about himself and passes enquiries on to Marc. Datenschutz
what I do
Take a product from idea to production, and set up the architecture, tooling and team habits it will live with for years.
Multi-tenancy, service boundaries, independent deploys, migrations off frameworks that stopped fitting. Backwards-compatible, while production keeps running.
Queues, idempotent consumers, event sourcing and CQRS where correctness matters, like payroll that must reproduce any past month exactly.
Real-time voice agents, LLM tool calling and WhatsApp integrations, with DSGVO and EU data residency designed in.
selected work
Self-taught, with a degree in entrepreneurship and a founder's habit of owning the whole product. Each project opens into the context, the decisions and the stack.
how I build
My LinkedIn headline, borrowed from The Grug Brained Developer by Carson Gross. It is a joke. It is also the method.
Postgres, a monolith, one server, until the problem proves it needs more. Distribution is a cost; pay it where it earns its keep.
Traces and a baseline before anyone says "fixed".
Pure functions, honest types, code a new teammate can follow on day one.
Test-driven by default. It is how I move fast without breaking what pays the bills.
DSGVO, EU hosting and the AI Act shape the design before the first line of code.
Claude Code drafts, I review until I own every line. Faster, same standard. Where the client agrees, of course.
stack
working together
contact
I read and answer every message myself.