SaaS QA Engineer — Pre-Launch Full-Platform Testing & Regression QA

Looking for an experienced SaaS QA Engineer to independently perform comprehensive pre-launch QA testing across our entire SaaS platform.

The testing scope includes all areas of the product, not only the public website or customer-facing pages.

Full Testing Scope
You will test the complete platform, including:
Public website: Homepage, pricing, informational pages, forms, links, navigation, and other public-facing pages.

Public booking/customer experience: Complete booking flows, service/provider selection, scheduling, customer details, confirmations, cancellations, payments, and related customer-facing functionality.

Business side: Business registration, onboarding, authentication, dashboard, appointments/scheduling, customers, services, team/providers, payments, reporting, settings, subscriptions/billing, and all other business-account functionality.

Platform/Admin staff side: Admin authentication, internal dashboards, business/account management, support functionality, administrative tools, permissions, staff workflows, and other internal platform functionality.

Authentication & security-related flows: Sign-up, sign-in, sign-out, password reset, social authentication, sessions, protected routes, permissions, and unauthorized-access scenarios.

Billing & payments: Trials, subscriptions, plan changes, payments, refunds, cancellations, failed-payment scenarios, and applicable webhook/integration behavior.

Emails & notifications: Transactional emails, verification flows, notifications, delivery behavior, and failure/error scenarios.

Integrations: Relevant third-party services, APIs, and integration-dependent workflows.

Data & permissions: Creating, editing, deleting, and persisting data; account/tenant separation; roles; permissions; and access controls.

UI/UX functionality: Forms, buttons, links, navigation, validation, loading states, empty states, error states, and unexpected user behavior.

Responsive & browser testing: Mobile and desktop layouts across relevant screen sizes and major browsers.

Regression testing: Retest completed fixes and verify that changes have not broken previously working functionality.

Testing should cover complete end-to-end workflows, not just individual pages.
The QA engineer should also perform exploratory testing rather than relying exclusively on a checklist. We want an independent tester who actively looks for bugs, edge cases, broken workflows, data inconsistencies, permission problems, and issues we may not already know about.

Bug Reporting
Every identified issue should include:
Clear bug title
Severity/priority
Area of the platform affected
Exact steps to reproduce
Expected behavior
Actual behavior
Screenshots or screen recordings when useful
Browser/device information
Relevant technical observations when available

Retesting
After fixes are completed by our developer, you will independently retest reported issues, check for regressions, rerun critical end-to-end workflows, and mark each issue as Passed, Failed, Reopened, or Requires Further Review.

Final Deliverable
Provide a final QA report containing all identified issues, severity, current status, retest results, remaining known issues, critical workflow PASS/FAIL results, and any unresolved risks that should be reviewed before launch.

This is an independent QA role. Your responsibility is to thoroughly test the entire platform — public website, customer/booking experience, business side, and internal admin/staff side — document issues accurately, and independently verify fixes before launch.