Mid-Level QA Automation Engineer

We are looking for an experienced QA Automation Engineer to make sure the products our customers and internal teams rely on work as intended, every release. Our work spans consumer-facing web platforms, dense, workflow-driven internal admin tools, and mobile applications. Because our product priorities evolve, you can expect to move between projects over time rather than owning a single test suite indefinitely. The common thread across all our work is a strict adherence to industry standards and best practices. We treat test code as production code: clean, maintainable, reviewed, and reliable enough that a failing test always means something. Beyond writing code, you will play a pivotal role in elevating our engineering culture by mentoring our manual QA engineers and guiding their transition into automation roles. Your Initial Focus: Your first major project will be the test automation for a complex consumer-facing travel and booking platform. You will cover both the public-facing checkout flow (mobile web, dynamic search with results arriving from multiple suppliers, and live price changes up to the moment of payment) and the high-density internal management panels used to handle complex multi-supplier orders, cancellations, and customer support workflows. A starter Playwright suite already runs on every pull request; you will turn it into real coverage, define how the project is tested, and use this foundation to start upskilling team members. Key Responsibilities Mentorship & Team Growth: Act as a technical mentor for our manual QA team, designing structured learning paths and pairing with them to build their automation capabilities in TypeScript and Playwright. Transform code reviews into teaching opportunities.Test Automation & Framework Design: Design, write, and maintain reliable, scalable automated end-to-end tests in TypeScript with Playwright, for both the customer-facing site and the admin tools.Standards & Best Practices: Apply modern test architecture (fixtures, page objects or equivalents, test data management) and internal style guides, so the suite stays fast, readable, and maintainable as it grows.Test Strategy & Coverage: Decide what to test at which level (UI, API, or contract) and prioritise the journeys that matter most: sign-in, search, checkout and payment, order changes, and cancellations.Asynchronous & Third-Party Behaviour: Make non-deterministic behaviour testable. That covers suppliers that respond slowly, fail or change prices mid-checkout, race conditions, retries, and partial results. Use mocking, service virtualisation, and controlled test data, never fixed waits.CI & Release Quality: Keep suites running on every pull request in CI, investigate and eliminate flaky tests instead of retrying them, and own release sign-off in the acceptance environment before production.Code Review & Collaboration: Take part in code review and technical discussions alongside frontend and backend engineers. Raise testability concerns early, while features and API contracts are still being designed.Cross-Functional Collaboration: Work closely with product management, designers, and engineers to turn requirements into clear acceptance criteria. Push back when a flow won’t hold up against real-world latency, edge-case data, or slow networks.Non-Functional Quality: Cover responsive and cross-browser behaviour, localisation (multiple languages including non-Latin scripts, and multiple currencies), accessibility (WCAG), and performance checks on mid-range mobile devices. What We Are Looking For Experience: 4+ years in QA engineering focused on test automation for production web applications, with solid, hands-on Playwright experience (fixtures, network interception and mocking, tracing, parallel execution).Mentorship & Leadership: Proven track record of upskilling, training, or mentoring manual QA engineers to transition into automation roles. You know how to explain test architecture patiently and foster a culture of continuous technical growth.Strong TypeScript: You write test code to the same standard as product code, not recorded scripts with light edits.Mobile Automation (strongly preferred): Hands-on experience automating native iOS and Android apps with Appium, Maestro, Detox, XCUITest, or Espresso. Our upcoming projects include mobile applications, and you may move to them.Complex Async Testing: Comfortable testing the gap between dynamic server states and user actions: loading states, streamed results, optimistic updates, retries, and error recovery.Auth & Payments: Experience testing authentication flows (one-time email codes, OAuth with Google and Apple, sessions and cookies) and payment flows against provider test environments.API Testing: Confident testing REST APIs directly and reading API contracts and documentation.CI/CD: Experience running and maintaining test suites in CI pipelines (GitHub Actions or similar), and judging whether a failure is the product, the test, or the environment.Language: Professional working English. Your bug reports let a developer reproduce the problem without a follow-up question. Nice to Have Contract Testing & Service Virtualisation: Experience isolating third-party integrations in tests.Internationalization Testing: Multi-currency formatting and multi-language UIs, including non-Latin or right-to-left scripts.Accessibility & Visual Regression: axe or similar accessibility tooling, and visual comparison testing.Performance Testing: Core Web Vitals and load testing (k6 or similar).Device Clouds: BrowserStack, Sauce Labs, or similar, for real mobile browsers and devices.Domain Experience: E-commerce, marketplaces, or booking products. What This Role Is Not This is not a role where you click through test cases from a spreadsheet before each release. You will be expected to think critically about asynchronous behaviour, third-party failures, edge cases in real data, and how features are designed. Repeatable checks belong in code that runs on every pull request. If you prefer manual regression testing, or working at the end of the process on finished features without influencing how they are built, this role will not be a good fit.