For testers

Get paid to break things.

Real apps, real money, on your own schedule. Every job is funded before you see it, and you keep 90% of the budget.

Free to join. No bidding credits, no subscription, no cut of anything you did not earn.

What you keep
  • Quick Pass≤30 min$4.50on a $5 budget
  • Full Sweep~2 hours$22.50on a $25 budget
  • Deep Dive3+ hours$90on a $100 budget

90% of the budget, after a 10% service fee. Founders often post above these floors — you pitch your own rate.

Why testers stay

Every job is already paid for

The board only lists funded work. You are never chasing an invoice or hoping a client comes back.

You keep 90%

Same split as Upwork, without connects, bidding credits, or a subscription. What you pitch is what you earn, minus one service fee.

Your record travels with you

Ratings across six traits, approved reports, and badges build a public profile founders hire from — you are not starting from zero every time.

How you earn

  1. Set up your profile. Devices, niches, languages, and a sample report if you have one.
  2. Send a proposal. Pitch your rate, the devices you will use, and the flows you will cover.
  3. Do the testing. Work the brief on real devices. Ask questions in the workroom as you go.
  4. Get paid. Submit your report. On approval, Stripe pays you out automatically.

Straight answers

How do I actually get paid?

Through Stripe, straight to your bank. You connect a Stripe account once; when a founder approves your report, the payout is released automatically. You keep 90% of the job budget.

What if the founder just never pays?

They already have. Every job on the board was paid for before it was listed — that is why the board only shows funded work. If a founder goes quiet after you deliver, the report auto-approves after 7 days.

Do I need to be a professional QA engineer?

No. Careful, curious people who write clearly do well here. Deep Dive jobs need Pro level (100 XP), which you reach through approved work — everything else is open from day one.

What does a good report look like?

Severity, the device and OS, numbered steps that reproduce the issue, and a screenshot or recording. We give you the structure — you fill it in.

Start with one job this week.

244 reports delivered · 118 testers on the platform