UK

United Kingdom · Technical roles · Mid-Level (2-5 years)

Head of QA

Here is the whole job, in plain words. What it is, a real day, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior QA Engineer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Mid-Level QA Engineer · Test Automation Engineer · Quality Assurance Specialist

Built on an analysis of 43,079 real UK job descriptions · grounded in qualifications employers recognise

Start with a free Future Fluency check, tuned to Head of QA

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

You'll be a key player in making sure our software actually works as it should. This isn't about just finding bugs; it's about making sure our products are robust and reliable for our customers. You'll own the quality for specific features, working closely with developers and product managers to get things right from the start.

2What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Cypress or Playwright (Test Automation Frameworks)Intermediate

You'll be writing, debugging, and maintaining automated UI test scripts for new features and existing functionality. You'll be comfortable updating selectors and handling basic test failures.

Postman or Insomnia (API Testing Tools)Intermediate

You'll use these to execute API tests, validate responses against expected outcomes, and log defects for our backend services. You'll be familiar with collections and environment variables.

TestRail or similar (Test Management)Intermediate

You'll be operating within our test management system to write test cases, execute test runs, and accurately update test statuses. You'll also use it to track your progress.

Jira or similar (Bug Tracking)Intermediate

This is where you'll be logging clear, reproducible bug reports, tracking their lifecycle, and collaborating with developers on fixes. You'll also manage your own tasks here.

JMeter or k6 (Performance Testing Tools)Basic

You should be able to run pre-written performance test scripts and gather basic results like response times. You won't be designing complex scripts yet, but you'll understand the output.

GitLab CI or Jenkins (CI/CD & DevOps Tools)Basic

You'll understand how your automated tests fit into the continuous integration/delivery pipeline. You'll be able to trigger builds and interpret test results from the logs.

BrowserStack or Sauce Labs (Cross-Browser/Device Platforms)Intermediate

You'll use these platforms for manual cross-browser/device testing and to run your automated scripts against a variety of environments. You'll debug platform-specific issues.

3What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing inWhere you are nowThe step above
Test Plan ApprovalDrafted by you, reviewed and approved by Senior QA Engineer.Drafted by you, reviewed by Senior QA Engineer, approved by you for your owned features.Designed and approved by you, with high-level review by QA Lead/Manager.
Bug Priority & SeveritySuggested by you, confirmed by Senior QA Engineer/Product Owner.Assigned by you based on impact and risk, with consultation for critical issues.Final decision on critical/blocking bugs, influencing release decisions.
Automated Test ScopeExecutes existing scripts, suggests minor additions.Determines which test cases to automate for new features, implements them independently.Defines automation strategy for a workstream, mentors others on implementation.
Go/No-Go for a FeatureProvides test status, recommendation made by Senior QA Engineer.Provides clear recommendation based on testing, final decision with Senior QA Engineer/Product Owner.Makes the final 'go/no-go' call for their owned workstreams, with consultation for major releases.

4How you'll be judged

The scoreboard, honestly: the hard targets, how often each one is actually looked at, and the quiet human signals that never make it onto a dashboard.

Bug Report Clarity & Reproducibility
The percentage of your bug reports that developers accept without needing further clarification or failing to reproduce.
Target · <10% rejection/clarification rate

You reported 20 bugs this month; 18 were accepted immediately, 2 needed a quick chat. That's a 10% clarification rate, which is spot on.

Automated Test Coverage (Feature Level)
The percentage of critical paths within the features you own that are covered by robust, automated tests.
Target · Achieve 75% coverage for new features within 2 weeks of code complete

For the new 'User Profile' feature, you added automated tests covering 80% of the key user flows, exceeding the target.

Regression Test Execution & Pass Rate
How consistently you execute assigned regression test cases and the stability of those tests (i.e., not flaky).
Target · Execute 95% of assigned regression test cases within the release window; >90% pass rate for your owned tests

Before the last release, you ran all 150 of your assigned regression tests, with 145 passing first time. The 5 failures were legitimate bugs, not flaky tests.

