About Me

I work to ensure software ships without end users paying the price for what slipped through. I stumbled into QE out of necessity (student loans have a way of focusing the mind), but my background in computer engineering technology — embedded systems, the hardware/software interface — gave me a different lens than most testers. Once I was in it, I committed to actually getting good at it.

Most of what I care about sits under the umbrella of Shift-Left testing: catching problems closer to where code is written rather than handing a pile of bugs to a QE member at the end of a sprint. Flaky specs and root-cause-analysis rabbit holes are expensive — they balloon fast without the right tooling and infrastructure underneath them.

The thing I focus on most is developer experience around testing infrastructure. A framework that's painful to run locally doesn't get used. When the local experience is good — fast feedback, clear failures, low friction — it becomes much easier for the whole team to share ownership over quality rather than routing everything through a dedicated QE bottleneck.