Senior Quality Engineer, Attest

• 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/TypeScript and some legacy Go — you don't need all of it. If you've built quality into complex systems in other languages, that transfers
• Genuine, demonstrable use of AI tools in your day-to-day engineering work, and active curiosity about where they go next. You're experimenting and learning in a fast-moving space
• Experience running regression and test management processes at scale
• A prevention mindset. You think about how defects stop happening as much as how they get caught, and you're comfortable challenging how a team builds and ships
• The ability to influence without formal authority, and to communicate clearly with technical and non-technical stakeholders. You'll be changing how other people work, mostly by persuading them
• Comfort with ambiguity and real autonomy. There's no existing quality function to lean on, and no one here who can hand you the answer. You'll hit pushback and find things don't work as you hoped — we need someone who handles that well and asks for feedback rather than waiting for it
• We encourage you to apply even if you don't fit all the criteria above, especially if you're energised by embracing the future and building impactful, high-quality software

Desirable

• 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
• Senior Quality Engineer at Attest: be our first dedicated quality expert shaping strategy and building greenfield automation for a platform trusted by global brands