How qahuman is meant to work.
qahuman is a two-sided QA marketplace. That only works if both sides understand the rules: how jobs are funded, who sees sensitive access, what gets delivered, and what happens when the work is weak.
Post with context. Hire with evidence.
- 1Post a brief with focus areas, budget, access notes, and any required devices.
- 2Fund the job through Stripe so testers know the work is serious before they apply.
- 3Review proposals, compare profiles and reviews, and accept one tester.
- 4Receive a structured report, request revisions if needed, then approve or dispute.
Win work through quality, not noise.
- 1Browse open work, check the brief carefully, and pitch only the jobs you can execute well.
- 2If accepted, read the locked kickoff brief before you start the timer.
- 3Deliver a report with severity, repro steps, evidence, and a usable summary.
- 4Get paid through Stripe after approval and build public proof through reviews.
Proposal-based matching
Founders are not forced into a mystery assignee. Testers pitch, founders compare, and one tester is accepted before work starts.
Escrow-backed approval
Jobs are funded through Stripe before work begins. Founders can request revisions, approve the report, or escalate a dispute.
Public tester proof
Tester profiles show completed jobs, visible reviews, and trait scores so founders are not hiring blind.
Evidence for disputes
Brief focus areas, optional scenarios, report content, revision notes, and message threads create the paper trail needed when a job goes sideways.
- Use temporary or sandbox credentials only. Do not share production credentials.
- Sensitive job access should be limited to the maker, the assigned tester, and admins resolving disputes.
- Rotate or revoke any shared credentials once the job is complete.
- If a job requires unusual access, founders should explain the environment clearly in the brief before a tester accepts.
- Founders get up to 3 change rounds before final approval or dispute.
- Testers should treat the report as professional work product, not casual beta feedback.
- Disputes depend on evidence: brief focus areas, optional scenarios, messages, report content, and follow-up notes.
- Strong public reviews matter because they reduce risk for the next match.
Inspect the proof before you commit.
The fastest way to understand the marketplace is to inspect the deliverable itself and see how an approved job can be verified publicly.