Job Introduction
At Tribepad, we put People first, Product second and Profit third. Our recruitment technology is used by employers such as Greggs, Northumberland County Council, the Met Office and DFS.
We're on a mission to make recruitment faster, fairer and better for everyone. Along the way, we've earned these accreditations:
Certified B Corporation
ISO 9001, ISO 14001 and ISO 27001 certified
The Role
Six-month Contractor role, full-time from January 2027, reporting to the CPTO.
Mostly remote - Sheffield two or three days a month for planning and team days. Standard day rate, paid monthly.
We’re moving quality from a manual, end-of-process activity to something built into the pipeline from the start. This is a hands-on role; you’ll define the quality strategy, build the automation foundations and get them running in CI, and bring our QA engineers and developers with you so the capability is theirs when you leave.
What you'll do
By the end of six months, we expect:
A written quality strategy for what the teams actually use: what we automate and at which layer, what stays exploratory, how we test AI-driven features, what the definition of done requires, and how quality is measured. Agreed with the product managers and the principal engineers.
Automated test foundations in place and running in CI on every merge: a
maintainable end-to-end suite in Playwright covering the critical recruiter and candidate journeys, API and contract tests for the backend, and a sensible approach to test data across tenants.
Quality shifted left. Testable acceptance criteria written with the product managers before work starts, developers writing and owning tests as part of the definition of done, QA pairing with developers from the first day of a ticket rather than at the end.
An approach to testing AI features: evaluation sets, golden questions, regression on model or prompt changes, and clear rules for when a non-deterministic output is good enough to ship.
AI used in the quality process itself. Test generation, coverage analysis, triage of failures and review automation, with judgement about where it helps and where it does not. Our developers are already using Claude heavily, and the quality practice should match.
Quality is visible in the delivery metrics: escaped defects, change failure rate, flaky test rate and time spent in test, feeding the delivery dashboard the leadership team already uses.
Our QA engineers own the automation: writing and maintaining Playwright and API tests, working in the pipeline and using AI tooling well. Built through pairing, code review and real tickets.
Before you apply:
You are available full-time from 1 January 2027 for six months, no overlapping contracts.
Operating through a limited company and set up to work outside IR35: own kit, own methods, substitution clause acceptable.
UK-based with the right to work, able to get to Sheffield two or three days a month and work UK hours.
Has built an automated test practice from a low base at least once, in a product team, and can show what it looked like six months after they left. Maintaining a suite someone else built does not count.
Has taken manual testers into automation before and can point to someone who got there because of it.
References from a product or engineering team they were embedded in, not just an agency or consultancy client.
Experience:
Extensive experience in software testing and leading quality engineering in a B2B SaaS product team working in sprints with CI/CD.
Playwright in-depth. Page object or fixture-based architecture, parallelism, handling flakiness properly rather than with retries, visual and accessibility checks, running in CI with useful reporting.
API and contract testing. REST APIs, schema and contract tests, test data setup and teardown, testing against a multi-tenant database without leaking between tenants.
Test strategy and risk-based design. Knowing what to automate at which layer, what to leave exploratory, and what not to test. Writing acceptance criteria with product managers that are testable from the start.
CI/CD and engineering fluency. Git, PRs, pipelines (GitHub Actions or similar), trunk-based development and feature flags. Comfortable reading application code in a Laravel or similar PHP codebase and SQL against PostgreSQL.
Testing AI and LLM-driven features. Evaluation sets, golden question sets, measuring accuracy and regression when models or prompts change, deciding what good enough means for non-deterministic output.
Using AI in the testing process itself. Generating and maintaining tests with tools like Claude or Copilot, AI-assisted triage and review, and clear judgement about where it helps and where it produces plausible rubbish.
Shift-left ways of working. Has moved a team from QA at the end to quality built in, with developers owning tests as part of the definition of done.
Quality metrics. Has defined and reported escaped defects, change failure rate, flaky test rate and test cycle time, and used them to drive improvements.
Nice to have, not required
Performance and load testing (k6 or similar) for a multi-tenant SaaS platform.
Security testing basics and working alongside pen tests and ISO 27001 controls.
Accessibility testing to WCAG 2.2, which matters for a candidate-facing product.
Testing integrations: webhooks, third-party APIs, HR system connectors, SSO.
Recruitment or HR tech. Applicant tracking, candidate journeys, the quirks of requisitions versus openings versus jobs.
Testing migrations from a legacy product.
A PE-backed or scale-up environment.
How we work
Three cross-functional teams, each with a Senior Product Manager, engineers and shared QA, working in two-week sprints with a demo every fortnight. Trunk-based development, feature flags, deploy on merge.
You will work day-to-day with the principal engineers who own technical direction and with the QA engineers. You will make the calls on quality approach and tooling.
