Role · available now
A QA engineer who verifies every fix the day it lands.
Jarred takes the part of QA that nobody has time for and everybody pays for: retesting, regressions, release checks, test writing, and the evidence that proves a verdict.
Free for 30 days · no setup fee
A day. In the order it happens.
09:00
A ticket moved back to “QA”
He reads the fix, the PR and the deploy, retests it on staging in a real browser, records the result with screenshots, and comments the verdict on the ticket. Or he moves it to “Needs fixes” with the exact step that fails.
10:30
The nightly suite is red
He reads the failure, reproduces it, and says whether it's the product, the test or the environment — with the line.
12:00
“Write tests for the discount calculation”
He writes them in your repo's style, runs them green, proves each one fails against broken code, and opens a PR you can review.
14:00
Release planning call
He joins, listens, answers “what's still open in 3.8?” from the board, and the decisions land in the project memory.
16:00
A deploy is about to land on staging
A colleague is mid-test there. He says whose work it lands under before it runs.
Monday
The report
Tickets verified, bugs found before production, releases checked, hours of QA work — against what it costs with people.
What he works with.
Slack or Microsoft Teams · Jira, Asana or Linear · GitHub or Bitbucket · GitHub Actions, Bitbucket Pipelines · Envoyer and similar deploy tools · LaunchDarkly · a real browser on your staging environment · Google Meet.
Something else? Ask — the connectors are the easy part.
What he will not do.
Change production on his own
Production access is read-only unless separately agreed; pushing, merging or deploying to production always needs a human yes, at any trust level.
Call a result verified without evidence
A verdict is linked to what his tools returned — a screenshot, a log, the failing step. What he could not verify is labeled unverified, by the platform, not by a prompt.
Enter what you mark off-limits
An admin panel, a billing page: he can't navigate there. The rule is enforced in code, not asked of him.
Proof.
Our first customer's week, counted from the log: 97 test results, 103 approved changes, 10 bugs before production, $94 of AI usage. The case study →
€1,200 a month. Free for 30 days.
A 30-minute call, then ten minutes of your admin's time. The first ticket gets verified the same day.