Writing

How we replaced a static rule-based system spread across microservices with a real-time, Flink-driven risk engine at N26 — and what we learned.

A product engineer brings a small tooling idea to platform. The default response — no, not now, here's why it won't work — builds a wall. There's a better one.

I used to relaunch the app five times to check one change. TDD felt like homework until the feedback loop clicked — now tests are how I think, not what I do after.

Code freezes feel like arbitrary bureaucracy — until you're the one on call during the holidays. The real reason companies do them isn't what most engineers think.

Nine thousand containers, two hundred microservices, one licensed EU bank. An insider tour of how N26's stack actually worked — and the parts we hadn't finished yet.

You finished the program. Now what? Stop collecting certificates. Build something recruiters can click. Prepare like interviews are the job — because for a while, they are.