Performance engineering
I make products fast, and keep them fast.
I start from measurements, fix causes instead of symptoms, and stop regressions before they merge.
The evidence
Strengths — with receipts
Six strengths, and the stories behind each one. No adjective here without a story you can read.
Performance engineering
I start from measurements, fix causes instead of symptoms, and stop regressions before they merge.
The evidence
Architecture & technical decisions
Stack choices, state boundaries and shared building blocks, argued with trade-offs rather than taste.
The evidence
Quality on critical flows
Payments, wallets and bookings get tested first, across components, integration, end to end and real browsers.
The evidence
UX & product thinking
Shorter booking paths, forms that fail where the error is, and states the designs forgot.
The evidence
End-to-end ownership
End-to-end responsibility for a booking platform, and a World Cup launch on a deadline that couldn't move.
The evidence
Working across teams
Backend, design, product and management: payloads checked before raising issues, edge cases agreed before coding.
The evidence
How I decide
Decisions→