UK

United Kingdom · Technical roles · Entry Level (0-2 years)

Associate 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 bandEntry Level (0-2 years)
  • Direct reportsNo direct reports
  • Reports toQA Engineer or Senior QA Engineer
  • UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Junior Software Tester · Entry-Level QA Analyst · Software Quality Assistant

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 Associate 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

This isn't just about finding bugs; it's about learning the ropes of software quality, understanding how things break (and why), and getting your hands dirty with real-world testing. You'll be the fresh pair of eyes, the one who spots the obvious stuff everyone else missed because they're too close to the code. It's a foundational role, meaning you'll spend a fair bit of time learning our systems and processes. Honestly, it's a great spot to kick off a career in tech, especially if you're keen on making sure things actually work as they should.

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 use Jira daily to log bugs, update test case statuses, track your work, and read user stories. It's our central hub for everything development and QA related.

Git (Version Control System)Intermediate

You'll use Git to pull the latest code, switch branches, and understand how to check out different versions of the software for testing. No need to be a Git expert, but the basics are essential.

Postman or Insomnia (API Testing)Intermediate

You'll use these tools to execute pre-built API requests, check responses, and validate basic functionality of our backend services. This helps you test without needing a UI.

Cypress or Selenium WebDriver (UI Automation)Basic

You'll be running existing automated UI tests, analysing the results, and maybe making very minor updates to locators if something changes. You won't be writing complex scripts from scratch yet.

Apache JMeter or k6 (Performance Testing)Basic

You'll run pre-written performance test scripts and gather basic metrics like response times or error rates. It's about understanding what these tools do, not designing complex load tests.

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
Bug Severity & PriorityIdentify potential severity/priority, but always consult with and get approval from your QA Engineer or Senior QA Engineer before setting it in the system.Can assign initial severity/priority for routine bugs, but still consult on critical or blocking issues.Full authority to assign severity and priority for most bugs, only consulting on highly ambiguous or politically sensitive issues.
Test Scope & CoverageExecute assigned test cases within the defined scope. Do not deviate or add new tests without explicit approval from your supervisor.Can propose additional test cases or areas for exploration within a feature, seeking approval from the QA Lead.Defines test scope and coverage for specific features or components, making recommendations to the QA Lead or Product Owner.
Tool Selection & MethodologyUse the tools and methodologies provided. Do not introduce new tools or change processes without explicit instruction.Can research and propose alternative tools or minor process improvements to the QA Lead.Makes technical decisions regarding testing tools, frameworks, and methodologies for their workstream, with input from the QA Lead.

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 issues (not 'works as designed' or 'can't reproduce').
Target · >90% accepted as valid

If you report 10 bugs, we'd expect at least 9 of them to be confirmed and assigned to a developer for fixing. Anything less means we need to refine your bug reporting skills.

Test Case Execution Completion
How often you finish your assigned test runs within the estimated timeframes.
Target · Completes 95% of assigned test runs on schedule

If you're given 20 test cases to run in a day, we'd expect you to get through 19-20 of them. If you're consistently falling behind, we'll figure out why and help you speed up.

Bug Report Clarity Score
A measure of how clear, concise, and complete your bug reports are, based on feedback from developers and your QA lead.
Target · <10% of bug reports sent back for clarification

Out of 20 bug reports, we'd hope no more than 2 come back with developers saying 'I don't understand the steps' or 'where's the screenshot?'

Learning & Growth
How actively you seek out new knowledge, ask questions, and apply what you've learned to your daily tasks. It's about showing you're keen to develop.
  • You'll be asking thoughtful questions in daily stand-ups, taking notes during training, and showing you've taken feedback on board in subsequent tasks. We'll see you trying out new tools or techniques you've been shown, even if you need a bit of help.
Team Collaboration & Communication
How well you work with the rest of the QA team and developers. Are you a good listener? Do you ask for help when stuck? Can you explain what you've found clearly?
  • You're actively participating in team discussions, offering to help with straightforward tasks, and clearly communicating your findings (both verbally and in writing). People will say you're easy to work with and that your bug reports are easy to understand.
Adherence to Process
How consistently you follow our established testing procedures, documentation standards, and bug reporting guidelines. We have processes for a reason, and you'll need to stick to them.
  • Your test results are logged correctly, your bug reports follow the template, and you're using the right tools for the job. Your QA lead won't need to remind you constantly about the basics.

5Would you like it

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

What people enjoy
Solving Puzzles & Finding Flaws

You'll get a genuine kick out of reproducing a tricky bug or finding a new way to break a feature. The 'aha!' moment when you figure out the exact steps to make something fail will be truly satisfying.

Spending an hour trying different combinations of inputs on a form and finally hitting on the one that causes an error, then clearly documenting it.

Contributing to Product Quality

You'll feel proud knowing that the software going out to customers is better because of your careful work. You'll see your bug reports lead to fixes, making a tangible difference.

Seeing a feature you thoroughly tested go live without any major issues, knowing you played a part in that success.

Continuous Learning & Skill Development

You'll be eager to learn new testing techniques, understand different parts of the system, and pick up new tools. Every day will present an opportunity to expand your knowledge.

Taking the initiative to read up on a new testing concept after a team discussion, or asking your QA lead for resources to learn more about a specific tool.

What frustrates people
  • Running the same regression tests repeatedly, even when you're sure nothing has changed.
  • Spending ages writing a detailed bug report only for a developer to say 'can't repo' (can't reproduce it).
  • Being asked to 'just check' something without clear instructions or acceptance criteria.
  • Finding a bug, reporting it, and then seeing it sit in the backlog for ages without being fixed.
  • Dealing with test environments that are constantly breaking or aren't set up correctly, making it hard to actually test the software.
