The moment I discovered my mission was actually a frustrating one.

I was deep in the weeds building a multi-agent LLM system, wiring up tools, managing context between agents, and I hit a wall. Not because the technology couldn't do what I needed. But because the documentation was written for someone who already understood it. There was no demo that showed the real use case. No one who'd been in the same trench and could just say: here's what actually works.

I figured it out eventually. But I kept thinking, how many developers just give up right here? That moment stuck with me. And it pulled me toward DevRel.

I earned a double Master's from Technische Universität Berlin and KTH Royal Institute of Technology in Stockholm, two of Europe's top universities, then built data infrastructure at Babbel in Germany before founding two AI startups in San Francisco. Three continents, four languages, and somewhere along the way I became someone who genuinely can't stop building things and can't stop wanting to explain them.

That combination, the engineer who also obsesses over how knowledge travels from one developer to another, is what makes me feel like DevRel is where I belong.

I've been living this work for the past year. I co-organized AI events in SF that drew 500 developers. I've run product demos with a 60%+ demo-to-trial conversion rate. I've written the technical docs that cut onboarding time by 40%. Every single time, the thing that mattered wasn't the feature, it was how clearly someone understood what they could do with it.

That's what drives me: closing the gap between what a technology makes possible and what a developer actually feels capable of building.

If you're building AI tools, DevRel teams, or developer communities, I'd love to connect and swap notes on what actually helps developers get unstuck.