Remote-First Works. But Not With Everyone.
Why remote-first is a people problem, not a location problem — and the Goal Owners framework that makes distributed teams actually work.
Read More →
Fourteen years building software, ten leading distributed teams — hands-on with Go, org design and agentic AI.
I'm a software engineer and technical leader — fourteen years building software, ten of them leading engineering teams across cybersecurity, health tech and enterprise data.
As a German living in Denmark, my expat journey has shaped how I think about cross-cultural collaboration and remote team dynamics — and taught me the value of diverse viewpoints and inclusive environments where good ideas can come from anywhere.
I've worked remote-first since 2014 and believe in it more than ever in the AI era. When AI tooling measurably accelerates how teams deliver, the limiting factor isn't where people sit — it's whether they deeply understand the mission and are genuinely committed to the outcomes.
My leadership philosophy centers on ownership, continuous learning, and decisions that balance innovation with practical delivery. Great technology emerges where technical excellence meets human understanding.
Strategic thinking paired with hands-on engineering — grounded in what actually works for distributed teams.
Data-driven decisions through open discussion with all stakeholders. Technical choices emerge from transparent dialogue between engineering, product and business — alignment without lowering the bar.
Structured experimentation with a clear-eyed view of AI: having led an org-wide shift to agentic engineering, I care as much about where AI shouldn't decide as where it should.
Autonomous distributed teams built on transparent, honest and clear communication. Remote works when shared understanding and genuine commitment are created deliberately — not assumed.
High standards through code review, architecture discussions and continuous learning. Technical debt is a strategic choice, not an inevitability.
Fourteen years of building software, ten of them leading engineering teams — remote-first, across cybersecurity, health tech and enterprise data.
Leading the engineering organization of a cybersecurity company, reporting directly to the CEO. Drove the org-wide shift to agentic AI engineering: ~90% Claude Code adoption on an AI policy I authored, lifting PR throughput ~75% on a DORA baseline I stood up — with change-failure rate back at baseline within two months.
External architecture advisor and hands-on engineer for five clients across five domains — scoping legacy rescues and greenfield MVPs, then delivering them. A real-time ad server built from scratch in Go in 2021 is still in production and under active development 4+ years later.
Built the engineering team of a Berlin security startup from zero to six — with every hire staying for the full three years. Without a dedicated product function, brought three security and compliance product lines from concept to market — making previously enterprise-only web security available to the SMB market.
Co-architected the DataSpace cloud file-storage product family, stabilized and took over the backend of a teleradiology "Radiology-as-a-Service" platform, and built a fully automated CI/CD pipeline in 2015 — pre-Docker, pre-GitHub-Actions.
Leading teams with expertise across Golang, JavaScript/TypeScript, and Java ecosystems, specializing in microservices architecture and cloud-native solutions.
Why remote-first is a people problem, not a location problem — and the Goal Owners framework that makes distributed teams actually work.
Read More →Learn how to build fast, scalable web applications without traditional databases using modern caching strategies, in-memory persistence, and smart architecture patterns.
Read More →