QA Analyst (Part-Time) – Manual + Playwright UK PropTech SaaS Start-up | Fully Remote

Simply Outsourcing; South Africa; On-site; ZAR 300,000 - 540,000; Full time

Job summary

Simply Outsourcing is seeking a detail-focused QA tester to join our testing team in South Africa. You’ll own exploratory and regression testing across SaaS features, ensuring reliability before go-live and guiding bug reports through our systems.

You’ll work with senior engineers and co-founders, maintaining Playwright end-to-end tests, validating money paths, migrations, and data integrity, while keeping documentation up to date and communicating in clear written English.

Qualifications

• 3+ years testing web SaaS products, with at least one role where you were the main or only tester.
• Ability to plan tests based on risk and explain priorities.
• Hands-on exploratory and regression testing, with lightweight test case tracking.
• Proficient in Playwright in TypeScript; Cypress experience transfers.
• API testing with Postman, or Playwright’s request API, including error handling and webhooks.
• SQL to check data landed in Postgres after actions.
• Ability to read GitHub Actions CI runs and distinguish flaky tests from real failures.
• Clear, reproducible bug reports in GitHub Issues, Linear or Jira.
• Good written English, since most of the job is written.

Responsibilities

• Explore and test every feature before live release across browsers and mobile.
• Own the release checklist and regression runs for every release.
• Maintain and update Playwright end-to-end tests; add cases for found bugs.
• Provide clear bug reports with steps, screenshots and severity; verify fixes.
• Test critical money paths: Stripe subscriptions, credits, and financial calculators.
• Ensure data separation between customers and migration accuracy.
• Keep test cases and known issues documentation up to date.

Skills

Exploratory testing

Regression testing

Risk-based planning

Written communication

Test case management

Tools

Playwright

Cypress

Postman

SQL

Job description

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.

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

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.