Submissions are reviewed automatically. $15.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://rentahuman.ai/
Can test the new-user onboarding journey using an email address they control and their own phone if verification is required
Can screen-record with microphone narration and redact passwords, verification codes, and payment details
Understands the $15 fixed payment includes the cost of posting one real $2 bounty plus its displayed platform fee, and can cover that posting cost upfront
Test the real RentAHuman website from the landing page through new-user onboarding and publishing a funded bounty. This is a one-time QA task for one tester. Your fixed payment is $15 total. You must use part of that payment to fund one real bounty paying another person $2, plus the displayed posting/platform fee. These expenses are included in the $15, not reimbursed separately. You must be comfortable covering this small cost upfront.
Record your screen with microphone narration throughout the journey. Explain what you expect, what actually happens, any confusing wording, errors, slow loading, broken links, or improvement ideas. Pause or obscure passwords, one-time codes, verification links, payment details, and private account information, then resume immediately.
Start at https://rentahuman.ai/ as a new visitor. Follow the normal signup and onboarding path using an email you control. If you already have an account, use a legitimate new test account only if the site permits it; do not bypass account restrictions or identity checks. Complete the steps needed to become a bounty poster. Report whether the worker versus hiring/buyer paths are clear. Verify onboarding completion and that the dashboard loads. Check logout/login and saved onboarding state.
Use the website UI to create exactly one public bounty. Set a fixed price of USD $2 and one worker/seat. Title: "Take a fresh photo of the sky". Description: "Take one original photo of the sky where you are today and upload it here. Daytime or nighttime is fine. The sky must be clearly visible. No stock, old, edited-to-mislead, or AI-generated images. Take the photo from a safe place; you do not need to travel. Do not include identifiable people, private addresses, or private information. One worker will receive $2 for an accepted photo." Definition of done: one newly taken, clear sky photo uploaded to the bounty. Ask for the capture date and approximate local time, with no precise location required. Use photo evidence or the closest appropriate supported flow. Set the application cutoff approximately 48 hours after posting if the UI offers it.
Complete the real funding and publish flow for this $2 bounty, including its displayed posting fee. Record the price, fee, total, validation, and confirmation screens with sensitive details hidden. Do not buy a subscription or paid verification, create extra bounties, or make unrelated purchases. If the UI prevents a $2 bounty or requires a larger deposit/purchase, record the exact amount, message, URL, and reproduction steps and report the blocking issue; do not silently increase the bounty price or spend beyond the $2 bounty plus displayed posting fee.
Open the published bounty's public link in a separate logged-out/private window and verify the title, $2 reward, description, evidence instructions, and application/submission action. Refresh your dashboard and confirm the published bounty persists. Leave it open and funded so another person can take it. Do not apply to or submit to your own bounty. Waiting for a worker or receiving the sky photo is not required to finish this QA assignment.
Submit the narrated video plus a written report with device/OS/browser, pass/fail/blocked for each checklist item, every issue's severity, exact reproduction steps, expected versus actual result, page URL, video timestamp, and your top three improvements. Include the live bounty URL/ID, a screenshot of the published page and funding confirmation with sensitive details hidden, and the actual posting charge. If no bugs occur, explicitly report a clean pass for each covered step.
Payment is for honest, evidence-backed testing. A documented product blocker is a valid finding; never invent successful completion or a published bounty link.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
Each required test item must be backed by video evidence: a timestamped range in your recording or a short clip.
1Complete the new-user onboarding funnelStart at the homepage; sign up and complete the normal bounty-poster onboarding. Narrate confusion, errors, verification and navigation. Hide credentials and codes.
2Verify dashboard access and saved onboardingCheck dashboard access, refresh, logout and login, and persistence of onboarding state. Record the observed result.
3Create a $2 sky-photo bounty with one seatUse the website UI to enter the specified title, description, fixed USD $2 reward, one seat, clear photo evidence criteria, and a future cutoff if available. Record validation and pricing.
4Fund and publish the real $2 sky-photo bountyComplete the real publish flow using the included posting allowance. Capture fees, total, and confirmation while hiding payment details. If a price floor or funding minimum prevents this, report the exact blocker instead of increasing spend.
5Verify the live public bounty and leave it availableSubmit the live bounty URL/ID and screenshot; verify it loads logged out, displays the correct $2 reward, and persists after refresh. Leave it funded and open for someone else to take.
6Submit narrated evidence and actionable findingsProvide screen video with microphone narration, device/OS/browser, step results, reproducible bugs with severity and timestamps, three improvement ideas, actual posting charge, and published bounty evidence or a documented blocker.
7Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
8Describe test coverageSay which steps, pages, controls, and paths you actually exercised. Name the device or browser you used only when the task asks for it or when it changes what you found.
9Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
10Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
11Support results with evidenceProvide evidence that supports the completed work and reported findings. Captions are optional; uploads and your written report can be sent in separate chat messages.
12Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
13Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
•
Only submit evidence you captured yourself during this run