I'm Stefan. For the last five years at Red Hat I've worked across six products, and I keep ending up in the seams between them, the places where one team's decision quietly breaks another's.
Outcomes from public sources — Principled Technologies, TechTarget, Forrester.
One of these cases has a button labeled Fix that didn't fix anything. Another is an operation you can't undo halfway through. These are the five problems I'd want to be judged on. Each was a hard model long before anyone drew a screen.
Moving a running virtual machine between data centres with zero downtime, the first UI anyone had built for it.
Read the case → Cloud costs · ShippedFinance, IT operations and developers all needed it, so I built three views, because each of them thinks about cost differently.
Read the case → Server monitoring · ShippedThe old tool dropped 30–50 separate recommendations on you each morning; I grouped the related ones into a plan you could actually act on.
Read the case → Automation · ShippedThree tools, three teams, one shared workflow, and a button labelled "Fix" that finally does what it says.
Read the case → Access control · ShippedMost access-control tools quietly assume one type of administrator. I designed ours around three, and that decision reshaped the product.
Read the case →That's the kind of problem I like most. If it sounds like yours, say hello.