| Detail | For this role |
|---|---|
| Department | Information Technology |
| Level | Senior management |
| Reports to | Vice President Engineering |
| Direct reports | QA Manager, Test Manager, Senior QA Engineer |
| Experience | 14+ years in software testing, including 5 or more years leading QA teams across several products or programs |
Head of QA job description template
Copy this job description, replace the text in square brackets and post it on your careers page or a job portal.
Job title: Head of QA
Department: Information Technology
Reports to: Vice President Engineering
Location: [City], [office, branch or site]
About the role
The Head of QA owns software quality across every product or client program a company runs. They set the test strategy, decide what gets automated, define the release quality gates and lead the QA managers, test leads and engineers who apply them. In Indian product companies and IT services firms the role reports to engineering or delivery leadership and has the authority to hold a release that is not ready. A good Head of QA cuts production defects without slowing releases and builds automation that teams actually trust.
Key responsibilities
- Define the organization-wide test strategy covering unit, API, UI, performance, security and user acceptance testing, and who owns each layer.
- Set release quality gates such as pass rates, open defect limits by severity and performance baselines, and sign off or hold releases against them.
- Decide the automation roadmap, choose frameworks and tools, and make sure regression suites run in the CI pipeline on every build.
- Plan QA headcount and skill mix across products or client programs, balancing manual, automation and performance testers.
- Run defect leakage analysis after each release and agree prevention actions with engineering managers.
- Standardize test documentation, test data management and test environment booking across teams.
- Review QA effort in proposals and project plans so testing is not squeezed at the end of the schedule.
- Handle quality escalations from clients or product owners, and lead root cause reviews for serious production defects.
- Hire and develop QA managers and test leads, and build a learning path from manual testing to automation.
- Report defect leakage, automation coverage and test cycle time to engineering and delivery leadership every month.
Requirements
- B.E., B.Tech, MCA or B.Sc in Computer Science
- ISTQB Advanced Level Test Manager certification is an advantage
- Hands-on automation experience in Java, Python or JavaScript
- 14+ years in software testing, including 5 or more years leading QA teams across several products or programs
KRAs and KPIs for a Head of QA
Key result areas for the appraisal form, each with a KPI you can measure every month or quarter.
| Key result area | How to measure it |
|---|---|
| Defect leakage | Defects found in production below 5 percent of all defects logged for each release |
| Automation coverage | At least 70 percent of regression test cases automated and running in the CI pipeline |
| Release readiness | No release goes live with open severity 1 or 2 defects unless a business owner signs an exception |
| Test cycle time | Full regression for a major release completed within 2 working days |
| Stakeholder feedback | Quality score of 4 or more out of 5 from clients or product owners each quarter |
| Team capability | At least half of manual testers trained on the automation framework within the year |
Skills and tools
Tools used day to day: Selenium or Playwright, Appium, JMeter or k6, Jira with Xray or Zephyr, Jenkins or GitHub Actions, Postman, TestRail.
Reporting line and career path
Next roles: Vice President Engineering, Head of Delivery, Head of Engineering
Interview questions for a Head of QA
- A product has no automation at all. How do you decide which regression cases to automate first?
- Engineering wants to ship tonight with three open severity 2 bugs. What do you do?
- What does your release quality gate include, and who is allowed to override it?
- Defect leakage doubled last quarter. How do you find out why?
- Would you embed testers in product teams or keep a central automation group? Why?
- Tell me about a time automation gave false confidence. What changed afterwards?
Managing a Head of QA in ZeniaHR
Hire and manage your information technology team in one place
Post the role, onboard the new hire, and track attendance, leave and KRAs in ZeniaHR. Free for your first 50 employees.
Book a free demoSee pricingFrequently asked questions
What does a head of QA do?
A head of QA owns software quality across a company's products or client programs. They set the test strategy and automation plan, define release quality gates, decide whether a release is ready, lead QA managers and test leads, and report numbers such as defect leakage to engineering leadership. The job balances release speed against the risk of defects reaching customers.
What is the difference between a head of QA and a QA manager?
A QA manager runs testing for one product line or a group of projects and manages testers directly. A head of QA sets strategy, tools and quality gates for the whole organization, plans QA headcount and has the final say on release quality. QA managers and test managers usually report to the head of QA.
Which certification is useful for a head of QA?
ISTQB certifications are the most recognized in India, and the Advanced Level Test Manager module fits this role best. Employers also look for hands-on automation experience with Selenium, Playwright or Appium, and for a record of reducing production defects over several releases, which counts for more than the certificate.