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

QA Engineer

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 or QA Lead
UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Software Tester · Test Engineer · Quality Analyst

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 QA Engineer

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

As a QA Engineer, you're the person who makes sure our software actually works as it should, day in, day out. You'll spend your time digging into new features, writing test cases, and hunting down those sneaky bugs before our customers ever see them. It's about being a detective for quality, ensuring what we build is robust and reliable. Honestly, you're the last line of defence before our code goes live, which is a pretty big deal.

2What you'd actually use

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

Jira (with Xray or Zephyr plugins)Intermediate

You'll be executing test plans, writing detailed bug reports (with logs and screenshots, obviously), and keeping ticket statuses updated. It's our central hub for all things project and quality.

Cypress or Selenium WebDriverBasic

You'll be running existing UI automation scripts, investigating why they failed, and making minor updates to locators if something shifts on the page. We don't expect you to build a framework from scratch yet, but you should be comfortable in the code.

Postman or InsomniaIntermediate

You'll be executing API requests from pre-built collections, checking status codes, and validating JSON responses. This is crucial for testing the 'backend' of our applications where the real logic often lives.

Apache JMeter or k6Basic

You'll run existing performance test scripts and gather basic metrics like response time. You won't be designing complex load tests yet, but understanding the output is important.

Git (Version Control System)Intermediate

You'll use Git for version control – cloning repositories, pulling the latest code, committing your changes (especially for automation scripts), and pushing them. It's how we manage all our code.

Jenkins or GitLab CIIntermediate

You'll be triggering builds in our CI/CD pipelines, checking the results of automated tests, and understanding if a new deployment has passed its quality gates. It's how we get code from development to production.

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 choice	Coming in	Where you are now	The step above
Test Case Design & Scope	Designs test cases under direct supervision; scope is limited to simple features. All designs reviewed.	Independently designs test cases for new features, including edge cases. Seeks input for complex scenarios. Owns scope for specific modules.	Defines test strategy and scope for entire workstreams. Reviews and approves test designs from junior team members. Makes recommendations on test coverage.
Bug Severity & Priority	Reports bugs with suggested severity; final priority set by supervisor or during triage.	Assigns initial severity and priority to bugs, justifying decisions. Escalates disagreements or critical issues for discussion in bug triage.	Leads bug triage meetings, makes final decisions on severity/priority for their workstream, and can override developer objections with sound reasoning.
Tool & Methodology Selection (within project)	Uses tools and methodologies as directed by supervisor.	May propose alternative testing tools or methodologies for specific problems, but needs approval from Senior QA or Lead.	Makes technical decisions on testing tools and methodologies for their projects, aligning with team standards. Can champion new approaches.
Automated Test Script Changes	Runs existing scripts, reports failures. Makes minor text/locator changes under guidance.	Maintains and updates existing automated test scripts (e.g., fixing flaky tests, updating locators, adding small new tests). Code reviewed by Senior QA or developer.	Develops complex automation scripts from scratch, designs reusable components, and defines best practices for automation within their area. Reviews junior automation code.

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.

Valid Bug Rate

The percentage of bugs you report that developers accept as legitimate and actionable, not 'can't repo' or 'not a bug'.

Target · Above 95%

If you report 20 bugs in a month and 19 of them are accepted and fixed, that's a 95% valid bug rate. It shows your reports are clear and accurate.

Test Case Execution Coverage

How much of the new feature's functionality you've covered with your test cases, compared to the total scope.

Target · Minimum 80% for critical paths

For a new login flow, you've written and executed tests for successful login, failed login, password reset, and 'remember me' functionality, covering 85% of the defined requirements. This means you've thought broadly about how users might interact with it.

Bug Report Clarity & Completeness

The number of times a developer needs to ask you for more information or clarification on a bug report.

Target · Fewer than 5% of your bug reports require clarification

Out of 15 bug reports, only one developer asked for an extra screenshot or a clearer reproduction step. That's a good sign your reports are precise.

Regression Test Maintenance

The percentage of existing regression tests you're responsible for that are kept up-to-date and passing, or clearly marked as needing attention.

Target · 90% accuracy and relevance

