We want you to feel confident about how you’ll get paid for your work as a tester at Tester Work. Here’s everything you need to know.
How the payment works:
Clear rates in every invite
Each email invitation to a test cycle states how much you’ll earn either per approved bug or as a fixed amount for completing a test case.Payment is per approved work
If multiple testers report the same bug, only the first valid report will be approved and paid.When you get paid
Payments are sent in US Dollars (USD) at the end of each test cycle. Usually, it takes up to 2 weeks after the cycle ends to receive the payment.Minimum payout threshold
If your earnings are below $5, they’ll roll over and be paid once you reach the threshold.Requirements for payment
You must submit complete, valid bug reports. Please review our Bug Reporting Guidelines and Bug Severity Guidelines to make sure your submissions qualify.Payment methods
We currently pay via PayPal, Upwork or Bank Transfer through Wise. All services may charge their own fees. Check that your chosen method is available in your country before testing.Update your preferred payment method anytime in your Tester Work profile.
Contractor status
You are an independent contractor, not an employee. This means you are responsible for reporting your earnings to your local tax authority.
When payments can Be withheld
We reserve the right to deny or withhold payments if there’s a valid reason, such as:
False or inaccurate information in your profile
Using an outdated or unsuitable testing environment
Holding duplicate accounts
Incomplete test execution
Low-quality reports
Not following client requirements
Testing outside the specified project window
If there’s ever an issue with your payment, we’ll let you know. You can always submit a ticket through our Zendesk Support Center to resolve concerns.
💡 Tips to earn more
We want you to succeed and get as many opportunities as possible. Here’s how to maximize your income:
1. Be eligible for more projects
Keep your device list up to date
Hold onto older devices for possible legacy tests
Keep at least one device updated with the latest OS
If you have a developer license, install beta OS updates early for priority projects
Check your email often. The test invites are time sensitive.
2. Increase your accepted bug count
Read the Test Specification carefully. It tells you which bugs we’re looking for
Avoid duplicate bugs by reviewing existing reports and known issues
Include all required details in bug reports. Missing info can mean losing payment
Remember: functional bugs usually pay more than usability suggestions (unless stated otherwise)
3. Learn from the community
Review other testers’ reports to sharpen your own bug-hunting skills
Engage with Tester Work’s social media channels where we share helpful tutorials and tips
The bottom line: The more accurate, complete, and consistent your work is, the more you’ll earn. We’re here to support you every step of the way.
Happy testing! 🚀
Comments
0 comments
Article is closed for comments.