A few days
Pre-launch test pass
A focused round of QA on a build or a flow before you ship, with a written list of what's broken and how bad it is.
Freelancer category
Testers who find the bug before your customers do.
Manual QA, usability testing, and clear bug reports — on real phones and browsers, not just an emulator. Every tester in the iince pool has filed reports a developer could act on, not vague 'it's broken' notes.
- Covers
- Web, iOS, Android
- Shortlist
- Usually within 48 hours
- Fee
- Once, only if you hire
Example shortlist3 people
Checkout QA before launch, subscription app
$25–40/h · start this week · English
DV
QA tester
5 yrs · Manila · $25–30/h · free now
Manual QAiOS / AndroidBug reports
Why: Files tidy reports with exact steps and a screen recording; developers rarely have to ask twice.
EO
Usability tester
4 yrs · Nairobi · $20–28/h · part-time
Think-aloudWeb flowsEN
Why: Records clear think-aloud walkthroughs and points to the exact screen where people get stuck.
RP
QA tester
7 yrs · Kraków · $30–40/h · free from Monday
Cross-browserRegressionEN / PL
Why: Methodical cross-browser passes; keeps a checklist so nothing ships untested.
Example of the format. Real shortlists include portfolio links and current availability.
The work
What they take off your plate
Manual QA of websites and mobile apps on real devices
Bug reports with clear steps to reproduce, logs, and screenshots
Usability and think-aloud testing on real user flows
Cross-browser and cross-device checks before you ship
Vetting for this role
What we check before we shortlist a app & website testers.
General vetting isn't enough. These are the checks specific to this role, on top of the skill tests every applicant takes.
A real bug report, not a complaint
We ask for a sample report. Clear steps to reproduce, expected vs actual, and a screenshot or recording — or it doesn't make the shortlist.
Their own devices
We confirm which real phones, browsers, and OS versions they can test on. Emulator-only testers are flagged as such.
A short test task
For most briefs we give a quick trial flow to test. We read how they report before we introduce them.
Typical engagements
The three briefs we see most.
Per release
Regression testing
The same checklist run on each release, so a fix in one place doesn't quietly break another.
Monthly, part-time
Ongoing QA and feedback
A tester on call for new features, usability feedback, and cross-device checks, without a full-time hire.
Typical ranges, not quotes. Your brief decides the scope and the timeline.
App & website testers: questions
Before you hire.
Do they test on real devices or emulators?
Tell us the devices and browsers that matter to you. We shortlist testers who own the real phones and OS versions you need, and we say plainly when someone only has an emulator.
What does a bug report from them look like?
Clear steps to reproduce, what they expected, what actually happened, and a screenshot or screen recording — the kind a developer can act on without a follow-up call.
Can I hire a tester for one release and then stop?
Yes. Short, per-release and pre-launch rounds are common. Put the build, the flows, and the deadline in your brief.
Often hired together
Start a brief
Tell us what you need.
Send a short brief — role, budget, timeline. We'll come back with two or three people we'd hire ourselves, usually within 48 hours.
Request a shortlistA good brief for a app & website testers says
- Product: website, iOS app, Android app, or all
- Devices and browsers that matter to your users
- The job: pre-launch pass, regression, or usability feedback
- Timing: when you ship and how fast you need results
- Languages: the ones your users test in