About
The best decisions
I've made weren't
just technical.
I've worked on payments, platform modernization, and regulated systems at NAB, Commonwealth Bank, oOh!media, AMP, Seven West Media, InfoTrack, and Nexty. Right now that's the digital payments org at NAB, where I lead engineering for PayID and FX capabilities serving millions of customers.
Platform strategy
for regulated systems and product teams
Engineering leadership
across distributed teams and delivery pressure
Risk and governance
where reliability and compliance both matter
Writing and thinking
about decisions that matter at scale
How I build
Every system I architect starts with the same question: what's the smallest thing that's true to the problem? Complexity is easy. Knowing when to stop is the craft.
I lead from the code up. I care about the architecture, the operating model, and the people making decisions inside it. Good systems have to survive change, not just demo well.
Domains of judgment
Platform architecture
The right abstraction boundary saves a lot of pain. Most engineers draw it too early.
Engineering leadership
The bottleneck is never the people — it's what they're not allowed to decide.
Financial infrastructure
Compliance looks like a constraint until you realise it's a moat.
Payments & resilience
A system that degrades gracefully is more valuable than one that never fails.
Technical strategy
The most expensive decision is the one disguised as a small implementation detail.
Get in touch
I lead engineering at NAB and write about the decisions that compound at scale. If something here resonates — platform strategy, technical leadership, or constraint trade-offs at scale — I'd like to hear from you.