QA Engineer

RCP Platform — Job Description

Reports to: CTO

Work arrangement: Office-first, in line with RCP's collaborative, in-person working culture

About the team

The Digital Team exists to make RCP a genuinely digital consultancy — technology, data, and AI as core to how RCP delivers, not a layer bolted on. This role sits inside that team, building the RCP Platform from a greenfield position rather than maintaining legacy systems.

Purpose

Own the testing automation suite and functional testing strategy for the RCP Platform, including a dedicated framework for testing the platform's AI features — Claude API integrations, prompt-based behaviour, and AI-generated outputs. Work closely with developers during refinement and sprint execution so testability is built in from the point requirements are defined, not bolted on at the end. Joins a competent team that needs more depth and capacity to deliver on RCP's digital journey.

Why this role, why now

• This is a build, not a maintenance job — contribute to the RCP Platform from a greenfield position, not legacy upkeep.
• Fast-paced, cross-functional team — product, engineering, data, and AI sit together, not in silos.
• Genuine ownership — define and build the testing strategy and automation framework from scratch, not inherit someone else's backlog of technical debt.
• Build the framework for testing the platform's AI features — a genuinely novel testing problem, not a solved one — alongside a modern automated stack.
• Own the testing automation suite and functional testing strategy for the RCP Platform
• Build and maintain automated test coverage across unit, integration, and end-to-end layers (Vitest, Playwright)
• Define the team's quality standards and testing processes
• Integrate QA into the development workflow — work with developers during refinement and sprint execution to build in testability at the point requirements are defined
• Perform manual and exploratory testing alongside automated coverage
• Build and maintain a framework for testing the platform's AI features — Claude API integrations, prompt-based behaviour, and AI-generated outputs
• Close existing testing gaps across the platform, including database and edge function test coverage
• Flag quality risks and technical debt early in stand-ups and sprint ceremonies

Key responsibilities

Technical skills

Must-have

Nice-to-have

• Vitest (unit and integration testing)
• Playwright (end-to-end browser testing)
• Test planning and test case design
• API testing and mocking
• Manual and exploratory testing
• Git/GitHub workflows
• Experience testing AI/LLM-powered features (prompt evaluation, output validation, handling non-determinism)
• Supabase/Postgres testing (RLS, migrations)
• CI/CD (GitHub Actions)
• Experience defining QA processes in a small or scaling team
• Comfortable using AI code assistants to build test automation
• Meticulous attention to detail — catches edge cases and gaps others miss
• Communicates quality risks and blockers clearly to developers, the Tech Lead, and wider team
• Initiative — spots testing gaps and acts on closing them without waiting to be asked
• Problem-solving — breaks down ambiguous failures and works through them methodically
• Collaborative — works closely with developers at the point requirements are defined, not just at the end of the sprint
• Pragmatic — balances thorough testing with delivery speed

Soft skills

Experience

5+ years in a QA or test engineering role, with hands-on experience building automated test suites (unit, integration, and end-to-end) in a modern web stack.

First 90 days

• Weeks 1–4: Onboard into RCP and the Digital Team — meet the CTO, developers, and wider team; get hands-on with the RCP Platform codebase, the existing Vitest and Playwright test suites, and the team's Scrumban sprint cadence; begin closing the highest-priority testing gaps.
• Weeks 5–8: Take ownership of the testing automation suite — build out coverage across unit, integration, and end-to-end layers, and integrate QA into refinement and sprint execution.
• Weeks 9–12: Establish the team's quality standards and testing processes; begin building out the framework for testing the platform's AI features; established working rhythm with the Tech Lead and wider team.