Aachen, Germany · Remote EU · UTC+2Hire me

I Modernize Systems 
That Cannot Go Down. 

Senior backend and platform engineer in Aachen. I take legacy systems into services, teams into modern practice, and platforms into production that I then operate: Kotlin, Spring Boot, Kubernetes, TypeScript and React. Where teams build with AI, I build the guardrails that keep what ships defensible. Open to senior roles across the EU and remote worldwide.

11+

Years shipping production

50+

Enterprise tenants served

100+

Sites ranked to Google page one

15

Person team modernized

12

Applications in production

Backend · Platform & Kubernetes · Frontend · Legacy Modernization

Aachen · Remote worldwide · Relocating within Germany · Permanent or contract

Complex is cheap. Simple takes years.

Five products. In production. Anyone can demo. These run: two live with real users, three shipping toward launch, each with a written case study one click away.

$status --all5 products · 2 live with real users

He is an excellent mentor, always willing to share his knowledge and help others grow. No matter the challenge, he always finds efficient and effective solutions. He would be an invaluable asset to any organization.

Richa Deshpande · Worked with Edvard on the same team

I personally learned a great deal from him about cloud architecture and Spring Boot, thanks to his patient and thorough explanations. I highly recommend Edvard to anyone looking for a talented, driven, and collaborative software developer.

Sebastian Kaiser · Worked with Edvard on the same team

Beyond his brilliant work as an engineer, he is a natural leader and an indispensable team player. Any team would be lucky to have him on board.

Nikita Moritz · Worked on the same team, reported to Edvard directly

Still running. That's the point. Development started May 2025, live in 2026, running since. The receipts sit in the card below.

DanceClub

danceclub.app

Production platform for social dance events, from discovery through to organizer operations.

Modular monolith · 65 Gradle modules · 10 Postgres schemas · 4 Next.js frontends

Self-hosted end to end. CI/CD on every push. No on-call rotation, no SRE team, it simply hasn't needed one.

Development started May 2025. Live in production since 2026.

$uptime danceclub.applive since 2026

65

Gradle modules

10

Postgres schemas

104

Published events

15

Localized markets

One monolith in. Twelve services out. Zero downtime. Not my product, my employer's: a German B2B SaaS in Aachen. Three years leading the decomposition and mentoring the team that runs it.

Vaadin monolith

one deploy, all risk

50+ tenants

zero-downtime cutovers

Gypsilon Software GmbH · Aachen · Apr 2022 to Jan 2025 · Led + mentored

The full track record

Four things you get on day one. Not a list of tools. The scale I have already run, the ownership I already carry, and the range that lets me take the whole problem instead of a slice of it.

50+

Tenants in one system

Invoice processing automated end to end for 50+ enterprise tenants: a scanned document or an inbound email through issuer and tenant resolution to an approved payment. Mercedes-Benz is among the clients running on it.

Multi-tenant scale, in production
15

Person team taken off legacy

Moved a team of legacy developers onto Spring Boot and a two-week release cadence, mentored three engineers directly, and introduced the quality gate that cut code-quality violations by more than 60%. Also took the company off-premise to the cloud.

Modernization the team kept using
12

Applications built and operated

Kubernetes, GitOps and the observability under it across 8 Linux hosts, as the sole operator and on call for all of it. That includes catching a 13-day silent certificate renewal failure that every probe had reported as healthy.

I run what I ship
100+

Sites ranked to page one

A decade of building things people actually find and use, from client SEO work early on to a platform across 15 localized markets with roughly 1,500 indexed pages. I know what happens to software after the deploy.

Across the full career

AI writes the code now. So what are you hiring for? The honest answer, with receipts. Generating code got cheap. Deciding what survives, and being accountable when it doesn't, did not.

01

Anyone can demo. Almost no one can keep it running.

AI gets you to a working demo in an afternoon. It doesn't write the migration, notice that backups stopped six weeks ago, or carry the pager at 3am. Production is a discipline, not a deploy button: tests against real databases, migrations, monitoring, rollback plans, the boring parts that decide whether you still have a product in year three.

12 apps on Kubernetes · GitOps · full monitoring stack
02

AI is brilliant in an empty repo and useless in yours.

Your core system carries fifteen years of undocumented business rules, and the revenue flows through it. That context doesn't fit in a context window, and the risk tolerance is zero. Brownfield work is judgment, sequencing, and nerve. It's the work most engineers avoid and the work I'm best at.

12 services · 50+ tenants · zero downtime
03

I don't just use AI. I direct it, and I teach teams to.

Two years building agent workflows, MCP servers, and correction protocols. My own agent infrastructure runs my deployments, and I built PLMHub so AI-generated systems stay understandable to the humans who own them. One person with Copilot gets faster. A team with the right discipline compounds.

2 years in the loop · MCP · agents · PLMHub

Three steps. Hire me or contract me. The same discipline either way: a conversation, working software in week one, and knowledge your team keeps.

01
Step 1

Conversation

Thirty minutes on your actual problem. Role, contract, or rescue, we scope it straight.

02
Step 2

Ship in week one

A real ticket in the first week, not onboarding theater. Decisions documented as I go.

03
Step 3

Production, together

Working software in production and a team that understands it. No knowledge silo, no PDF.

Sounds like your team?

A 30-minute call, no pitch. Hiring, contracting, or just a hard problem, bring it.

Replies within 24 hours · Aachen, UTC+2