Companies in this catalog do not charge applicants. Never send money to apply.
Description
We’re looking for a Head of Quality Engineering to raise the bar for quality across our web, mobile, and desktop products.
This is a high-impact leadership role for someone who can shape a scalable quality engineering strategy, drive meaningful test automation, and turn quality into a measurable engineering discipline. You’ll work across teams, influence engineering decisions, and build processes and systems that help quality scale beyond the QA team. We’re looking for someone with strong technical expertise who can set the direction, guide implementation, and make informed trade-offs rather than being responsible for day-to-day hands-on execution.
We are actively integrating AI and automation into all areas of the business and are looking for candidates with a mindset focused on improving efficiency, automating repetitive processes, and delivering a better user experience.
Key responsibilities
Own the company's test coverage trajectory (unit and end-to-end) and make it grow predictably as a managed metric, not as a side effect of individual enthusiasm
Build the quality infrastructure and standards that let developers and AI agents write and run tests as a natural part of delivery. The role builds the instruments; engineering teams produce the tests
Turn tests into real protection for the products: quality gates as the default state of every codebase, so broken changes stop reaching users
Move releases, mobile first, from manual verification to automated confidence, so release cadence can grow without trading away quality
Define how the company trusts AI-written code: the verification layer and acceptance standards for agent-driven development
Grow the QA discipline and the QA engineers across all teams, in partnership with their team leads: shared standards, shared tooling, and a common bar for what quality engineering means at Muse
Build and maintain the company-level quality roadmap together with the product team leads, and report progress and risks to engineering leadership
Requirements
Proven impact: You have a track record of taking teams or organizations from having tests that provide limited protection to implementing automated testing that reliably gates releases. You can demonstrate the impact with measurable results, such as improved coverage, fewer escaped defects, faster release cycles, reduced flaky-test rates, or similar metrics.
Cross-platform automation: You have production experience across web, mobile, and desktop , with hands-on expertise in at least two and architecture or review-level experience in the third.
Web: Playwright or equivalent at scale, with experience designing maintainable test architecture, parallelizing test execution, and systematically addressing flaky tests.
Mobile: Maestro, Detox, Appium, or equivalent, with experience supporting release trains, staged rollouts, and reliable device/emulator CI.
Desktop: Native applications across Windows, macOS, or Linux. Experience with visual regression testing is a plus; C++/Qt experience is an advantage.
Quality & CI/CD: You treat quality as an engineering metric. You have established quality baselines, tracked meaningful trends, and validated that automated tests effectively detect defects through mutation testing or equivalent practices. You have operated large automated test suites as real CI/CD gates, balancing required checks, branch protection, test reliability, and feedback speed.
AI-assisted engineering: You have hands-on experience with AI-assisted coding and test generation using tools such as Claude Code, Cursor, or similar. You understand where AI-generated tests provide meaningful protection and where they may simply increase coverage without improving confidence.
Leadership: You can grow and mentor engineers without relying on formal line-management authority. You have helped other engineers develop stronger automation skills and can demonstrate this impact. You are comfortable defending quality decisions using data and clearly articulating trade-offs, including when to block a release and when the level of risk is acceptable.
