How I got here.
The non-linear path.
Before tech, I taught. This wasn't a detour. Every cross-team knowledge transfer, every AWS onboarding program I built, every VP briefing I simplified — this background is in all of it. Teaching forces you to find the explanation that actually lands, not the one that sounds impressive.
Joined a Java high-availability trading platform. Sprint completion was erratic. I took on the Scrum Master role alongside engineering, introduced explicit dependency mapping at planning, and built a blocker escalation protocol. Sprint completion improved 39% across 3 releases. The instinct to identify a gap, own it without being asked, and deliver a measurable fix — that pattern has repeated itself ever since.
Built predictive models on clinical health data, medical image classification with CNNs for cancer detection, and transaction fraud detection at scale. The medicine-adjacent work was deliberate. I still want to understand how systems fail and how to detect failure before it becomes catastrophic — whether that system is a human body or a distributed fleet of 6.85M health check endpoints.
Started writing production code. Built the consensus algorithm, the health analytics platform, the cryptographic authentication system. Then grew into owning programs at a scale where writing code became one tool among many. Sole TPM on the $4.4B New Zealand region build. FedRAMP program for 3 years, zero breaches. Founded RedSkull, built Friday Recap, wrote the Tampermonkey tracker. Programs I built now run regions I will never manage. That's the goal.