Defect Discovery Rate (Pre-Production)
The number of significant bugs you find in new features before they even get close to production.
Target · Find an average of 3-5 critical/high severity bugs per major feature release

For the 'Basket Checkout' revamp, you found 4 high-severity bugs related to payment processing before it went live, saving us a massive headache.

Collaboration & Proactive Risk Identification
How well you work with developers and product managers, not just finding bugs, but spotting potential issues early in the design phase.
  • You're regularly invited to early design discussions. Developers come to you for advice on testability. You're bringing up potential edge cases in stand-ups before code is even written. You're seen as a partner, not just a gatekeeper.
Test Automation Improvement
Your contribution to making our automated test suites more robust, faster, and easier to maintain.
  • You're actively refactoring old, brittle tests. You're proposing and implementing small improvements to our automation framework. Your automated tests rarely fail due to flakiness, and they run quickly.
Knowledge Sharing & Mentorship
How effectively you share your expertise and help less experienced team members grow.
  • You're helping new joiners understand our testing processes. You're doing informal code reviews for junior engineers' test scripts. You're documenting tricky test scenarios for others to use.

5Would you like it

The honest version. What people enjoy, and what grinds them down.

What people enjoy
Building Reliable Products

You get a real kick out of finding a critical bug before it reaches customers. You're driven by the idea of making our software genuinely robust and trustworthy.

Spending an extra hour to find that obscure browser-specific bug, knowing it prevents customer complaints.

Solving Technical Puzzles

Debugging a flaky automated test, figuring out why an API call is failing, or reproducing a complex user-reported issue – these are the challenges that energise you.

Spending an afternoon tracking down why a specific automated test keeps failing intermittently, finally nailing the root cause in the test environment setup.

Continuous Improvement

You're always looking for ways to make our testing processes better, faster, or more efficient, whether it's optimising a test script or suggesting a new tool.

Proposing a small change to our CI/CD pipeline to get earlier feedback on test failures, and then helping to implement it.

What frustrates people
  • Last-minute code merges that invalidate your testing efforts.
  • Vague or constantly changing requirements for features you're testing.
  • Dealing with flaky automated tests that undermine confidence in the suite.
  • The perception that QA is a 'cost centre' rather than a value-add.
What this role does not give you
  • A purely strategic, high-level role without hands-on testing.
  • A role where you're solely responsible for building new features (that's for development).
  • A predictable 9-to-5 where nothing ever changes or goes wrong.

6Who you work with

Your reliable delivery of quality-checked features directly impacts customer satisfaction and reduces the number of costly bugs that hit production. Essentially, you're helping us avoid embarrassing and expensive mistakes, which keeps our customers happy and our developers focused on building new things, not fixing old ones.

