Explore the earning opportunities available through Tester Work.
Exploratory Test Cycles
Compensation is based on the quality and impact of the bugs identified. In this testing type, payment is determined by the number of valid bugs reported, as well as their severity, during each test cycle.
| Bug severity | Standard payment |
| Low | $2 |
| Medium | $4 |
| High | $6 |
| Critical | $8 |
Functional Test Case Execution
This testing type offers a fixed payment per test cycle. Payment is issued upon completion of all assigned test cases within the cycle.
| Testing type | Standard payment |
| Test Case execution | $8/hour |
💡 Important notes
The final payment for Test Case Execution cycles may vary depending on the following factors:
- The overall duration of the test cycle
- The complexity and difficulty of the assigned test cases
- The country of execution, in the case of localized testing
Payment Terms:
Payment is processed within 2 weeks after the overall project completion date, not from the date individual testers complete their assigned tasks.
Payments are sent via PayPal, bank transfer through Wise, or Upwork.
In addition, starting June 2026, the final payout is subject to a performance-based adjustment structure.
The initial payout value may be reduced based on the following criteria:
| Scenario | Payout Adjustment | Example |
| Submission meets all quality standards and is submitted within the required SLA | 1.0x payout | Complete and clear bug report, all required fields included, correct screenshots/attachments, accurate severity/tagging, and submitted on time |
| Submission requires moderation, CTM edits, or intervention due to quality issues | 0.7x payout | Missing required information, incorrect or missing screenshots, incomplete execution, unclear reproduction steps, incorrect severity/tagging, or reports requiring CTM correction before acceptance |
| Submission is submitted after the required SLA/deadline | 0.9x payout | Valid execution submitted after the requested submission deadline or outside the active testing window |
| Submission is both late and requires moderation/CTM intervention | 0.6x payout | Submission delivered after the SLA, while also requiring corrections, follow-ups due to missing information, or additional CTM rework before approval |
Important Notes
- No deductions will apply when testers proactively ask questions, clarify uncertainties, or flag possible instruction inconsistencies before submitting.
- We strongly encourage testers to raise concerns early whenever instructions are unclear to help avoid avoidable rework and ensure smooth execution quality.
- Quality adjustments are intended to reflect the additional operational review or correction effort required before a submission can be approved.
What Does Not Trigger a Quality Reduction
- We understand that small differences can happen during testing and reporting. A payout reduction will not be applied for minor formatting differences, slight wording variations, or situations caused by unclear or conflicting instructions.
- Testers are also encouraged to proactively ask questions or flag uncertainties before submitting. Reaching out for clarification will never negatively impact your payout and is always preferred over guessing or submitting incomplete information.
- All submissions are reviewed contextually by the moderation team, with the goal of keeping evaluations fair, transparent, and consistent for the testing community.
Transition Payment Clarification
Please note that any ongoing cycles where a different payout value was previously communicated will not be affected by these payout updates.
During the transition period, you may receive two separate pending payments for the same cycle:
- One pending payments is generated automatically through the platform based on the current automated payout value.
- A second adjustment pending payments will be issued manually to add the remaining payout difference and ensure the final total matches the originally communicated amount.
This temporary process is part of the platform updates currently being implemented and is intended to ensure all testers receive the correct final payout.
