> Markdown version of [/jobs/ext/4612818-quality-assurance-engineer-automation](https://www.wearedevelopers.com/jobs/ext/4612818-quality-assurance-engineer-automation). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Quality Assurance Engineer (Automation) - **Company:** Lyrebird Health - **Location:** UK (Remote available) - **Salary:** £61,073.0 - **Contract:** Permanent contract - **Skills:** Test Suite, Application Programming Interfaces (APIs), Artificial Intelligence, Automation of Tests, Unit Testing, Code Review, Databases, Continuous Integration, Database Testing, Python (Programming Language), PostgreSQL, Load Testing, Svelte, Mockito, Standard Sql, Software Testing Automation Framework, Test Data, TypeScript, Web Applications, Openapi, Grafana, Backend, Langfuse — LLM Observability and Analytics Platform, Pytest, Playwright, Sentry, Production Code, DeepEval, JestJS, Docker - **Published:** November 7, 2026 - **Apply:** https://www.adzuna.co.uk/jobs/details/5956703900 ## About the Role * Strong test automation experience in both TypeScript and Python, writing tests as production-quality code * Deep hands-on experience with Playwright, plus component testing with Vitest and Testing Library * Solid pytest skills, including async tests, fixtures, mocking and test data factories such as polyfactory or Faker * Experience running tests in CI pipelines (ideally Buildkite) and in Docker, with coverage measurement and reporting * Working knowledge of SQL and Postgres, and confidence testing at the database layer * Experience with API contract testing against OpenAPI schemas Nice to have * Experience evaluating large language model output with tools such as DeepEval, openevals or Langfuse * Load testing experience with Locust * Familiarity with Svelte, Storybook, or Supabase and its CLI-based database testing * Experience with observability tools such as Sentry, OpenTelemetry and Honeycomb * A background in healthcare, clinical software or other regulated, safety-critical environments Every test you write protects a clinician who is relying on Lyrebird in the middle of a busy day, and the patient sitting in front of them. When our platform is fast, stable and trustworthy, clinicians spend less time on admin and more time on care. You'll be the person who makes sure we can promise that with confidence, release after release. ## Description You'll own the quality of the Lyrebird platform, from the first commit to the release gate. This is a hands-on, code-first engineering role, not manual test scripting. You'll make our Playwright end-to-end and integration suites faster and more reliable, build contract tests that stop backend changes from silently breaking the web app, and design ways to evaluate clinical model output where exact-match assertions don't work. You'll also be the quality partner to our SRE function, giving them the health checks, synthetic monitors, load test results and post-deployment signals they need. When a release is ready to go, you'll give a clear yes or no, backed by evidence. This role suits an engineer who sees testing as a craft and treats a test suite as production code. You're comfortable moving between TypeScript and Python in the same day, you get real satisfaction from deleting a flaky test and cutting minutes off a pipeline, and you'd rather help other engineers write better tests than be the only person who writes them. You'll enjoy the hard problem at the centre of this role: how to prove that non-deterministic AI output is safe and accurate enough for clinicians to rely on., * Extend our API and partner integration suites, and build contract tests from our OpenAPI schemas so no backend change can break the web app without warning * Add coverage gates to our Buildkite pipeline, using reporting that already breaks quality down by product area * Support and collaborate with our engineering teams with CICD development and oversight * Test the clinical output of our models with DeepEval, openevals and Langfuse traces, designing evaluations that hold up when responses change from run to run * Run load tests with Locust ahead of major releases and hand clear findings to the SRE function * Build the signals SRE depends on: health checks, synthetic monitors and post-deployment tests * Own the release quality gate, giving a clear yes or no with the evidence behind it * Raise the standard of testing across engineering through shared patterns, fixtures and thoughtful code review