What to do:
Evaluate whether visitors can quickly understand Madhav's professional background, skills, and projects, then locate and review a portfolio project or contact method within five minutes.
Navigate to the homepage and identify the primary sections or navigation menu visible on the page
Locate and review Madhav's professional summary, skills, or background information presented on the site
Find and click on at least one portfolio project or work sample to view project details
Identify how to contact Madhav or express interest in working together using visible CTAs or contact information
Return to the homepage and assess overall clarity of the value proposition and call-to-action hierarchy
Evidence: Record screen navigation and interactions with narration describing ease of finding information. Write findings on clarity of professional positioning, project discoverability, contact accessibility, and whether the portfolio effectively communicates Madhav's expertise and availability within five minutes of first visit.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
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. $4.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://madhav-balachandar.netlify.app/
Evaluate whether visitors can quickly understand Madhav's professional background, skills, and projects, then locate and review a portfolio project or contact method within five minutes.
1. Navigate to the homepage and identify the primary sections or navigation menu visible on the page
2. Locate and review Madhav's professional summary, skills, or background information presented on the site
3. Find and click on at least one portfolio project or work sample to view project details
4. Identify how to contact Madhav or express interest in working together using visible CTAs or contact information
5. Return to the homepage and assess overall clarity of the value proposition and call-to-action hierarchy
Evidence: Record screen navigation and interactions with narration describing ease of finding information. Write findings on clarity of professional positioning, project discoverability, contact accessibility, and whether the portfolio effectively communicates Madhav's expertise and availability within five minutes of first visit.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
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