You own the regression suite for the 'checkout' flow. After a new release, all 50 tests in that suite are passing, or any failing ones have valid bug reports linked, showing you're on top of things.

Proactive Issue Identification

How often you spot potential problems or edge cases that weren't explicitly in the requirements, or identify risks early in the sprint.

You're bringing up 'what if' scenarios in sprint planning, suggesting additional test cases, or pointing out design flaws before development even starts. Developers and Product Managers say things like, 'Glad you thought of that!'

Collaboration with Development

How effectively you work with developers to understand and resolve bugs, rather than just throwing them over the fence.

Developers come to you for help reproducing tricky bugs, you're actively participating in bug triage, and you're seen as a partner in quality, not just a gatekeeper. You're helping them understand *why* a bug matters, not just *that* it exists.

Contribution to Test Automation

Your efforts in running, maintaining, and making small improvements to our automated test suites.

You're regularly running automated tests, investigating failures, and making minor code changes to keep them stable (e.g., updating a locator in Cypress). You might even propose a small new automated test for a critical path.

Learning & Application of New Techniques

Your willingness to learn new testing methodologies or tools and apply them to your daily work.

You're trying out a new test case design technique, experimenting with a different API testing approach, or sharing something you learned from an online course or article with the team. You're not just sticking to what you know.

5Would you like it

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

What people enjoy

Ensuring Product Quality

You get a real kick out of finding a critical bug before it hits production. You're driven by the idea that your work directly contributes to a stable, reliable product that customers trust. It's about pride in the craftsmanship of the software.

You spend an extra hour digging into a tricky edge case, find a data corruption bug, and feel a genuine sense of accomplishment knowing you saved the company a major headache and protected user data.

Problem Solving & Investigation

The hunt for a bug is exciting for you. You enjoy the challenge of piecing together clues, isolating variables, and figuring out the root cause of an issue. It's like solving a puzzle every day.

A developer says 'can't repo' but you persist, trying different browser versions and user roles until you find the exact steps to reproduce it, then clearly explain the 'why' behind the bug.

Learning & Skill Development

You're keen to pick up new tools, learn different testing techniques, and understand how the underlying systems work. You see every new feature or bug as an opportunity to expand your knowledge.

You volunteer to learn a new API testing tool or take an online course on performance testing, then try to apply what you've learned to your current project, even if it's just a small part.

What frustrates people

The 'Works on My Machine' Defence: Spending hours meticulously documenting a bug, only to have a developer dismiss it because they can't immediately reproduce it in their specific local environment. It's infuriating.
Vague Acceptance Criteria: Being asked to test a user story with requirements like 'the page should load fast' or 'the user experience should be intuitive'. What does that even mean? It leads to subjective and endless debates.
Pre-Release Pressure: Being the last gate before a release and facing immense pressure from management and product teams to 'just sign off' despite known, non-trivial bugs. It's a tough spot to be in.
Unstable Test Environments: Wasting significant time investigating 'bugs' that turn out to be issues with the testing environment itself (e.g., bad data, a downstream service is down, misconfiguration). It's a time sink.
Being the 'Bearer of Bad News': Consistently being the person who has to tell the team their hard work has flaws, and sometimes being perceived as a blocker rather than a collaborator. It's not always glamorous.

What this role does not give you

A quiet, predictable, and entirely independent work environment. You'll be talking to people, and priorities can shift.
Guaranteed immediate resolution for every bug you find. Some bugs are low priority, or might even be 'won't fix'.
A role where you're solely focused on coding new features. Your primary output is quality, not new functionality.
A role where you don't have to deal with messy, incomplete, or changing requirements. That's just the reality of software development.

6Who you work with

This role directly impacts product reliability and customer satisfaction. A good QA Engineer ensures fewer bugs make it to production, which means less downtime, fewer support tickets, and a better reputation for our software. You're essentially safeguarding our brand and making sure our development efforts translate into high-quality, usable products. Frankly, without solid QA, everything else falls apart eventually.

Inside the business

Software Development Team (your closest allies, and sometimes, friendly adversaries)
Product Managers (who define what we build)
UX/UI Designers (who care about the user experience)
DevOps Team (who handle deployments and environments)

Outside the business

