Software without headlines.Except one:it works.
I’m Christian, senior software engineer and cloud architect with 0+ years in production systems. I take responsibility where architecture, operations and code collide, and deliver solutions that keep running without me.
Four disciplines.
One responsibility.
I don’t spread myself across everything. These four are my day-to-day, and I have shipped systems into production and beyond in every one.
Cloud-Native Architecture
Production-ready platforms on Kubernetes & AWS, without YAML spaghetti.
I design and build cloud infrastructure that holds up under load and runs without heroics. Focus areas: EKS, Terraform, FluxCD, observability. No lift-and-shift, but architecture that uses the cloud where it actually pays off.
Backend Engineering
Java & Go for systems that digest millions of events per day.
Spring Boot, Quarkus, Go microservices. Event-driven architectures with Kafka, clean REST APIs, distributed systems that don’t become interesting only at the first load test.
Frontend that matters
React & Next.js, when the backend needs a face.
When the frontend is part of the product, not an afterthought: SSR, PWA, realtime via WebRTC. I write frontends a backend engineer can still read two years later.
AI Integration
Agentic workflows, OCR & LLM pipelines. Pragmatically in production.
Not model research, but production-grade integration. Agentic workflows with tool-use and eval loops, OCR pipelines, vision services, LLM-assisted automation. What ships: low latency, predictable cost, clear failure modes.
Clients across
7 industries.
A selection from 12 production engagements since 2010, from mid-cap to DAX corporates. Every logo stands for a concrete project, not a business card.
Broadly placed, not arbitrary.
Shares weighted by engagement duration. Focus on regulated industries with high demands on scalability, availability and compliance.
On the bench, every day.
Tools are means, not identity. The ones below have proven themselves in production: repeatedly, across industries, under real load.
Four lines I measure code against.
Boring tech, where possible.
Postgres before Mongo. Kafka before EventBridge. Proven tools beat the latest GitHub trend every time.
Let’s talk about
real problems.
Available for new projects from 1 August 2026. Inquiries answered within 24 hours with an honest read on whether the project fits.