About the Role
At Multidots, we build enterprise WordPress for some of the world’s most demanding publishers and brands — the kind of work where a single missed defect can reach millions of readers. As our QA Manager, you’ll lead a team of 8-10 QA engineers and own the thing our clients trust us for most: quality they never have to think about.
This is a senior leadership role that sits alongside our Engineering Managers and reports to the CTO. You’ll set the quality strategy for the whole practice, grow a high-performing QA team, and push us toward a modern, automation-first approach — shifting quality earlier, catching issues faster, and freeing your team from repetitive manual work.
This role is WordPress-focused, but not WordPress-only. As the publishing technology landscape evolves — headless architectures, platforms like Sanity, and new tooling — you’ll make sure our quality practices evolve with it. You bring deep QA expertise and an appetite to keep learning.
What You’ll Own
Your team
- Lead a QA team of 8–10 as their manager — running 1:1s, supporting their day-to-day, removing blockers, and being the person they come to when something’s in their way. You’re accountable for how your QA engineers grow and how it feels to work on your team.
- Own onboarding and growth for every QA engineer. You’ll get new hires productive quickly, spot where each person needs to stretch — especially from manual toward automation — and turn those gaps into concrete growth plans so the team is measurably stronger over time.
- Build the QA hiring bar. You’ll help define what great QA looks like at Multidots, interview candidates, and grow the team with people who raise the standard.
Quality strategy & standards
- Own the quality strategy for the practice — the test approach, coverage expectations, entry/exit criteria, and the standards every project is held to. You set the bar for what “done and verified” means at Multidots.
- Define and own the metrics that matter — escaped-defect rate, coverage, test cycle time — and use them to drive real, continuous improvement rather than vanity reporting.
- Champion shift-left quality. You’ll partner with Engineering Managers to move testing earlier — into design, code review, and CI — so defects are caught before they ever reach a client.
Automation & tooling
- Drive our move to an automation-first approach. You’ll set the automation strategy, decide what’s worth automating, and steadily reduce reliance on repetitive manual testing across the team.
- Stay hands-on. You’ll write and review test scripts yourself, keep your technical instincts sharp, and partner with engineering on the deeper automation framework and CI/CD integration.
- Own the QA toolchain. You’ll evaluate and standardize the tools your team relies on — test management, automation, cross-browser, performance, and accessibility — and keep them fit for purpose as we scale.
Delivery partnership
- Partner with Project Management and Engineering. PMs own timelines and scope; EMs own the code — you’re the quality counterpart, giving clear go/no-go signals, surfacing risk early, and making sure quality is never the thing that slips under deadline pressure.
Technical Expertise We Expect
- Deep QA expertise across the full spectrum — test strategy, functional, regression, cross-browser/device, and exploratory testing — with the judgment to know where each belongs.
- Strong hands-on automation skills: experience with modern tools such as Cypress, Playwright, or Selenium, and comfort reading and writing test scripts yourself.
- Solid understanding of how quality integrates into CI/CD pipelines — automated test runs, gating, and fast feedback loops — in partnership with engineering.
- Practical knowledge of API testing (Postman, REST/GraphQL) and how to validate the layers beneath the UI.
- A working grasp of web performance, accessibility (WCAG), and security-adjacent testing — enough to hold a real standard on each.
What Success Looks Like
In your first 6–12 months, escaped defects are trending down, a growing share of testing is automated rather than manual, and quality is built in earlier across projects. Your QA engineers can point to real growth under your leadership, and your PM and EM partners trust QA as a clear, reliable signal rather than a bottleneck.
What We’re Looking For
- 10+ years in quality assurance, including proven experience leading and growing a QA team.
- A track record of building QA strategy and process from the ground up — not just executing test plans, but defining how quality works.
- Demonstrated success driving automation and reducing manual testing without sacrificing coverage.
- Strong stakeholder skills — able to give honest go/no-go calls and partner well with engineering and delivery leaders.
- Curiosity and openness to new technology — a QA expert today who’s eager to grow with the publishing tech landscape.
Nice to Have
- Experience testing high-traffic editorial, media, or publishing platforms where performance and uptime are non-negotiable.
- Hands-on work building or scaling automation frameworks and integrating them into CI/CD (GitHub Actions, GitLab CI, or similar).
- Familiarity with WordPress QA specifics — the block editor, multisite, content migrations, and plugin/theme regression at scale.
- Exposure to headless / decoupled setups and adjacent platforms (e.g. Sanity), and how QA adapts to them.
- Experience using AI-assisted QA workflows — test generation, self-healing automation, or AI-driven exploratory testing — with a clear point of view on where they help and where they don’t.
- Depth in specialized testing: accessibility (WCAG 2.1/2.2), performance/load, or security testing.