End-users (ultimately, you're protecting their experience)
Customer Support (who deal with any escaped defects)

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 software testing role, where you've actively designed and executed test cases.
A solid understanding of at least one bug tracking tool (like Jira) and a test management system.
Experience with basic SQL queries for data validation (e.g., SELECT statements).
Familiarity with at least one programming or scripting language (e.g., Python, JavaScript) for understanding automation scripts, even if you're not writing them from scratch yet.
A demonstrable track record of finding and clearly reporting bugs in a professional software environment.

8What to practise next

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

Advanced Test Automation Scripting

As our products grow, manual testing becomes unsustainable. The ability to write robust, maintainable, and efficient automated tests will be crucial for keeping up with release cycles and ensuring comprehensive regression coverage.

Page Object Model (POM) · Test Data Management in Automation · API Test Automation Frameworks · CI/CD Pipeline Integration for Tests

This quarter: Take an online course on advanced Cypress or Selenium scripting, focusing on design patterns like POM.
Next quarter: Contribute a new, fully automated test case for a critical user flow, getting it reviewed by a Senior QA.
Month 6: Start exploring API test automation using a coding language, integrating it into a small project.

Quick win: Offer to refactor a small, existing flaky automated test to make it more stable. It's a great way to learn by doing.

Performance Testing Scripting & Analysis

Customers expect fast, responsive applications. Understanding how to design and execute basic performance tests, and then interpret the results, will be key to identifying bottlenecks before they impact users.

Load vs. Stress Testing · Key Performance Indicators (KPIs) · Workload Modelling · Basic Bottleneck Identification

This month: Read up on the basics of performance testing and the difference between various types of tests.
Next month: Run an existing JMeter or k6 script, then try to modify it slightly to test a different endpoint or increase user load.
Month 3: Work with a developer to interpret the results of a performance test, identifying potential areas for optimisation.

Quick win: Shadow a Senior QA or developer during a performance test review meeting to understand the language and concerns.

9Staying current once you are in

What people here do to keep up

Regularly contributing to open-source projects, especially those related to testing frameworks or tools.
Attending industry meetups, webinars, or conferences (like EuroSTAR or TestBash) to stay current with trends and network.
Taking online courses on platforms like Udemy, Coursera, or Pluralsight to deepen your skills in automation, performance testing, or a new programming language.
Reading relevant blogs, books, and articles on software testing best practices and emerging technologies.
Participating in internal knowledge-sharing sessions or presenting on a new technique you've learned to the team.

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 Case Generation

Generative AI is getting incredibly good at understanding natural language. Testers who can effectively 'talk' to these AIs will be able to generate comprehensive test cases and identify edge cases much faster than manual methods. It's about working *with* the AI, not being replaced by it.

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

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 Case Generation

Generative AI is getting incredibly good at understanding natural language. Testers who can effectively 'talk' to these AIs will be able to generate comprehensive test cases and identify edge cases much faster than manual methods. It's about working *with* the AI, not being replaced by it.

Context windows and token limits
Role-playing in prompts
Output validation strategies
Iterative prompting

What you’ll use

Skills this role draws on

Technical

Agile/Scrum Methodologies
Test Case Design & Management
Bug Triage & Root Cause Analysis (RCA)
Regression Testing Strategy
Exploratory Testing

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
Associate QA Engineer (L1)
1.5 - 2.5 years
Skills to master
- Mastering basic test execution, writing clear bug reports, understanding the SDLC, and getting comfortable with our core tools (Jira, Git). It's about learning the ropes and proving you can reliably follow instructions and spot issues.
You're ready to move on when
- Consistently delivering accurate and complete bug reports with minimal oversight.
- Successfully executing assigned test cases within estimated timeframes.
- Proactively asking clarifying questions about requirements and test scenarios.
- Demonstrating a solid grasp of our product's basic functionality and user flows.
2
Graduate Software Engineer (with a QA focus)
2 - 3 years
Skills to master
- Strong foundational coding skills, an understanding of software architecture, and a keen interest in quality. You'd typically spend time in development before transitioning to QA, bringing a developer's perspective to testing.
You're ready to move on when
- Successfully completing coding tasks and demonstrating clean, maintainable code.
- Showing a natural inclination to test your own code thoroughly and identify potential issues.
- Expressing a genuine passion for software quality and breaking things in a controlled way.
- Understanding the impact of code changes on system stability and performance.
3
Manual Tester from a different industry
2 - 4 years
Skills to master
- Adapting to our specific tools and processes, learning basic automation concepts, and understanding the technical nuances of our product. Your manual testing expertise is valuable, but you'll need to upskill on the technical side.
You're ready to move on when
- Quickly picking up our internal systems and testing methodologies.
- Demonstrating a strong aptitude for learning new technical skills (e.g., scripting languages, API testing tools).
- Consistently providing valuable insights from exploratory testing and user-centric perspectives.
- Successfully transitioning from purely manual testing to incorporating automated test execution and analysis.

11Where this role leads

The long view:Your journey here is what you make it. We're committed to providing the opportunities and support for you to grow, whether that's becoming a deep technical expert, leading teams, or branching out into other areas of the business. The best part? You'll always be at the heart of making sure we deliver amazing software.

Pay & demand

Typical pay £47,118 a year Source: ONS Annual Survey of Hours and Earnings, 2025 (provisional), under the Open Government Licence v3.0

The figure is the median for full-time employees in the ONS occupation this job title codes to (IT quality and testing professionals), from the April 2025 survey — about six months old when published, as ASHE always is. It is that occupation's middle, not this role's. Half earn more.

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 QA Engineer 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.

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:

Engineering software testingLevel 4

Applied to your work in QA Engineer

This unit aims to enable learners to understand and apply the principles of engineering software testing. Learners will gain the ability to plan, conduct, analyse, and evaluate software testing processes using appropriate tools and techniques, ensuring the effectiveness and quality of software development.

How the thinking builds

Remember
Understand
Apply
Analyse
Evaluate
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.

Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
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.
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.
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.
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 QA Engineer

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.

Valid Bug RateThe percentage of bugs you report that developers accept as legitimate and actionable, not 'can't repo' or 'not a bug'.If you report 20 bugs in a month and 19 of them are accepted and fixed, that's a 95% valid bug rate. It shows your reports are clear and accurate.Above 95%
Test Case Execution CoverageHow much of the new feature's functionality you've covered with your test cases, compared to the total scope.For a new login flow, you've written and executed tests for successful login, failed login, password reset, and 'remember me' functionality, covering 85% of the defined requirements. This means you've thought broadly about how users might interact with it.Minimum 80% for critical paths
Bug Report Clarity & CompletenessThe number of times a developer needs to ask you for more information or clarification on a bug report.Out of 15 bug reports, only one developer asked for an extra screenshot or a clearer reproduction step. That's a good sign your reports are precise.Fewer than 5% of your bug reports require clarification
Regression Test MaintenanceThe percentage of existing regression tests you're responsible for that are kept up-to-date and passing, or clearly marked as needing attention.You own the regression suite for the 'checkout' flow. After a new release, all 50 tests in that suite are passing, or any failing ones have valid bug reports linked, showing you're on top of things.90% accuracy and relevance

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 QA Engineer to Senior QA Engineer (L3), and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior QA Engineer (L3)→ your design

Where this takes you

Your journey here is what you make it. We're committed to providing the opportunities and support for you to grow, whether that's becoming a deep technical expert, leading teams, or branching out into other areas of the business. The best part? You'll always be at the heart of making sure we deliver amazing software.

See Your Progress GrowIllustration

QA Engineer

Agile/Scrum Methodologies
Test Case Design & Management
Bug Triage & Root Cause Analysis (RCA)
Regression Testing Strategy
Exploratory Testing

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

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

Senior QA Engineer (L3)
3 - 5 years in current role
You'll move from owning specific features to owning entire workstreams, mentoring junior QAs, and driving improvements to our testing processes and automation frameworks.
- Expert-level automation scripting: Building complex, reusable automation frameworks and components from scratch.
- Test strategy design: Defining comprehensive test strategies for large, complex features or product areas.
- Performance testing design: Designing and scripting new load and stress tests, and analysing results to pinpoint bottlenecks.
- Shift-left advocacy: Actively influencing product and development teams to embed quality earlier in the lifecycle.
SDET (Software Development Engineer in Test)
3 - 6 years in current role
This is a more technical, coding-heavy path. You'll spend more time writing and maintaining automation frameworks and tools, acting as a bridge between development and QA.
- Developing and maintaining custom test tools and utilities.
- Architecting and implementing advanced automation frameworks (e.g., integrating with CI/CD, reporting).
- Expertise in multiple programming languages relevant to our tech stack.
- Performance engineering: Optimising application performance through code analysis and testing.

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, even tedious. But what if you could offload those tasks to an AI, freeing you up for the really interesting, complex bug hunting and exploratory testing? This isn't science fiction; it's happening now. We're investing in AI tools to make our QA Engineers more effective, more efficient, and frankly, happier.

Our AI Productivity Hub is designed to take the grunt work out of your day, giving you back precious hours. Imagine less time writing boilerplate code and more time actually breaking the software in clever ways. Here's a peek at how AI can transform your daily grind as a QA Engineer:

Automated Test Script Generation

Feed AI tools your user stories or even design mockups, and watch them automatically generate baseline UI and API test scripts. This handles the repetitive setup code, letting you focus on refining the logic and adding specific assertions. You'll spend less time on the boring bits, more on the clever ones.

Flaky Test Analysis & Diagnosis

Ever spent hours trying to figure out why an automated test fails sometimes and passes others? Our AI can analyse thousands of CI/CD test runs, spot patterns in flaky tests, and even suggest the root cause (e.g., 'this test only fails when API X is slow' or 'it's a timing issue on slow environments'). It's like having a super-sleuth for your test suite.

Intelligent Edge Case & Test Data Generation

Struggling to think of every possible edge case for a new feature? Give a user story to a generative AI and ask it to 'act as a malicious user' or 'identify 10 unusual scenarios for this form'. It can also churn out realistic, anonymised test data (names, addresses, complex JSON payloads) so you don't have to manually create it. More creative testing, less manual data entry.

Smart Bug Reporting & Documentation

You've found a bug, you've got the steps, but writing that perfectly formatted report takes time. Use AI assistants to turn your quick notes or even voice-recorded observations into perfectly structured bug reports. The AI can auto-populate fields, suggest severity based on keywords, and even ensure all necessary logs are attached. More finding, less formatting.

Common questions

How do you become a QA Engineer?

Common routes in include Associate QA Engineer (L1) (1.5 - 2.5 years), Graduate Software Engineer (with a QA focus) (2 - 3 years) and Manual Tester from a different industry (2 - 4 years). Times vary with prior experience.

Where can a QA Engineer progress to?

This role can lead on to Senior QA Engineer (L3) (3 - 5 years in current role) and SDET (Software Development Engineer in Test) (3 - 6 years in current role), depending on the skills you build.

What level is a QA Engineer 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 QA Engineer?

Increasingly, Prompt Engineering for Test Case Generation. 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 QA Engineer, 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 10 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 QA Engineer: 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 Zavmo curriculum screen: a three-month plan built for a customer support lead, five Ofqual-regulated units and a hundred and ninety-six credits. — 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 as a QA Engineer are highly transferable. You could move into roles like Product Management (understanding quality helps define better products), Business Analysis (translating requirements accurately), or even back into Software Development (with a strong quality-first mindset). Your analytical and problem-solving abilities are valuable across the tech sector.

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.

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.

QA Engineer

What's rising in its place

Prompt Engineering for Test Case Generation

Skills this role draws on

Technical

How you actually get there, here

Associate QA Engineer (L1)

Graduate Software Engineer (with a QA focus)

Manual Tester from a different industry

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

Roles this leads to

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

A conversation, not a course

No two people run this the same way

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

Everything else the record holds

The career path, and where it branches

Senior QA Engineer (L3)

SDET (Software Development Engineer in Test)

Where AI is starting to help

Automated Test Script Generation

Flaky Test Analysis & Diagnosis

Intelligent Edge Case & Test Data Generation

Smart Bug Reporting & Documentation

Common questions

You’ve started things before

Less than one coaching session. Every month.

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