Writing · Behavioral
Stories
One story per principle: a call made in ambiguity, a bet that paid off, a bet I almost made, the hardest technical decision I have owned, and a time I grew someone. Each one is the version I would tell in an interview: context, scope, the call I made and the number that came out.
- When the rules had no ownerThe hard part of a rating-engine re-platform isn't the engine — it's that nobody in the building can tell you what the rules are. The path forward isn't a spec. It's a chair next to the actuary.
- Caching for correctness, not speedEvery outside reviewer told me to scale the database. I bet the cache was load-bearing for the contract — not just the latency — and that's why it worked.
- The job-per-table bet I almost madeI spent two weeks defending the obvious design before I noticed I was the one defending it. The real failure wasn't the architecture — it was how long I waited to change my mind.
- When the cache becomes the contractMoving the source of truth from Aurora to DynamoDB for a regulated workflow is the kind of decision that looks reckless on a whiteboard. The wrong call would have shipped duplicate clearances against real customer money.
- The shift from triage to root causeThe fastest way to grow an operations engineer isn't a training plan. It's to stop rewarding the work that keeps them stuck.