Software Engineer
Backend systems Β· Cloud infrastructure Β· Tech enthusiast
I build backend systems that are boring in the best way β observable, predictable, and designed to age well. Currently focused on scalable architectures, distributed systems, and making complex things simple.
Building systems that scale, solving problems that matter.
Maersk β Copenhagen, Denmark
Leading platform modernisation initiatives and backend service optimisation for global shipping operations. Driving cloud migration, event-driven architectures, and quality engineering practices across a microservices ecosystem.
TDC Β· Tata Consultancy Services β Copenhagen, Denmark
Built and modernised backend systems for telecom infrastructure, ensuring high availability for mission-critical services. Specialised in event-driven architectures, automation, and cloud readiness.
Reduced backend processing times through architectural modernisation across global shipping operations.
Kafka-based architecture with sub-100ms latency and 50% faster deployments via optimised CI/CD.
Cut SonarQube issues by 85%, enforced quality gates, and increased test coverage across microservices.
Pioneered MCP server integration and agentic AI to simplify complex backendβdatabase workflows, accelerating developer productivity across 7,000+ stored procedures β using Claude Sonnet 4.5 and GPT-5 for intelligent code generation, testing, and documentation.
Java (8β21), Spring Boot, REST, SOAP, Microservices, Event-driven architecture, Kafka, Integration & Component Testing
MS SQL, MySQL, PostgreSQL, MongoDB, Flyway, schema migrations, API-to-database abstraction (7,000+ stored procedures)
Docker, Docker Compose, Azure, Git, GitHub Actions (CI/CD), Kubernetes, Terraform, SVN
OpenTelemetry, Prometheus, Grafana, Loki, SonarQube, JUnit, Mockito, TDD
Java Β· Python Β· JavaScript Β· SQL Β· Go
MCP servers (MSSQL, Atlassian), Claude Sonnet 4.5, GPT-5 β workflow automation and LLM-assisted engineering
Thoughts on engineering, systems, and building things that last.
The best systems are the ones you can explain in a few sentences. Complexity is easy β anyone can add another service, another queue, another layer. Simplicity requires discipline, restraint, and the courage to say no.
PostgreSQL. Redis. Python. These aren't exciting choices. But they're reliable, well-documented, and proven at scale. Save your innovation tokens for problems that actually matter.
Monitoring tells you that something is wrong. Observability tells you why. Build systems that explain themselves: structured logging, distributed tracing, correlation IDs.
Not how many algorithms you've memorised. I care about how you think, how you communicate, and how you approach problems you haven't seen before. Can you break down a complex system? Do you consider trade-offs?
Every few months, someone proposes using Redis as the primary datastore. Databases guarantee durability. Caches optimise for speed. These are fundamentally different problems β use the right tool for each.
The goal of a code review isn't to catch bugs (though that's nice). It's to share knowledge, align on patterns, and build better engineers. A good review makes the whole team stronger.
Moments captured, places remembered.
When I'm not writing code, I'm usually behind a camera or planning the next trip. Photography taught me patience and perspective β two things that make me a better engineer. These are some places I've been, stories I want to remember.
Three weeks in the mountains. No cell service, no email β just trails and clouds. Captured sunrise at 14,000 feet. The air was thin, the light was perfect.
Cherry blossoms, temples, and quiet streets at dawn. Kyoto reminded me that beauty doesn't have to be loud β a lesson I try to apply to code too.
Midnight sun, northern lights, waterfalls. Iceland is a photographer's dream β and a reminder that nature operates on a completely different scale than we do.
Moody skies, ancient castles, and landscapes that felt pulled from another era. Waiting hours for the right light is meditative β you can't rush it, you can't force it.
Slow boats, palm trees, sunsets that looked unreal. Kerala is where I learned to slow down. Not everything needs to be optimised for efficiency.
Mountains, lakes, endless hiking trails. Photographed the Milky Way for the first time here β clear skies, minimal light pollution, and a reminder of how small we are.
I shoot mostly with natural light, minimal editing. Sony Ξ±7 III, 24-70mm for versatility, 85mm for portraits. Less gear means more focus on the shot. The same principles I apply to code: clarity, restraint, and intention.