I build test strategy and API automation, and I practice context-driven testing (Rapid Software Testing). Based in St. George, Utah, and open to remote.
I lead testing for an API-focused development team at Mountain America Credit Union, a $22B credit union.
I investigate software to find problems that matter, designing experiments under uncertainty and applying heuristics to evaluate behavior.
Rapid Software Testing treats testing as skilled human investigation, not a scripted process. Every session has a charter, oracles, and heuristics. Every bug report tells a story. I'd rather delete a weak test than pretend it covers something.
I audit my team's checks the same way I'd audit my own: ruthlessly, quietly, on paper. Recent work includes a credit-union core transformation covering migrated APIs, replacement services, and post-migration member data.
Every bug report tells a story. The story I tell is the one stakeholders can act on, not the one the test tool happens to print.
Testing is only as useful as what gets reported. Rather than describe how I write up findings, I published an example: two hours of exploratory testing against Cal.com, written up the way I would hand it to stakeholders.
Nobody asked me to write it. I picked a product I use, spent two hours on it, and published what I found. An example is only worth reading if the findings are real ones.
Read the full report→I'm looking for a team that treats testing as investigation. If that sounds like yours, I'd like to hear about it.
Roles, projects, and tools in one document, ready to pass along to the rest of the hiring team.