What to do:
Overview: Evaluate RentAHuman across three dimensions: (1) UI design polish and consistency, (2) content clarity and navigation, and (3) authentication functionality and basic security. Begin at https://rentahuman.ai/, also visit https://rentahuman.ai/bounties and https://rentahuman.ai/login during the journey.
PART 1 β UI Design & Visual Polish
Starting at https://rentahuman.ai/, browse the homepage and all accessible public pages, then sign up and explore authenticated areas.
Report on:
Any icons, illustrations, or visual elements that feel generic, inconsistent, or AI-generated in style.
Inconsistent spacing, font sizes, font weights, or colour usage across pages.
Components or sections that feel unfinished, misaligned, or visually out of place.
Areas where the design feels unprofessional or lacks a modern, cohesive look.
Specific pages or sections that would benefit most from a design improvement.
PART 2 β Content Clarity & Navigation
While browsing all sections (public and authenticated), report on:
Any sections where the copy is vague, ambiguous, or lacks sufficient context to understand what the feature does or what action to take next.
Navigation items or labels that are unclear or misleading.
Onboarding flows, instructions, or tooltips that do not give enough guidance.
Specific pages where adding more detail, examples, or explanatory text would help users understand what to do.
Visit https://rentahuman.ai/bounties and report whether the information presented there is specific and actionable enough for a new visitor to understand how bounties work.
PART 3 β Authentication Flow & Basic Security
Use a test account you create and control throughout this section. Do not use real personal credentials.
Log in with your test account and confirm the flow works as expected.
Attempt repeated failed logins (e.g., 10+ times with wrong credentials) and report whether any rate limiting, CAPTCHA, lockout, or warning is triggered.
Report whether there is any indication of brute-force protection.
Note whether a 2FA/MFA prompt appears at any point.
Session handling:
After logging in, note whether the session persists correctly across page refreshes and navigation.
Log out and confirm you cannot access authenticated pages without logging back in.
If possible, note whether the session expires after a period of inactivity.
Password reset:
Trigger the password reset flow and report whether it functions correctly (you do not need to complete a real reset β just verify the flow initiates and communicates clearly).
Report any missing security signals, such as no rate limiting on login, no password strength enforcement, no 2FA option, or unclear session expiry behaviour.
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 75 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:
Experienced with usability and UI/UX evaluation
Able to assess visual design quality and consistency
Comfortable testing authentication flows and basic security considerations
Use a desktop browser (Chrome or Firefox latest recommended)
What you must do to be paid
Before you apply
Access to a device that can open https://rentahuman.ai/
Experienced with usability and UI/UX evaluation
Able to assess visual design quality and consistency
Comfortable testing authentication flows and basic security considerations
Use a desktop browser (Chrome or Firefox latest recommended)
**Overview:** Evaluate RentAHuman across three dimensions: (1) UI design polish and consistency, (2) content clarity and navigation, and (3) authentication functionality and basic security. Begin at https://rentahuman.ai/, also visit https://rentahuman.ai/bounties and https://rentahuman.ai/login during the journey.
---
**PART 1 β UI Design & Visual Polish**
Starting at https://rentahuman.ai/, browse the homepage and all accessible public pages, then sign up and explore authenticated areas.
Report on:
- Any icons, illustrations, or visual elements that feel generic, inconsistent, or AI-generated in style.
- Inconsistent spacing, font sizes, font weights, or colour usage across pages.
- Components or sections that feel unfinished, misaligned, or visually out of place.
- Areas where the design feels unprofessional or lacks a modern, cohesive look.
- Specific pages or sections that would benefit most from a design improvement.
---
**PART 2 β Content Clarity & Navigation**
While browsing all sections (public and authenticated), report on:
- Any sections where the copy is vague, ambiguous, or lacks sufficient context to understand what the feature does or what action to take next.
- Navigation items or labels that are unclear or misleading.
- Onboarding flows, instructions, or tooltips that do not give enough guidance.
- Specific pages where adding more detail, examples, or explanatory text would help users understand what to do.
- Visit https://rentahuman.ai/bounties and report whether the information presented there is specific and actionable enough for a new visitor to understand how bounties work.
---
**PART 3 β Authentication Flow & Basic Security**
Use a test account you create and control throughout this section. Do not use real personal credentials.
**Sign-up (https://rentahuman.ai/login or the registration page):**
- Complete the registration flow with a tester-controlled test account.
- Check whether password strength requirements are enforced (e.g., minimum length, complexity rules).
- Confirm that password confirmation is required and validated correctly.
- Note whether any 2FA/MFA option is offered or referenced during sign-up.
- Try submitting a weak password (e.g., "123456") β is it accepted or rejected? Report the outcome.
**Login (https://rentahuman.ai/login):**
- Log in with your test account and confirm the flow works as expected.
- Attempt repeated failed logins (e.g., 10+ times with wrong credentials) and report whether any rate limiting, CAPTCHA, lockout, or warning is triggered.
- Report whether there is any indication of brute-force protection.
- Note whether a 2FA/MFA prompt appears at any point.
**Session handling:**
- After logging in, note whether the session persists correctly across page refreshes and navigation.
- Log out and confirm you cannot access authenticated pages without logging back in.
- If possible, note whether the session expires after a period of inactivity.
**Password reset:**
- Trigger the password reset flow and report whether it functions correctly (you do not need to complete a real reset β just verify the flow initiates and communicates clearly).
**Report any missing security signals**, such as no rate limiting on login, no password strength enforcement, no 2FA option, or unclear session expiry behaviour.
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 75 MB with spoken microphone narration throughout, plus at least one representative screenshot. Captions, written narration, and on-screen text do not replace the required microphone audio.
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
β’
Experienced with usability and UI/UX evaluation
β’
Able to assess visual design quality and consistency
β’
Comfortable testing authentication flows and basic security considerations
β’
Use a desktop browser (Chrome or Firefox latest recommended)
SKILLS NEEDED
Experienced with usability and UI/UX evaluationAble to assess visual design quality and consistencyComfortable testing authentication flows and basic security considerationsUse a desktop browser (Chrome or Firefox latest recommended)