Senior Quality Engineer

The role

This is not a testing role in the traditional sense. We're not looking for someone to catch bugs at the end of the pipeline and hand them back. We're looking for someone to own how quality happens across the entire product. As we like to put it: QA owns the testing strategy, not product quality. Product quality is shared by Product and Engineering. Your job is to make sure the whole system is set up so that everyone can build confidence in what we ship, from the moment a feature is designed to the moment it's released. That means enabling engineers to test effectively, driving a quality mindset across teams, and building the systems and processes that support it, not just writing and running test cases.

We think about quality the way our users experience the product: as complete journeys, not as a checklist of acceptance criteria. If you read this and think "quality is someone else's problem once I've logged the bug," this role isn't for you. If you think in terms of "can the user actually achieve their goal here, and how do I make the whole team confident that they can," keep reading. This is a senior role because it demands ownership. Not the word, the behavior: seeing what needs to happen and making it happen without being told, working across Product, Engineering, Data as a matter of course, and taking responsibility for the testing strategy of a feature end to end.

Core responsibilities

• Own the testing strategy for the features and areas you work on. Decide how confidence gets built, which validation happens at which layer (unit, component, integration, API, golden, E2E, accessibility, performance, security, manual, exploratory), rather than defaulting everything to end-to-end testing.
• Get involved early. Join discovery and specification reviews before development starts: clarify assumptions, surface edge cases, identify risks and dependencies, and ask the hard questions ("what happens if the API fails, if permissions are denied, if the user abandons the flow?").
• Design test cases as part of feature development, not after it. Covering user journeys, happy paths, edge cases, error handling, recovery, and regression.
• Enable engineers to own their part of quality. Give developers the test suites, regression packs, environments, and mock data they need to validate their own work before it reaches you, and help build a culture where they do.
• Do the testing that matters. Structured execution of prepared cases plus mandatory exploratory testing to find what predefined cases can't predict, like usability issues, cross-feature interactions, and wrong assumptions.
• Maintain a living view of test coverage per feature. So release decisions are based on measurable confidence rather than "the ticket is closed."
• Continuously improve the automation strategy and the process itself. Reduce flakiness, close coverage gaps, cut repetitive manual regression, and free up time for exploratory, accessibility, security, and performance work.
• Bring AI/LLM tools into the workflow. Use them to speed up test case design, automation scripting, and exploratory testing, and keep pushing the team's QA practices forward as new tools emerge.