Comprehensive QA Audit for ShowManager.pro
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted3 hours ago
***NOTE: Your bid will be refused if it is not the ACTUAL hourly rate you intend to charge. We don't deal with Bait & Switchers. Our tester needs to have integrity. Your bid is binding. Bid an amount that isn't the same when we chat wit you, we will add you to our growing list of Freelancers we do not hire. Ever.
We are looking for an experienced **QA / Product Tester** to thoroughly test our SaaS platform, ShowManager.pro.
ShowManager.pro is a platform used to manage trade shows, expos, fairs and similar events. It includes functionality for event organizers, exhibitors/vendors, booth management, floor plans, ticketing, attendee experiences, reporting and other event-management workflows.
We are NOT looking for someone who simply clicks buttons and reports obvious bugs.
We need someone who can think like a **product owner, QA engineer and real end user**.
Your job will be to test complete workflows and identify:
* Bugs and technical problems
* Broken or confusing user flows
* Business logic errors
* Missing validation
* Edge cases
* Permissions / role problems
* Inconsistent behaviour
* Poor UX
* Confusing wording or instructions
* Design/layout issues
* Mobile/responsive issues
* Places where users could get stuck
* Features that technically work but do not make sense from a user's perspective
### How the work will be assigned
We will provide specific areas or scenarios to test.
For example:
"Create a new event, configure the show, create booth types, add booths, invite an exhibitor, have the exhibitor register, select a booth and complete the process."
We expect you to explore beyond the exact happy path.
Try different sequences.
Try doing things incorrectly.
Try changing information midway through a process.
Try cancelling, going backward, refreshing the page, using another role, entering unusual data, etc.
Think about what a real customer might do.
### Reports
For each testing assignment, provide a detailed report.
Every issue should include:
**Title**
Short description of the issue.
**Severity**
Critical / High / Medium / Low / Suggestion
**Area**
Example: Exhibitor Registration / Booth Management / Ticketing
**Steps to reproduce**
Exact steps we can follow to reproduce the problem.
**Expected behaviour**
What you believe should happen.
**Actual behaviour**
What actually happened.
**Screenshots or screen recording**
Include visual evidence whenever useful.
**UX / Product Recommendation**
If something technically works but you believe it could be improved, explain why and recommend a better approach.
We also want a summary at the end of each assignment containing:
* Overall impression of the workflow
* Major blockers
* Logic problems
* UX concerns
* Design inconsistencies
* Suggested improvements
* Things that worked particularly well
### Important
We want someone who is comfortable saying:
"This feature technically works, but the workflow doesn't make sense."
or:
"This isn't technically a bug, but users are going to get confused here."
Those observations are extremely valuable to us.
### Ideal Candidate
Experience with some combination of:
* SaaS product testing
* Manual QA
* UX testing
* Product management
* Web application testing
* Complex multi-role platforms
* E-commerce or ticketing systems
* Event management software
Experience writing professional QA reports is strongly preferred.
You should have excellent English communication skills and be able to explain problems clearly.
### Initial Paid Test
We will start shortlisted candidates with a small paid testing assignment.
You will be given one workflow in ShowManager.pro to test.
We will evaluate the quality of your testing based on:
* Depth of testing
* Quality of issues discovered
* Ability to identify logic problems
* UX/product thinking
* Clarity of your report
* Screenshots/video evidence
* Ability to reproduce problems
* Ability to identify edge cases
If the work is strong, this can become ongoing work as the platform continues to develop.
When applying, please tell us:
1. What SaaS/web applications have you tested?
2. How do you approach testing a workflow you've never seen before?
3. Give an example of a UX or logic problem you discovered that was not technically a software bug.
4. What tools do you use for screenshots, screen recording and bug reporting?
5. Please provide an example of a QA/testing report if you have one.
We are looking for an experienced **QA / Product Tester** to thoroughly test our SaaS platform, ShowManager.pro.
ShowManager.pro is a platform used to manage trade shows, expos, fairs and similar events. It includes functionality for event organizers, exhibitors/vendors, booth management, floor plans, ticketing, attendee experiences, reporting and other event-management workflows.
We are NOT looking for someone who simply clicks buttons and reports obvious bugs.
We need someone who can think like a **product owner, QA engineer and real end user**.
Your job will be to test complete workflows and identify:
* Bugs and technical problems
* Broken or confusing user flows
* Business logic errors
* Missing validation
* Edge cases
* Permissions / role problems
* Inconsistent behaviour
* Poor UX
* Confusing wording or instructions
* Design/layout issues
* Mobile/responsive issues
* Places where users could get stuck
* Features that technically work but do not make sense from a user's perspective
### How the work will be assigned
We will provide specific areas or scenarios to test.
For example:
"Create a new event, configure the show, create booth types, add booths, invite an exhibitor, have the exhibitor register, select a booth and complete the process."
We expect you to explore beyond the exact happy path.
Try different sequences.
Try doing things incorrectly.
Try changing information midway through a process.
Try cancelling, going backward, refreshing the page, using another role, entering unusual data, etc.
Think about what a real customer might do.
### Reports
For each testing assignment, provide a detailed report.
Every issue should include:
**Title**
Short description of the issue.
**Severity**
Critical / High / Medium / Low / Suggestion
**Area**
Example: Exhibitor Registration / Booth Management / Ticketing
**Steps to reproduce**
Exact steps we can follow to reproduce the problem.
**Expected behaviour**
What you believe should happen.
**Actual behaviour**
What actually happened.
**Screenshots or screen recording**
Include visual evidence whenever useful.
**UX / Product Recommendation**
If something technically works but you believe it could be improved, explain why and recommend a better approach.
We also want a summary at the end of each assignment containing:
* Overall impression of the workflow
* Major blockers
* Logic problems
* UX concerns
* Design inconsistencies
* Suggested improvements
* Things that worked particularly well
### Important
We want someone who is comfortable saying:
"This feature technically works, but the workflow doesn't make sense."
or:
"This isn't technically a bug, but users are going to get confused here."
Those observations are extremely valuable to us.
### Ideal Candidate
Experience with some combination of:
* SaaS product testing
* Manual QA
* UX testing
* Product management
* Web application testing
* Complex multi-role platforms
* E-commerce or ticketing systems
* Event management software
Experience writing professional QA reports is strongly preferred.
You should have excellent English communication skills and be able to explain problems clearly.
### Initial Paid Test
We will start shortlisted candidates with a small paid testing assignment.
You will be given one workflow in ShowManager.pro to test.
We will evaluate the quality of your testing based on:
* Depth of testing
* Quality of issues discovered
* Ability to identify logic problems
* UX/product thinking
* Clarity of your report
* Screenshots/video evidence
* Ability to reproduce problems
* Ability to identify edge cases
If the work is strong, this can become ongoing work as the platform continues to develop.
When applying, please tell us:
1. What SaaS/web applications have you tested?
2. How do you approach testing a workflow you've never seen before?
3. Give an example of a UX or logic problem you discovered that was not technically a software bug.
4. What tools do you use for screenshots, screen recording and bug reporting?
5. Please provide an example of a QA/testing report if you have one.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.