I exist in the space between shipped and safe — the layer where product decisions become trust, or don't. Five years of testing the systems people hand their money, their data, and their week to, mostly before anyone else has to find out what they were really shipping.
What I'm known for isn't finding bugs. It's building the gate that stops them from coming back — the UAT process, the pipelines, the automation that turns one engineer's vigilance into something the next release inherits for free. A team I built, a release cadence I shaped, and a quality bar the product has to clear before I let it out the door.
Principle 01
Quality is not a feature.
It is the standard.
When something breaks — and it always does — I don't just log it and move on. Every bug gets documented in enough detail that a developer can fix it without a follow-up question, and every pattern gets folded back into the process: a new regression check, a new line on the UAT gate, a rule the next release inherits for free. Because in QA, the closest thing to bending time is preventing the future:
Principle 02
Catch it in staging,
or meet it in production.
The whole craft bends toward that one outcome. Every regression suite, every UAT gate, every line of automation I've ever written is just an attempt to move the moment of failure earlier — out of the customer's hands and into mine, where the cost is a Jira ticket and not a Friday-night war room. Staging is where I do my best work. Production is where I do the kind of work I'd rather not.