Senior Quality Engineer

This is a senior individual contributor role for the first dedicated quality engineer, owning quality across the entire platform. You will define what quality means for an AI-native product with generated content, build the system to maintain it, and have the authority to gate releases. You will write both production and test code, treating quality as an engineering problem.

What you'll do

• The automated test estate: Unit through end-to-end, across the traveller-facing app, the content platform behind it and our internal tooling. Making it fast, trustworthy and actually maintained.
• Release confidence: What gates a release, when it runs, and what a failure means. You will make shipping frequently safe rather than slowing it down.
• Evaluation of generated content: Defining what quality means for model-produced output, in every language we serve, and building the system that measures it.
• Developer experience: Tooling that makes the right thing the easy thing for engineers who are not testing specialists.
• The multi-brand dimension: One platform serving several partner brands, each with its own identity and configuration, tested as the matrix it genuinely is.
• The standard itself: Not as a written policy, but as working tooling that every engineer benefits from.

Who you are

• Experience: You have taken on a codebase with little reliable automated coverage and left it with a test platform the team trusts. Having done that more than once counts for a great deal.
• Coding skills: You write production code as readily as test code. Our stack is TypeScript and React on the front end, Node behind it, Postgres underneath, with Playwright and GitHub Actions doing much of the work. Python is welcome on the evaluation side.
• Non-deterministic output: You have built evaluation for non-deterministic output, whether on an existing framework or your own. Turning subjective judgement into something measurable is the harder half of this role.
• Agent-driven workflows: You already have agent-driven workflows that genuinely work, and clear opinions about where a model does not belong in the loop.
• Release gating: You are comfortable owning release gating end to end, including the conversations where something you built stops a release.

Nice to have

• Multi-brand or white-label products, where one platform ships as several identities.
• Internationalisation, and right-to-left languages in particular.

#J-18808-Ljbffr