What this role does not give you
  • Full autonomy over project direction or technical decisions (not yet, anyway).
  • Significant coding or development responsibilities (it's more about testing, not building).
  • A quiet, solitary work environment (you'll be talking to people constantly).
  • Immediate, high-level strategic influence (that comes with more experience).

6Who you work with

Your work, while supervised, is crucial for catching obvious defects early in the development cycle. This means fewer embarrassing bugs make it to our customers, which saves us money, time, and keeps our reputation solid. Honestly, you're the first line of defence against bad software.

Inside the business
  • QA Team Lead (for guidance and process adherence)
  • Software Developers (you'll be reporting bugs to them, so a good relationship is key)
  • Product Owners (they define what needs to be built, you'll help ensure it works)
  • Other QA Engineers (you'll work alongside them, learning from their experience)

7What you need before you start

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

  • A keen eye for detail – you're the person who spots the typo in the menu or the button that's slightly off-centre.
  • Basic computer literacy – you're comfortable navigating operating systems, installing software, and using common office applications.
  • A methodical and organised approach to tasks – you like following steps and keeping things tidy.
  • Strong communication skills, both written and verbal – you can explain what you've found clearly.
  • A genuine curiosity about how things work and, perhaps more importantly, how they *don't* work.

8What to practise next

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

Basic Scripting for Test Automation

As you gain experience, you'll be expected to understand and eventually contribute to our automated test suites. This means learning the basics of a programming language (like Python or JavaScript) to read, understand, and make minor changes to existing automation scripts. This will become important within 12-18 months.

Variables and Data Types · Control Flow (If/Else, Loops) · Basic Functions · Locators (CSS Selectors, XPaths)

  • This month: Start an online course on Python or JavaScript fundamentals (Codecademy, freeCodeCamp are good starts).
  • Month 2: Ask your QA lead if you can shadow a more experienced QA Engineer who works on automation.
  • Month 3: Try to understand a simple automated test script from our codebase. Can you identify the steps it's taking?
  • Month 4: Attempt to make a very minor change to an existing script (e.g., updating a locator) under supervision.

Quick win: Install a code editor (like VS Code) and just start playing around with basic scripting tutorials. No pressure, just explore.

Enhanced API Testing & Validation

More and more applications rely heavily on APIs (Application Programming Interfaces). Moving beyond simply running pre-built requests, you'll need to understand how to construct more complex requests and thoroughly validate the responses. This is important within 9-12 months.

HTTP Methods (GET, POST, PUT, DELETE) · Request Headers & Body · JSON Structure & Validation · Status Codes (200, 400, 500 etc.)

  • This month: Explore Postman's learning resources or YouTube tutorials on API testing basics.
  • Month 2: Try to build a simple API request from scratch (e.g., a GET request to a public API) and interpret the response.
  • Month 3: Work with your QA lead to understand how our internal APIs are structured and what data they expect/return.
  • Month 4: Practice validating complex JSON responses, checking for specific data points and structures.

Quick win: Download Postman and explore some of the public API collections available. Just play around with sending requests and seeing what comes back.

9Staying current once you are in

What people here do to keep up
  • Participating in online courses or tutorials on software testing fundamentals, agile methodologies, or basic programming (e.g., Python or JavaScript).
  • Attending industry webinars or local meetups focused on QA and software development (we'll help you find them).
  • Reading relevant blogs, articles, and books to stay up-to-date with testing trends and best practices.
  • Contributing to open-source projects or personal projects where you can practice your testing skills.
  • Actively seeking feedback from your QA lead and peers, and using it to identify areas for personal growth.

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: Basic Prompt Engineering for QA Tasks

AI language models (like ChatGPT or Claude) are becoming incredibly powerful. Knowing how to ask them the right questions – 'prompt engineering' – will save you hours. They can help you draft bug reports, generate test data, or even brainstorm edge cases. This is critical within the next 6-12 months.

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

Your PlanIllustration

Built for Associate QA Engineer

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

  1. Testing Engineering SoftwareETC Awards Limited · covers 4 of 4 standardsLevel 3
  2. Analysing and interpret the results of mechanical testsExcellence, Achievement & Learning Limited · covers 1 of 4 standardsLevel 3
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.

Basic Prompt Engineering for QA Tasks

AI language models (like ChatGPT or Claude) are becoming incredibly powerful. Knowing how to ask them the right questions – 'prompt engineering' – will save you hours. They can help you draft bug reports, generate test data, or even brainstorm edge cases. This is critical within the next 6-12 months.

  • Clear Instruction Giving
  • Context Provision
  • Output Validation
  • Ethical Use of AI

What you’ll use

Skills this role draws on

Technical

  • Agile/Scrum Methodologies
  • Test Case Design & Management (Execution Focus)
  • Bug Triage & Root Cause Analysis (Reporting Focus)
  • Exploratory Testing (Guided)
  • Shift-Left Testing Principles (Awareness)

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

    University Graduate (Computer Science/Related)

    0-1 year post-graduation

    Skills to master

    • Translating theoretical knowledge into practical testing scenarios, understanding business context, adapting to agile workflows, mastering our specific tech stack.

    You're ready to move on when

    • Completed relevant final year projects involving software testing or quality assurance.
    • Demonstrated strong analytical and problem-solving skills in academic work.
    • Eagerness to learn and apply new tools and methodologies in a commercial setting.
  2. 2

    Apprenticeship / Vocational Training

    0-1 year post-apprenticeship completion

    Skills to master

    • Applying learned testing techniques in a real-world environment, effective bug reporting, understanding team dynamics, time management.

    You're ready to move on when

    • Completed a recognised apprenticeship programme in software development or testing.
    • Practical experience with basic testing tools and methodologies.
    • Strong work ethic and ability to follow instructions and processes.
  3. 3

    Career Changer / Self-Taught

    1-2 years of self-study or related experience

    Skills to master

    • Formalising self-taught knowledge into industry best practices, building a portfolio of tested projects, understanding software development lifecycles.

    You're ready to move on when

    • Can demonstrate personal projects where they've actively tested software and reported bugs.
    • Completed online courses or boot camps in software testing or related technical fields.
    • Strong motivation and ability to learn quickly, often bringing a fresh perspective from a previous career.

11Where this role leads

The long view:Your journey starts here, as an Associate QA Engineer. We're not just offering a job; we're offering a launchpad for a rewarding career in a critical field. We're excited to see where you'll take it.

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 Associate 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.

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

This unit aims to equip learners with the ability to perform tests on engineering software according to specified procedures, accurately recording results and reporting deviations. Learners will also gain knowledge of various software testing methods used in engineering, understanding their purpose, benefits, and the tools involved.

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 Associate 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 issues (not 'works as designed' or 'can't reproduce').If you report 10 bugs, we'd expect at least 9 of them to be confirmed and assigned to a developer for fixing. Anything less means we need to refine your bug reporting skills.>90% accepted as valid
  • Test Case Execution CompletionHow often you finish your assigned test runs within the estimated timeframes.If you're given 20 test cases to run in a day, we'd expect you to get through 19-20 of them. If you're consistently falling behind, we'll figure out why and help you speed up.Completes 95% of assigned test runs on schedule
  • Bug Report Clarity ScoreA measure of how clear, concise, and complete your bug reports are, based on feedback from developers and your QA lead.Out of 20 bug reports, we'd hope no more than 2 come back with developers saying 'I don't understand the steps' or 'where's the screenshot?'<10% of bug reports sent back for clarification
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 Associate QA Engineer to QA Engineer (Level 2), and whatever you decide comes after.

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

Your journey starts here, as an Associate QA Engineer. We're not just offering a job; we're offering a launchpad for a rewarding career in a critical field. We're excited to see where you'll take it.

See Your Progress GrowIllustration
Associate QA Engineer
  • Agile/Scrum Methodologies
  • Test Case Design & Management (Execution Focus)
  • Bug Triage & Root Cause Analysis (Reporting Focus)
  • Exploratory Testing (Guided)
  • Shift-Left Testing Principles (Awareness)
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

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

  1. QA Engineer (Level 2)

    2-3 years in the Associate role

    This is the natural next step. You'll move from executing pre-defined tests to designing your own, taking ownership of testing for specific features, and starting to contribute to automation.

    • Test Case Design: Creating comprehensive test cases from user stories and requirements.
    • Basic Test Automation: Writing and maintaining simple automated test scripts (e.g., UI or API tests).
    • Regression Testing Strategy: Helping to define and optimise the regression suite for specific features.
    • Advanced API Testing: Building more complex API requests and writing basic test scripts within Postman/Insomnia.
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, especially when you're just starting out. But what if you could offload some of that grunt work to an intelligent assistant? Our AI Productivity Hub isn't about replacing you; it's about giving you superpowers. Think of it as having a tireless intern who handles the tedious bits, freeing you up to focus on the really interesting stuff – like breaking things in creative ways!

Even at an Associate level, AI can significantly boost your efficiency. You'll use these tools to make your bug reporting sharper, your test data generation quicker, and even get a head start on understanding why some tests are so flaky. It means less time on the mundane, more time learning and contributing to genuine quality.

Automated Test Script Generation (Assisted)

Imagine feeding a user story or even a simple mockup into a tool, and it gives you a starting point for your test scripts. You'll still need to review and refine them, but it cuts out a huge chunk of the initial setup. This means you can get to the actual testing faster and focus on the nuances.

Flaky Test Analysis (Basic Insights)

Got a test that passes one day and fails the next without any code changes? It's a 'flaky test'. AI can help you by looking at patterns in past test runs and giving you hints about why it's misbehaving. You'll get suggestions like 'this test often fails when the database is under load', which helps you investigate smarter.

Edge Case & Test Data Generation (Guided)

Brainstorming all the weird ways a user might try to break a system, or coming up with realistic test data, can be tough. AI can act as a 'malicious user' for you, suggesting unusual inputs or edge cases you might not have thought of. It can also quickly generate lists of realistic names, addresses, or other data you need for testing.

Intelligent Bug Reporting (Drafting Support)

Turning your observations into a perfectly formatted, clear bug report takes practice. AI tools can help you draft these reports, ensuring all the necessary fields are populated, the steps are clear, and even suggesting severity based on your description. It's like having a proofreader and a template-filler all in one.

Common questions

Common questions

How do you become an Associate QA Engineer?

Common routes in include University Graduate (Computer Science/Related) (0-1 year post-graduation), Apprenticeship / Vocational Training (0-1 year post-apprenticeship completion) and Career Changer / Self-Taught (1-2 years of self-study or related experience). Times vary with prior experience.

Where can an Associate QA Engineer progress to?

This role can lead on to QA Engineer (Level 2) (2-3 years in the Associate role), depending on the skills you build.

What level is an Associate QA Engineer in the UK?

This role aligns to RQF Level 2 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 an Associate QA Engineer?

Increasingly, Basic Prompt Engineering for QA Tasks. 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 an Associate 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 4 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 an Associate 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 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 2

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 entire tech industry. Whether you want to move into different product domains (e.g., FinTech, HealthTech, E-commerce) or even pivot slightly into roles like Product Management (with your quality mindset) or Technical Support, your QA foundation will serve you well. Good testers are always in demand, everywhere.

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.