What to do:
You will conduct a focused QA walkthrough of hwhelper.tech. Stay actively engaged throughout β do not remain idle; keep interacting with the site for the full session.
1. Account Creation
Navigate to the sign-up/registration page.
Create a new test account using your own test email and a password you control. Do not use any real personal or sensitive credentials.
Note any issues with the form (validation, error messages, UX, broken fields).
2. Login & Brute Force Resistance
Log out after creating your account.
Attempt to log back in normally.
Then deliberately attempt multiple failed logins in quick succession (e.g., 5β10 wrong passwords) to test whether the site has brute force protections such as rate limiting, CAPTCHA, account lockout, or login throttling.
Report clearly: Does the site appear to have any brute force protection? What happens after repeated failures?
3. General Exploration (minimum 3 minutes of active use)
Explore the site's main features while logged in β click through menus, use any tools or interactive features available, and test core functionality.
Look for broken links, UI bugs, confusing UX, slow loading, or unexpected errors.
Try any homework help or assistant features if present and note how well they work.
Useful findings to report:
Whether brute force protection exists and how it behaves
Any bugs, broken elements, or confusing flows during sign-up or login
Overall usability and any standout issues found during exploration
Your honest impressions of the site's quality and any recommendations
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 512 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $10.00 is released per accepted submission.
Tester requirements:
C1+ English proficiency (professional or near-native level)
Strong QA or software testing experience
Must remain actively engaged throughout the session β no idle time
Web Browser or Moblie Web
What you must do to be paid
Before you apply
Access to a device that can open https://hwhelper.tech/
C1+ English proficiency (professional or near-native level)
Strong QA or software testing experience
Must remain actively engaged throughout the session β no idle time
You will conduct a focused QA walkthrough of hwhelper.tech. Stay actively engaged throughout β do not remain idle; keep interacting with the site for the full session.
**1. Account Creation**
- Navigate to the sign-up/registration page.
- Create a new test account using your own test email and a password you control. Do not use any real personal or sensitive credentials.
- Note any issues with the form (validation, error messages, UX, broken fields).
**2. Login & Brute Force Resistance**
- Log out after creating your account.
- Attempt to log back in normally.
- Then deliberately attempt multiple failed logins in quick succession (e.g., 5β10 wrong passwords) to test whether the site has brute force protections such as rate limiting, CAPTCHA, account lockout, or login throttling.
- Report clearly: Does the site appear to have any brute force protection? What happens after repeated failures?
**3. General Exploration (minimum 3 minutes of active use)**
- Explore the site's main features while logged in β click through menus, use any tools or interactive features available, and test core functionality.
- Look for broken links, UI bugs, confusing UX, slow loading, or unexpected errors.
- Try any homework help or assistant features if present and note how well they work.
**Useful findings to report:**
- Whether brute force protection exists and how it behaves
- Any bugs, broken elements, or confusing flows during sign-up or login
- Overall usability and any standout issues found during exploration
- Your honest impressions of the site's quality and any recommendations
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot. Speak your findings aloud while recording whenever you can: narration is strongly encouraged and makes your report far more useful, but it is not required and a quiet recording will still be reviewed on its merits.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
β’
Access to a device that can open the target URL
β’
Report every issue with a severity and exact reproduction steps
β’
Only submit evidence you captured yourself during this run
β’
C1+ English proficiency (professional or near-native level)
β’
Strong QA or software testing experience
β’
Must remain actively engaged throughout the session β no idle time
β’
Web Browser or Moblie Web
SKILLS NEEDED
C1+ English proficiency (professional or near-native level)Strong QA or software testing experienceMust remain actively engaged throughout the session β no idle timeWeb Browser or Moblie Web