Experienced QA Engineers for SaaS Platform Testing
Budget: $5,000 – $10,000 USD
We are seeking immediately available QA engineers to execute structured manual QA testing on an enterprise SaaS platform. Speed and accuracy are critical.
This engagement is execution-focused, not exploratory or advisory.
We already have:
850+ pre-written test cases
Strict 1:1 feature-to-test-case mapping
Jira-ready workflows
Clear severity definitions and release gates
Your job is to run the tests, record results, and log high-quality bugs — fast.
What You Will Be Doing
Execute predefined manual test cases (no test design required)
Validate:
Core workflows
Permissions / role-based access
Negative and edge cases
Regression behavior
Mark pass/fail and add concise notes
Log clear, reproducible bugs in Jira with correct severity
Work in parallel with other QA testers by module
This is a hands-on execution role, not a documentation exercise.
Platform Scope
Modules include:
Operator (largest module)
Seller
Buyer
Investor
Broker
Vendor
You may be assigned one or more modules, depending on availability and speed.
Required Experience
5+ years QA experience on SaaS or enterprise platforms
Strong manual QA execution skills
Comfortable following structured test cases
Experience with Jira for bug tracking
Ability to start immediately
Strongly Preferred
Prior work on multi-module platforms
Experience testing permissions / access controls
Ability to work independently with minimal guidance
Automation experience is not required for this phase.
Timeline & Engagement
Immediate start
Short, intense execution window (1–2 weeks)
Remote
Contract-based
Potential follow-on work for regression cycles
How to Apply (Important)
Please include:
Your availability over the next 14 days
Your hourly rate
Examples of similar platforms you’ve tested
A brief description of how you write good bug reports
Generic applications will be declined.
Why This Is a Good Engagement
Clear scope (no guessing)
Fully prepared QA artifacts
Fast decision-making
Respect for QA as a critical function
Opportunity for repeat work
Question:
Briefly describe how you decide whether a bug should be marked Blocker vs High severity.
This engagement is execution-focused, not exploratory or advisory.
We already have:
850+ pre-written test cases
Strict 1:1 feature-to-test-case mapping
Jira-ready workflows
Clear severity definitions and release gates
Your job is to run the tests, record results, and log high-quality bugs — fast.
What You Will Be Doing
Execute predefined manual test cases (no test design required)
Validate:
Core workflows
Permissions / role-based access
Negative and edge cases
Regression behavior
Mark pass/fail and add concise notes
Log clear, reproducible bugs in Jira with correct severity
Work in parallel with other QA testers by module
This is a hands-on execution role, not a documentation exercise.
Platform Scope
Modules include:
Operator (largest module)
Seller
Buyer
Investor
Broker
Vendor
You may be assigned one or more modules, depending on availability and speed.
Required Experience
5+ years QA experience on SaaS or enterprise platforms
Strong manual QA execution skills
Comfortable following structured test cases
Experience with Jira for bug tracking
Ability to start immediately
Strongly Preferred
Prior work on multi-module platforms
Experience testing permissions / access controls
Ability to work independently with minimal guidance
Automation experience is not required for this phase.
Timeline & Engagement
Immediate start
Short, intense execution window (1–2 weeks)
Remote
Contract-based
Potential follow-on work for regression cycles
How to Apply (Important)
Please include:
Your availability over the next 14 days
Your hourly rate
Examples of similar platforms you’ve tested
A brief description of how you write good bug reports
Generic applications will be declined.
Why This Is a Good Engagement
Clear scope (no guessing)
Fully prepared QA artifacts
Fast decision-making
Respect for QA as a critical function
Opportunity for repeat work
Question:
Briefly describe how you decide whether a bug should be marked Blocker vs High severity.