Experienced Website QA Tester (Non-Technical) – Find & Report UX Bugs on Desktop & Mobile
Budget: $2 – $5 USD
Description:
We are running paid traffic to our website and observing interaction issues via Microsoft Clarity — users are clicking elements that do not function properly on certain devices or browsers. The site works well for us (Windows + iPhone), but clearly not for everyone.
We are looking for an experienced QA website tester (non-technical, no coding needed) who understands usability testing, device/browser variability, and can apply structured QA best practices to uncover and document issues.
Your Role:
Review user behaviour recordings (Microsoft Clarity) and spot usability issues or points of friction
Test the website across multiple browsers (Chrome, Safari, Firefox, Edge) and devices (desktop + mobile)
Interact with all critical user flows: menus, buttons, forms, checkouts, navigation
Use your QA knowledge to apply best practices in reporting, prioritisation, and testing depth
Document findings in a way that helps a developer or designer fix the issue fast
Deliverables (Your Output):
A comprehensive bug and UX issue report (Excel, Google Sheets or Word), including:
Page URL
Issue description
Steps to reproduce
Device & browser used
Screenshot or screen recording (strongly preferred)
Severity level (Low / Medium / High)
Suggested action or notes (optional but welcome)
Requirements:
Experience in manual website QA, usability testing, or similar QA freelance work
Familiarity with tools like Microsoft Clarity, Hotjar, or session replay tools
Strong attention to detail and pattern recognition
Ability to structure reports clearly and concisely for tech teams
Fluent written English
Bonus if you have:
Previous experience testing marketing or landing pages for campaigns
A working process you already use for structured testing and QA documentation
Access to BrowserStack or real devices for expanded testing
In your proposal, please include:
A short note on your experience in QA/testing
What devices and browsers you can test on
A sample of any past bug or usability report you’ve created (optional)
We are running paid traffic to our website and observing interaction issues via Microsoft Clarity — users are clicking elements that do not function properly on certain devices or browsers. The site works well for us (Windows + iPhone), but clearly not for everyone.
We are looking for an experienced QA website tester (non-technical, no coding needed) who understands usability testing, device/browser variability, and can apply structured QA best practices to uncover and document issues.
Your Role:
Review user behaviour recordings (Microsoft Clarity) and spot usability issues or points of friction
Test the website across multiple browsers (Chrome, Safari, Firefox, Edge) and devices (desktop + mobile)
Interact with all critical user flows: menus, buttons, forms, checkouts, navigation
Use your QA knowledge to apply best practices in reporting, prioritisation, and testing depth
Document findings in a way that helps a developer or designer fix the issue fast
Deliverables (Your Output):
A comprehensive bug and UX issue report (Excel, Google Sheets or Word), including:
Page URL
Issue description
Steps to reproduce
Device & browser used
Screenshot or screen recording (strongly preferred)
Severity level (Low / Medium / High)
Suggested action or notes (optional but welcome)
Requirements:
Experience in manual website QA, usability testing, or similar QA freelance work
Familiarity with tools like Microsoft Clarity, Hotjar, or session replay tools
Strong attention to detail and pattern recognition
Ability to structure reports clearly and concisely for tech teams
Fluent written English
Bonus if you have:
Previous experience testing marketing or landing pages for campaigns
A working process you already use for structured testing and QA documentation
Access to BrowserStack or real devices for expanded testing
In your proposal, please include:
A short note on your experience in QA/testing
What devices and browsers you can test on
A sample of any past bug or usability report you’ve created (optional)