Senior Quality Engineer

Attest is a trusted data provider to brands like Netflix, Unilever, Nestlé and Reddit, connecting them to 150+ million consumers across 59 countries. When those brands make decisions on our data, they're trusting the quality of our platform. This role owns that.

You'll be Attest's first dedicated Quality Engineer, joining the Quality Squad, a central team responsible for quality across the whole platform, not a single product area. Right now, engineers test their own code and you'd be building the practice from close to zero: the automation, the standards, the tooling, and the way quality thinking works here. The most interesting part is where quality sits in the process.

You would be working with stakeholders across Attest before the roadmap is fully scoped, you'd be in those first conversations, shaping what gets built, rather than running a checklist at the end.

A note on who we're looking for: Your title doesn't need to say QA. Some of the strongest candidates for this will be software or Dev Ops engineers who've taken quality seriously because nobody else was going to, and who want to make it the whole job. If that's you, please apply.

£75,000–£85,000 depending on experience, with equity options and comprehensive benefits.

In-person and Remote Working Balance

We work in a flexible hybrid model. Most squads collaborate in person around two days per week, with flexibility around which days work best. This helps us balance meaningful face-to-face collaboration with time for focused engineering work.

What You'll Be Doing

• Set the direction for quality at Attest. Decide what our test strategy, coverage standards, definitions of done and release confidence actually look like, and bring the ideas the squad doesn't have yet.
• Build the automation layer. Standing up automated testing is the first priority and largely greenfield. We have some JUnit, Cypress and Storybook in place; where it goes from here is your call, and we'd rather hear your view than have you inherit ours.
• Get quality in early, everywhere. Review proposals before code exists, across every squad. That means working collaboratively with engineers who've been here far longer than you, on their designs, before anything is built, less "this was wrong," more "here's how I'd validate this."
• Decide what's worth testing. Prioritise quality effort by risk and value, and be willing to say what we're deliberately not going to test. We don't want everything covered ten times over; we want the coverage that actually protects customers.
• Root-cause and feed back. Get hands-on with production issues and quality gaps, then turn what you find into changes in process and tooling rather than one-off fixes.
• Work AI-natively. Use AI coding assistants and agentic tools as a core part of how you work. We're also interested in where AI tooling could go further in a quality pipeline, evaluating quality in ways that go beyond a test case passing or failing. That's an open question here, and you'd help answer it.
• Define quality metrics that drive change. Measure what matters and use it to make the case for improvement, not just to report status.

What You'll Bring

You'll need:

• Demonstrable experience shaping how a team builds and ships quality — the strategy, standards and tooling, not executing test cases someone else wrote. Whether your title said QA or engineer matters less than what you've actually changed.
• Real strength in test automation. We use JUnit, Cypress and Storybook today, but we care far more about your thinking than your toolset, and we're genuinely open to being told we should be doing something different.
• Enough breadth to reason about validating a system you don't know yet. Our stack is Java (Spring Boot), Python, Vue/Type Script and some legacy…