Automation Engineer

• 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

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.

• 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.