For testers

Test real apps.
Get paid. Build a rep.

Browse open tests from developers who need real human feedback. Claim a slot, record your session, submit structured answers, and get paid when they approve — not maybe, guaranteed.

$5–$45
Per test
Set by each developer. Higher-tier testers access tests with higher pay.
~3 min
One-time setup
Identity check and skills assessment. Done once — then you can claim tests immediately.
Automatic
Stripe payouts
Payment releases to your Stripe Connect account the moment the developer approves your submission.
What you need

Three things to get started.

Setup is a one-time process. Once you're through it, claiming tests is instant.

Government-issued ID

A one-time identity check confirms you're a real person. This protects developers and ensures a high-quality tester pool. Your ID is reviewed solely for verification and is not shared.

Stripe account for payouts

Connect a Stripe account to receive payments. Stripe handles the transfer directly to your bank — QATested never holds your money after you're approved. Setting up Stripe Connect is free.

Ability to record your screen

Every submission requires a screen recording. Most testers use Loom (free) — record your session, then paste the link when submitting. Mobile testers can use the built-in screen recorder on iOS and Android.

How it works

From signup to first payout.

Clear steps, no surprises.

1

Get set up

Skills check (~3 min), ID verification, and Stripe Connect — all one-time. Most people finish onboarding in a single session, then you're cleared to claim tests.

2

Claim a slot

Browse open tests filtered by your device, browser, and tier. Read the brief, then claim — the slot is yours until the deadline.

  • Payout is fixed per slot — set by the developer
  • Rising/Top/Elite-gated tests often pay more
  • Claim and ghost it? That hurts your rating
3

Test, record, and submit

Follow the instructions. Record your full session (Loom works). Answer the form with specific, honest feedback — "it worked fine" with no detail won't cut it.

4

Get paid on approval

Developer approves → Stripe pays you. No invoice, no chasing anyone. Bank transfer follows Stripe's usual timing.

Quality standards

What makes a submission good.

Developers approve or reject each submission. Here's what they're looking for — and what tends to get rejected.

Gets approved Approved

  • Followed the test instructions exactly as written
  • Screen recording covers the full test session, not just part of it
  • Form answers are specific — references actual things you saw or did
  • Bugs are described clearly: what you did, what happened, what you expected
  • Honest even when nothing is broken — "I completed it without issues" is a valid answer
  • Submitted before the deadline

Gets rejected Rejected

  • Vague answers like "it was fine" or "looks good" with no detail
  • Recording doesn't show the parts the developer asked to test
  • Missed the deadline
  • Didn't follow the device or browser instructions
  • Copied or fabricated answers rather than testing the actual software
  • Recording link is broken or private
Tester tiers

The better you test, the more you can access.

Your tier is calculated from your average rating, approval rate, and tests completed. Higher tiers unlock tests that pay more — developers gate their best rates to Rising, Top, and Elite. You earn exactly what they post per slot.

Standard
All new testers start here.
  • Access to all open tests
  • Guaranteed slot pay
  • Public tester profile
Top
4.0+ rating · 85%+ approval · 15+ tests
  • Can claim Top-gated tests
  • Priority windows when enabled
  • Top badge on profile
Elite
4.5+ rating · 95%+ approval · 30+ tests
  • Can claim Elite-only tests
  • First access when priority window is on
  • Elite badge on profile
Ready to start?

Verify once. Start earning.

Sign up as a tester, complete the skills check and identity verification, and you'll have access to every open test on the platform. Early testers build their tier before the pool grows.

Building software and need real human feedback?

See how developers post tests →