Manual QA Tester for eCommerce Website – Ongoing Work
Manual QA Tester – eCommerce Website | 3-Month Contract
We are looking for an experienced Manual QA Tester to work with our development team on an established eCommerce website.
This is a 3-month contract, with work available between:
1:00pm–5:00pm Australian Melbourne time (AEST/AEDT)
Monday to Sunday
Up to 28 hours per week
You do not need to be available all 7 days.
We are looking for someone who can commit to a consistent weekly schedule within these hours. For example, if you are available Monday–Saturday from 1pm–5pm, please let us know.
The Role
Our developers complete bug fixes, improvements and new features and move their Trello tickets to Ready for QA.
The goal of this role is to keep development tickets moving through QA efficiently so completed work can be released to production as quickly as possible.
Your role will be to:
Test tickets in development and staging
Verify bug fixes and new functionality
Test normal flows and edge cases
Perform regression testing
Identify issues developers may have missed
Document bugs clearly with reproduction steps and screenshots/video
Retest fixes
Update QA tickets in Trello
Approve tickets when testing is complete
The website is an established eCommerce business, so testing will include checkout, payments, shipping, customer accounts, orders, emails, admin functionality and other website features.
What We're Looking For
Strong manual web QA experience
eCommerce testing experience
Excellent attention to detail
Good written English
Ability to investigate problems independently
Experience with Trello or similar ticketing systems
Reliable and consistent availability
This is primarily manual QA. Automated testing/programming is not required.
Contract
Duration: 3 months
Hours: Up to 28 hours/week
Available shifts: 1pm–5pm Melbourne time, Monday–Sunday
Schedule: Based on your regular availability
When Applying please tell us about yourself and answer the following:
1. Which days are you regularly available from 1pm–5pm Melbourne time?
2. How many years of manual QA experience do you have?
3. Have you tested eCommerce websites before? Please briefly describe your experience.
4. When a developer tells you a bug has been fixed, how would you test it beyond checking the original issue?
5. You start your shift and have several tickets waiting for QA. Some are urgent, some are more complex, and one has unclear requirements. Explain how you would prioritise your work, what you would do if you're unsure about a ticket, and when you would contact the developer or project owner.