Salary: TBC

The role

You’ll test everything the team builds before it reaches customers. Two people build and both ship every week: a senior engineer who owns the foundations, and a co-founder who builds screens using Claude Code. You’ll check both of them.

You’ll own the release checklist, the regression run, bug reports and fix verification. You’ll test by hand first and keep the automated end-to-end tests running. You’ll report to the founders rather than the engineer, so the person who wrote the code doesn’t decide whether a bug matters. Your first big job is testing the migration of 60 customers from GoHighLevel onto the new platform.

What you’ll own

Exploratory testing of every feature before it goes live, across the main browsers and on mobile

The release checklist and regression run on every release

Maintaining the Playwright end-to-end tests: updating them when screens change and adding cases for bugs you find

Clear bug reports with steps, screenshots and severity, and verifying fixes once shipped

Testing the money paths every time: Stripe subscriptions, credits and financial calculators

Checking data separation between customers (one customer must never see another’s data)

Testing the GoHighLevel migration so every customer’s data arrives complete and correct

Keeping test cases and known-issues documentation up to date

What you’ll need

3+ years testing web SaaS products, including at least one role where you were the main or only tester

Risk-based test planning: you decide what to test first when there isn’t time for everything, and can explain why

Hands-on exploratory and regression testing, with test cases kept in a lightweight tool (TestRail, Qase, Notion or a spreadsheet)

Working-level Playwright in TypeScript: run the suite, read a failure and trace, fix a broken locator, add a case (Cypress experience transfers)

API testing with Postman, Bruno or Playwright’s request API, including checking error handling and verifying webhooks

Read-level SQL to check what landed in Postgres after an action

Ability to read a GitHub Actions CI run and tell a flaky test from a real failure

Clear, reproducible bug reports in GitHub Issues, Linear or Jira

Clear written English, since most of the job is written

Requirements

Nice to have

Testing Stripe billing end to end in test mode (subscriptions, failed payments, webhooks, proration)

Validating data migrations (record counts, field mapping, reconciliation)

Using AI tools (Claude, Cursor, Playwright MCP) to draft test cases and automation, then checking the result

Multi-tenant and permissions testing

Accessibility (WCAG 2.2), mobile browser testing and visual regression tools

GoHighLevel experience

No property knowledge is needed, as the domain will be taught. You also won’t need to build test frameworks from scratch or do performance or security testing.

You’ll thrive here if you are

Pedantic in a good way: you notice the thing that’s slightly off and chase it down. You ask “what if the customer does this instead?” before the customer does, and you test the whole job a customer came to do, start to finish. You plan your own hours around what’s shipping that week, you report what you found even when the engineer disagrees, and you keep process light, so “not a bug” is an answer you can accept and move on from.

This probably isn’t for you if you’re a purely manual tester with no exposure to Playwright or Cypress, API testing or SQL; you’d rather spend your hours building a framework than testing the product; you need a test lead to assign you tickets; or you can only work full-time or fixed daily hours.