QA Engineer / Full-Stack Developer — Manual SaaS Testing & Bug Fixing
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted2 hours ago
Seeking an experienced **QA Engineer with full-stack development capabilities** to manually test an entire SaaS web application, identify and investigate defects, implement approved fixes, and regression-test those fixes.
**Manual QA is the primary responsibility of this role.** You must personally walk through and use the deployed application in a real browser as a customer, business user, and Platform Admin/staff user would.
Automated tests, typechecks, builds, scripts, linting, and other code-level checks are welcome as additional safeguards, but **they do not replace hands-on manual testing of the deployed application.**
Full-Platform Testing Scope
You will manually test all available pages, modules, and critical workflows across:
**Public Website & Customer Experience**
* Marketing and informational pages
* Navigation, links, buttons, and forms
* Public booking/customer experience
* Service and provider selection
* Availability and scheduling
* Customer information and confirmations
* Payments where applicable
* Booking changes and cancellations
* Validation and error states
**Entire Business Side**
* Registration and onboarding
* Authentication and account recovery
* Dashboard
* Appointments, calendar, and scheduling
* Clients/customers
* Services
* Team/providers and availability
* Payments and refunds
* Free trials, subscriptions, billing, plan changes, and cancellations
* Reports/analytics
* Account management and settings
* Roles and permissions
* Emails and notifications
* Other available business functionality
**Entire Platform Admin / Staff Side**
* Admin/staff authentication
* Admin dashboard
* Business and account administration
* User management
* Support functionality
* Administrative tools and workflows
* Roles and permissions
* Protected functionality
* Platform-level settings/actions
* Other available Platform Admin/staff functionality
The **entire business side and entire Platform Admin/staff side are required parts of the testing scope.**
Manual QA Requirements
Testing must involve real end-to-end use of the application, not simply confirming that pages load.
You will be expected to:
* Navigate through all major areas of the application
* Test buttons, links, menus, tabs, forms, modals, and other interactive elements
* Create, edit, and delete QA/test data
* Complete critical workflows from beginning to end
* Test valid and invalid inputs
* Test validation, empty, loading, success, and error states
* Verify data and session persistence
* Test authentication, protected routes, roles, and permissions
* Test unauthorized-access scenarios where appropriate
* Test interactions between customer, business, and admin workflows where applicable
* Test desktop and mobile/responsive behavior
* Test major supported browsers
* Perform exploratory and edge-case testing
* Identify functional, data, permission, workflow, and significant usability problems
You should actively look for issues that may not already be known.
QA Documentation & Bug Reporting
Maintain a clear **QA test matrix/checklist** showing what was manually tested, including the area/workflow, user role, result (**PASS / FAIL / BLOCKED**), related issue when applicable, and retest status.
Each identified bug should include:
* Clear issue title and severity
* Area/user role affected
* Steps to reproduce
* Expected vs. actual behavior
* Screenshot or screen recording when useful
* Browser/device where relevant
* Technical findings/root cause when identified
* Fix and retest status
A general statement that “QA passed” or “everything looks good” is not sufficient. We need clear documentation of actual test coverage.
Full-Stack Debugging & Bug Fixing
You must also be capable of technically investigating the issues you discover.
This may include diagnosing problems involving:
* Frontend
* Backend/server
* Database/data
* Authentication
* Authorization/permissions
* APIs
* Third-party integrations
* Environment/configuration
* Deployment/infrastructure
For **approved defects**, you will implement appropriate fixes, keep changes appropriately scoped, and avoid unrelated modifications.
Significant changes involving architecture, database schemas, security, billing logic, permissions, infrastructure, or core product behavior must be approved before implementation.
After a fix is available in the QA environment, you must **manually reproduce and retest the original workflow and check related functionality for regressions.**
GitHub & Development Workflow
**All code changes must be completed and delivered through our existing GitHub repository and established branch/deployment workflow. GitHub is the source of truth for the application code.**
You will be expected to:
* Work from the existing GitHub repository
* Use the designated QA/development branch
* Follow the established branch/deployment workflow
* Make clear, appropriately scoped commits
* Push completed work to GitHub
* Keep changes traceable and available for review
* Not create a replacement repository or separate codebase
* Not leave completed work only on a local machine
* Not make direct production changes outside the approved workflow
Manual testing should be performed against the appropriate **deployed QA/staging environment**, while approved code fixes should be made through the established GitHub workflow.
Production deployments and other high-impact changes require approval.
Qualifications
Looking for someone with experience in both **professional manual QA and full-stack web development**, including:
* Manual and exploratory SaaS testing
* Regression and end-to-end testing
* JavaScript/TypeScript
* React or similar frontend frameworks
* Backend/API development
* SQL/relational databases
* Authentication and authorization
* APIs and third-party integrations
* Git/GitHub
* Browser developer tools and network inspection
* Application logs and debugging
* Responsive web applications
* Deployment/configuration troubleshooting
Experience with **React, TypeScript, PostgreSQL/Supabase, Cloudflare, Stripe, Playwright, Cypress, or similar technologies** is a plus.
Deliverables
By completion of the engagement, we expect:
* Manual testing of the full provided platform
* Public/customer experience tested
* Entire business side tested
* Entire Platform Admin/staff side tested
* QA test matrix with PASS / FAIL / BLOCKED results
* Bugs documented with reproducible evidence
* Approved defects fixed through GitHub
* Fixes manually retested in the deployed QA environment
* Regression testing completed
* Critical end-to-end workflows verified
* Remaining known issues and blockers clearly documented
This is a **hands-on manual QA + full-stack debugging and bug-fixing role**. We need someone who will actually use the deployed product, find problems, investigate them technically, fix approved defects through GitHub, and manually verify that the application works afterward.
**Manual QA is the primary responsibility of this role.** You must personally walk through and use the deployed application in a real browser as a customer, business user, and Platform Admin/staff user would.
Automated tests, typechecks, builds, scripts, linting, and other code-level checks are welcome as additional safeguards, but **they do not replace hands-on manual testing of the deployed application.**
Full-Platform Testing Scope
You will manually test all available pages, modules, and critical workflows across:
**Public Website & Customer Experience**
* Marketing and informational pages
* Navigation, links, buttons, and forms
* Public booking/customer experience
* Service and provider selection
* Availability and scheduling
* Customer information and confirmations
* Payments where applicable
* Booking changes and cancellations
* Validation and error states
**Entire Business Side**
* Registration and onboarding
* Authentication and account recovery
* Dashboard
* Appointments, calendar, and scheduling
* Clients/customers
* Services
* Team/providers and availability
* Payments and refunds
* Free trials, subscriptions, billing, plan changes, and cancellations
* Reports/analytics
* Account management and settings
* Roles and permissions
* Emails and notifications
* Other available business functionality
**Entire Platform Admin / Staff Side**
* Admin/staff authentication
* Admin dashboard
* Business and account administration
* User management
* Support functionality
* Administrative tools and workflows
* Roles and permissions
* Protected functionality
* Platform-level settings/actions
* Other available Platform Admin/staff functionality
The **entire business side and entire Platform Admin/staff side are required parts of the testing scope.**
Manual QA Requirements
Testing must involve real end-to-end use of the application, not simply confirming that pages load.
You will be expected to:
* Navigate through all major areas of the application
* Test buttons, links, menus, tabs, forms, modals, and other interactive elements
* Create, edit, and delete QA/test data
* Complete critical workflows from beginning to end
* Test valid and invalid inputs
* Test validation, empty, loading, success, and error states
* Verify data and session persistence
* Test authentication, protected routes, roles, and permissions
* Test unauthorized-access scenarios where appropriate
* Test interactions between customer, business, and admin workflows where applicable
* Test desktop and mobile/responsive behavior
* Test major supported browsers
* Perform exploratory and edge-case testing
* Identify functional, data, permission, workflow, and significant usability problems
You should actively look for issues that may not already be known.
QA Documentation & Bug Reporting
Maintain a clear **QA test matrix/checklist** showing what was manually tested, including the area/workflow, user role, result (**PASS / FAIL / BLOCKED**), related issue when applicable, and retest status.
Each identified bug should include:
* Clear issue title and severity
* Area/user role affected
* Steps to reproduce
* Expected vs. actual behavior
* Screenshot or screen recording when useful
* Browser/device where relevant
* Technical findings/root cause when identified
* Fix and retest status
A general statement that “QA passed” or “everything looks good” is not sufficient. We need clear documentation of actual test coverage.
Full-Stack Debugging & Bug Fixing
You must also be capable of technically investigating the issues you discover.
This may include diagnosing problems involving:
* Frontend
* Backend/server
* Database/data
* Authentication
* Authorization/permissions
* APIs
* Third-party integrations
* Environment/configuration
* Deployment/infrastructure
For **approved defects**, you will implement appropriate fixes, keep changes appropriately scoped, and avoid unrelated modifications.
Significant changes involving architecture, database schemas, security, billing logic, permissions, infrastructure, or core product behavior must be approved before implementation.
After a fix is available in the QA environment, you must **manually reproduce and retest the original workflow and check related functionality for regressions.**
GitHub & Development Workflow
**All code changes must be completed and delivered through our existing GitHub repository and established branch/deployment workflow. GitHub is the source of truth for the application code.**
You will be expected to:
* Work from the existing GitHub repository
* Use the designated QA/development branch
* Follow the established branch/deployment workflow
* Make clear, appropriately scoped commits
* Push completed work to GitHub
* Keep changes traceable and available for review
* Not create a replacement repository or separate codebase
* Not leave completed work only on a local machine
* Not make direct production changes outside the approved workflow
Manual testing should be performed against the appropriate **deployed QA/staging environment**, while approved code fixes should be made through the established GitHub workflow.
Production deployments and other high-impact changes require approval.
Qualifications
Looking for someone with experience in both **professional manual QA and full-stack web development**, including:
* Manual and exploratory SaaS testing
* Regression and end-to-end testing
* JavaScript/TypeScript
* React or similar frontend frameworks
* Backend/API development
* SQL/relational databases
* Authentication and authorization
* APIs and third-party integrations
* Git/GitHub
* Browser developer tools and network inspection
* Application logs and debugging
* Responsive web applications
* Deployment/configuration troubleshooting
Experience with **React, TypeScript, PostgreSQL/Supabase, Cloudflare, Stripe, Playwright, Cypress, or similar technologies** is a plus.
Deliverables
By completion of the engagement, we expect:
* Manual testing of the full provided platform
* Public/customer experience tested
* Entire business side tested
* Entire Platform Admin/staff side tested
* QA test matrix with PASS / FAIL / BLOCKED results
* Bugs documented with reproducible evidence
* Approved defects fixed through GitHub
* Fixes manually retested in the deployed QA environment
* Regression testing completed
* Critical end-to-end workflows verified
* Remaining known issues and blockers clearly documented
This is a **hands-on manual QA + full-stack debugging and bug-fixing role**. We need someone who will actually use the deployed product, find problems, investigate them technically, fix approved defects through GitHub, and manually verify that the application works afterward.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.