Inside the business
  • Your immediate QA team (Senior QA Engineer, other QA Engineers)
  • Software Development Engineers (the folks building the features)
  • Product Owners/Managers (who define what we're building)
  • DevOps Engineers (who manage our deployment pipelines)
Outside the business
  • Occasionally, you might help support teams with customer bug reproductions, but direct external interaction is rare.

7What you need before you start

Not a wish list. The things you would be expected to already have.

  • At least 2 years of hands-on experience in a dedicated QA or Test Engineer role.
  • Proven ability to write and debug automated UI tests using a modern framework (Cypress, Playwright, Selenium, etc.).
  • Experience with API testing tools like Postman or Insomnia.
  • Solid understanding of the Agile software development lifecycle.
  • Demonstrable experience logging clear, reproducible bugs in a tool like Jira.
  • Basic understanding of version control systems, typically Git.
  • Ability to work independently on assigned features with minimal supervision.

8What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Performance Testing & Analysis

As our systems scale and user expectations for speed increase, understanding and proactively testing performance becomes critical. Moving beyond basic script execution to designing and interpreting complex load tests will be key.

Load vs. Stress vs. Soak testing · Identifying bottlenecks · Non-functional requirements (NFRs) · Distributed tracing basics

  • This week: Read up on the different types of performance testing and their use cases.
  • This month: Take an online course on JMeter or k6 beyond the basics, focusing on scripting complex scenarios.
  • Month 2: Volunteer to assist our Senior QA Engineer on a performance testing effort, even if it's just data analysis.
  • Month 3: Propose a small performance test for a new feature you're working on, even if it's just a simple load test.

Quick win: Familiarise yourself with our existing performance test reports and try to understand the key metrics and any identified issues.

Security Testing Fundamentals (SAST/DAST)

Security isn't just for dedicated security engineers anymore. A basic understanding of common vulnerabilities and how security testing tools work will help you spot potential issues early and collaborate more effectively with security teams.

OWASP Top 10 · Static Application Security Testing (SAST) · Dynamic Application Security Testing (DAST) · Basic penetration testing concepts

  • This week: Read the OWASP Top 10 list and understand each vulnerability.
  • This month: Explore a free online course on web security basics (e.g., PortSwigger Web Security Academy).
  • Month 2: Ask a developer or security engineer about our current SAST/DAST tools and how they're used.
  • Month 3: Incorporate basic security checks into your manual exploratory testing for new features (e.g., input validation).

Quick win: Be aware of common injection vulnerabilities when testing input fields. It's a simple mental check that can catch a lot.

9Staying current once you are in

What people here do to keep up
  • Attending industry webinars and conferences (e.g., TestBash, EuroSTAR) to stay current with testing trends.
  • Contributing to open-source testing projects or building personal automation projects.
  • Taking online courses on advanced test automation frameworks, performance testing, or security testing.
  • Participating in internal knowledge-sharing sessions or presenting on a topic you're passionate about.
  • Mentoring junior colleagues or new starters, which is a great way to solidify your own understanding.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Prompt Engineering for Test Automation

Large Language Models (LLMs) are rapidly changing how we generate code and content. Being able to 'talk' to these models effectively to generate test scripts, data, or summaries will be a massive productivity booster for QA engineers.

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

Your PlanIllustration

Built for Head of QA

2 units that map to this job, from the qualifications that cover it.

  1. Testing engineering softwareExcellence, Achievement & Learning Limited · covers 3 of 8 standardsLevel 3
  2. Engineering software testingExcellence, Achievement & Learning Limited · covers 3 of 8 standardsLevel 4
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering for Test Automation

Large Language Models (LLMs) are rapidly changing how we generate code and content. Being able to 'talk' to these models effectively to generate test scripts, data, or summaries will be a massive productivity booster for QA engineers.

  • Clear and concise prompting
  • Context windows and token limits
  • Output validation
  • Few-shot prompting

What you’ll use

Skills this role draws on

Technical

  • Test Strategy & Planning (Feature Level)
  • Shift-Left Testing Principles
  • Risk-Based Testing (RBT)
  • Behaviour-Driven Development (BDD) Understanding
  • Quality Metrics & Basic Analytics
  • Test Data Management (TDM)

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Associate QA Analyst / Junior QA Engineer

    2-3 years

    Skills to master

    • Mastering test execution, clear bug reporting, understanding basic automation concepts, and getting familiar with the SDLC.

    You're ready to move on when

    • Consistently delivering high-quality bug reports with minimal clarification needed.
    • Successfully executing assigned test cases and understanding their purpose.
    • Starting to write and debug simple automated test scripts independently.
    • Proactively identifying minor improvements to test processes.
  2. 2

    Developer with a passion for Quality

    3-4 years (transitioning from Dev role)

    Skills to master

    • Deepening understanding of testing methodologies, learning specific QA tools, and shifting focus from 'building' to 'breaking' and ensuring reliability.

    You're ready to move on when

    • Demonstrable experience writing robust unit and integration tests as a developer.
    • A clear desire to specialise in quality, not just development.
    • Strong debugging skills and an eye for detail in code quality.
    • Understanding of how to build testable software.
  3. 3

    QA Bootcamp Graduate with Industry Experience

    2-3 years post-bootcamp

    Skills to master

    • Applying bootcamp knowledge in a real-world, complex product environment, gaining hands-on experience with enterprise-level tools and collaboration.

    You're ready to move on when

    • A strong portfolio of automation projects from the bootcamp and subsequent roles.
    • Positive feedback from previous managers on problem-solving and adaptability.
    • Demonstrated ability to quickly learn and apply new technical skills in a professional setting.

11Where this role leads

The long view:Your journey as a QA Engineer at Zavmo is just the beginning. We're committed to providing the opportunities, mentorship, and resources you need to build a truly impactful and rewarding career in quality assurance.

Pay & demand

Pay and demand for this role will appear here, each figure traced to a named authoritative source (e.g. the ONS Annual Survey of Hours and Earnings, under the Open Government Licence). We don’t show numbers we can’t attribute.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Head of QA is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

Where it leads

Roles this leads to

12The team that's yours

No two people are taught the same way. This is one-to-one, not one-to-many.

Zavmo is a hyper-personalised AI learning platform. Twelve virtual tutors, each with a different way of teaching, and one orchestration agent that picks the right one for the moment. So every single lesson is shaped around you, your role, and the way you learn. Not a course everyone sits through. A conversation built for you, and no one else.

…and nine more, matched to you after your first chat. Meet all twelve

Start free and meet yours

13What it feels like

A conversation, not a course

Because your tutor knows your role, your projects and your last session, learning sounds like this. And it's different for every single person:

Testing engineering softwareLevel 3

Applied to your work in Head of QA

This unit aims to provide learners with the skills to plan and perform testing activities for engineering software, while maintaining a safe working environment and adhering to relevant health and safety regulations. Learners will also demonstrate the required occupational behaviours in line with their job role and company objectives.

How the thinking builds
  1. Remember
  2. Understand
  3. Apply
  4. Analyse
  5. Evaluate
  6. Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

One to one, not one to many

No two people run this the same way

A course is written once and handed to everyone. This is assembled around you, and keeps changing as it learns you. Five things it reads, and what each one changes.

  1. Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
  2. What you already know The first conversation finds your starting point, so you skip what you can already do and spend the time on what you cannot.
  3. The conditions you learn under Not a learning-styles quiz. The evidence does not support those. The dimensions the research does back, read once and used to shape the plan.
  4. How far you got last time It picks up mid-thought. The tutor knows what you said, what you struggled with, and what it asked you to try.
  5. Which tutor suits the moment Twelve of them, each for a different kind of thinking. The one who walks you through a first idea is not the one who stress-tests it.

See how you learn, free. Eight questions, no sign-up. A directional taster; the diagnostic inside Zavmo goes deeper and keeps adapting.

DemonstrateIllustration

Evidenced on your work in Head of QA

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

  • Bug Report Clarity & ReproducibilityThe percentage of your bug reports that developers accept without needing further clarification or failing to reproduce.You reported 20 bugs this month; 18 were accepted immediately, 2 needed a quick chat. That's a 10% clarification rate, which is spot on.<10% rejection/clarification rate
  • Automated Test Coverage (Feature Level)The percentage of critical paths within the features you own that are covered by robust, automated tests.For the new 'User Profile' feature, you added automated tests covering 80% of the key user flows, exceeding the target.Achieve 75% coverage for new features within 2 weeks of code complete
  • Regression Test Execution & Pass RateHow consistently you execute assigned regression test cases and the stability of those tests (i.e., not flaky).Before the last release, you ran all 150 of your assigned regression tests, with 145 passing first time. The 5 failures were legitimate bugs, not flaky tests.Execute 95% of assigned regression test cases within the release window; >90% pass rate for your owned tests
  • Defect Discovery Rate (Pre-Production)The number of significant bugs you find in new features before they even get close to production.For the 'Basket Checkout' revamp, you found 4 high-severity bugs related to payment processing before it went live, saving us a massive headache.Find an average of 3-5 critical/high severity bugs per major feature release
These are this job's own measures, with its own targets. Nothing is marked evidenced, because nobody has started this yet. Yours would fill in from the work you bring.

Your passport

This isn't a certificate you file away. It's a passport to the life you're designing.

Every credit you earn and every fluency you build adds up: evidence where it counts, carried with you. Zavmo keeps the map: where you are, where you're heading, and the next step, at your pace, around your life. From Head of QA to Senior QA Engineer (Level 3), and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior QA Engineer (Level 3)→ your design
Where this takes you

Your journey as a QA Engineer at Zavmo is just the beginning. We're committed to providing the opportunities, mentorship, and resources you need to build a truly impactful and rewarding career in quality assurance.

See Your Progress GrowIllustration
Head of QA
  • Test Strategy & Planning (Feature Level)
  • Shift-Left Testing Principles
  • Risk-Based Testing (RBT)
  • Behaviour-Driven Development (BDD) Understanding
  • Quality Metrics & Basic Analytics
  • Test Data Management (TDM)
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

14The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Head of QA is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior QA Engineer (Level 3)

    3-5 years in this Mid-Level role

    You'll move from owning features to owning entire workstreams or complex projects, mentoring others, and significantly influencing our test strategy.

    • Designing and building scalable test automation frameworks from scratch.
    • Leading complex performance testing efforts.
    • Deep expertise in a specific testing domain (e.g., security, accessibility).
    • Advanced data analysis for quality metrics and trends.
    • Representing QA in broader technical discussions.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, some parts of QA can be a bit repetitive. But what if you could offload the grunt work and focus on the really interesting stuff – like exploratory testing or designing complex scenarios? AI isn't here to replace you; it's here to make you a more powerful, efficient QA Engineer.

As a Head of QA (Mid-Level), you're already writing automated tests and managing test data. Imagine if an intelligent assistant could handle the first draft of your scripts or generate realistic data sets in seconds. That's the reality with AI. It's about giving you back valuable time to focus on what truly matters: finding the hard-to-catch bugs and ensuring a top-notch user experience.

Test Script Auto-Generation

Use AI tools like Applitools or Testim to watch you perform manual tests, then automatically generate resilient Cypress or Playwright scripts. This cuts down the tedious initial scripting time, letting you focus on refining and maintaining them. Think of it as having a junior engineer who writes perfect boilerplate code.

Intelligent Test Data Generation

Stop manually creating test data! AI-powered tools can generate vast, realistic, and context-aware data sets for your features, covering edge cases and data permutations you might miss. This is especially handy for performance or security testing, giving you much richer scenarios to work with.

Predictive Defect Analysis (for your features)

Point an AI at your feature's code commits and historical defect data. It can then predict which parts of your code are most likely to contain new bugs. This lets you focus your testing efforts where they're most needed, making your risk-based testing even smarter and more targeted.

Automated Bug Report Summaries

Feed your raw test results and bug details into an AI assistant and ask it to draft a concise, clear summary for your daily stand-up or a quick update to a Product Owner. It'll help you articulate issues faster and more effectively, saving you a few minutes every day.

Common questions

Common questions

How do you become a Head of QA?

Common routes in include Associate QA Analyst / Junior QA Engineer (2-3 years), Developer with a passion for Quality (3-4 years (transitioning from Dev role)) and QA Bootcamp Graduate with Industry Experience (2-3 years post-bootcamp). Times vary with prior experience.

Where can a Head of QA progress to?

This role can lead on to Senior QA Engineer (Level 3) (3-5 years in this Mid-Level role), depending on the skills you build.

What level is a Head of QA in the UK?

This role aligns to RQF Level 3 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for a Head of QA?

Increasingly, Prompt Engineering for Test Automation. These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows a Head of QA, works on the job you actually do, and keeps going at your pace rather than a timetable's.

  • Searching and planning stay free. You only pay when you start learning.
  • Your credits are yours. Regulated, and they don't vanish when a subscription ends.
  • Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 8 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming a Head of QA: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.
Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you'll gain here are highly transferable across the tech industry. Whether you want to specialise in specific domains (e.g., FinTech, HealthTech, Gaming) or move into broader engineering leadership roles, a strong QA background is always in demand.

Not sure this is the right direction?

Work out what you actually want from work first, then come back and see which roles fit it. Takes about ten minutes.

This role profile is © 2026Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Build my plan, free Here's the first ten minutes: a 2-minute confidence check → your personalised roadmap → meet the tutors matched to you. No card, cancel any time. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.