Independent software testing · St George, UT · remote

Find out what your release is hiding.

Fixed-price testing investigations for teams of ten to sixty. You get a written report: what I found, how bad it is, what I'd do about it.

No 01 · Diagnostic
$2,500 · one week
No 02 · Investigation
$9,500 · three weeks
No 03 · Retainer
$5,000 · monthly
Capacity
One engagement · at a time
01 / Approach

Testing is investigation, not ceremony.

notA QA engineer running scripted test cases
notQuality assurance rubber-stamping releases
notA gatekeeper who says "looks good, ship it"
amA tester who investigates software under uncertainty
amA practitioner of heuristics, oracles, and risk-based strategy
amThe person who reports what stakeholders can act on

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 — migrated APIs, replacement services, and post-migration member data.

methodology
Rapid Software Testing
core craft
Exploratory testing · oracles
automation
C# · NUnit · Postman
data
SQL Server · post-migration
Method
Charters over scripts
Every session opens with a charter — a mission, an oracle, a timebox. No pass/fail checklists pretending to be tests.
Philosophy
Fewer, better checks
A suite is as strong as its weakest assertion. I'd rather delete a hundred checks than ship one that lies.
Output
Stories, not tickets
A bug report names the risk, the stakeholder who cares, and the cost of ignoring it. Nobody should have to translate.
Practice
Question the rule
When a query returns zero rows, that's a hypothesis to test — not an answer. The rule itself might be what's wrong.
?
Operating principle
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.
Currently readingTaking Testing Seriously: The Rapid Software Testing Approach — James Bach and Michael Bolton
ReferenceRapid Software Testing methodology (Bach & Bolton)
Next investigationAI agent containment — escape surfaces
02 / Contact

Let's start.

Looking for a tester who investigates, not executes?

Send me the shape of what you're building — the stakes, the timeframe, where it hurts. I'll come back with how I'd investigate it.

LocationSt George, Utah · MT

Send a brief.

The more context, the sharper the response.