QA Automation Engineer

What you'll own

• —The automated suite across client products — and its runtime, because a slow suite gets skipped
• —Deciding what's worth automating and what isn't
• —Exploratory testing on the paths that matter most to the client's business
• —Accessibility testing as part of the definition of done

What we need

• —Playwright, Cypress or comparable, on a suite you owned
• —Enough programming to write maintainable test code, not just recordings
• —API testing alongside UI
• —The judgement to argue that something shouldn't be automated

Helpful, not required

• —Performance testing
• —Mobile automation
• —CI integration and flake triage

What this role isn't

So the wrong candidates can rule themselves out in thirty seconds rather than three interviews.

• ×It isn't a manual-only role.
• ×It isn't a gate at the end of a project — you're in from sprint one.

How we interview

1. 01Screening call — 30 minWhat you've automated and what you deliberately didn't.
2. 02Technical conversation — 75 minWe look at a real feature and plan its coverage together.
3. 03Conversation with the Head of Engineering — 45 minStandards and your questions.

Decision within two weeks of the first call. If it's a no, you get a reason, not silence.