UK

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

Junior Software Testing Assistant

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 toSenior QA Engineer
  • UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Entry-Level QA Assistant · Trainee Software Tester · QA Support 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 Junior Software Testing Assistant

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 making sure our software works as it should. You'll be the first line of defence, really, catching the obvious stuff and helping the team keep things running smoothly. It's a hands-on role where you'll get stuck into the day-to-day testing of our products, working closely with more experienced testers to learn the craft.

2What you'd actually use

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

Jira / Azure DevOps (ADO)Intermediate

Creating, updating, and transitioning bug tickets. Attaching logs and screenshots. Following established workflows precisely.

TestRail / Zephyr for Jira / XrayIntermediate

Executing assigned test runs, accurately marking steps as pass/fail, and linking defects to test cases.

Postman / Insomnia (API Testing)Basic

Running pre-written API collections to check basic functionality. Understanding how to check response codes (200, 404) and validate simple JSON payloads.

Git (via GitHub, GitLab, Bitbucket)Basic

Using `git pull` or `git clone` to get the latest code or test scripts. Checking out a specific branch to test a feature.

Confluence / Slack / MS TeamsIntermediate

Documenting test results, communicating status effectively in team channels, and finding relevant project information.

SQL (via DBeaver, SQL Server Mgmt Studio)Basic

Running pre-written `SELECT` statements to verify data was created or updated correctly during a test, or to check simple database entries.

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 and priority, but always consult your Senior QA Engineer for final classification before logging. Don't guess.Assign initial severity and priority for routine bugs based on established guidelines; escalate exceptions for review.Determine final severity and priority for most bugs, lead bug triage, and make recommendations for release blockers.
Test Case CreationExecute test cases written by others. You might suggest small improvements but won't be writing full test suites yet.Write test cases for new features based on acceptance criteria, with review from a Senior QA Engineer.Design comprehensive test plans and test cases for entire features or modules, establishing best practices.
Test Environment SetupFollow instructions to use pre-configured test environments and test data. Report any issues you find.Independently set up and tear down test environments for specific features, including basic data manipulation.Manage and troubleshoot complex test environments, including coordinating with DevOps for infrastructure needs.
Tool Selection & UsageUse the specified bug tracking (Jira) and test case management (TestRail) tools as instructed. Learn their basic functions.Choose appropriate tools for specific testing tasks (e.g., Postman for API testing) within approved tech stack. May suggest new tools for evaluation.Evaluate, recommend, and implement new testing tools or frameworks for the team, defining their usage guidelines.

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.

Test Case Execution Rate
The percentage of assigned test cases you complete within a given sprint or release cycle.
Target · Consistently above 95%

If you're given 50 test cases for a sprint, you should aim to run at least 48 of them, marking each step accurately as pass or fail.

Valid Bug Find Rate
The proportion of bugs you report that are accepted by the development team as genuine defects, not 'works as designed' or 'cannot reproduce'.
Target · Above 85% after your first three months

Out of 20 bugs you report in a month, at least 17 should be accepted by developers for fixing, showing your reports are clear and valid.

Bug Report Clarity Score
How often your bug reports are returned by developers asking for more information or clarification.
Target · Fewer than 10% of your bug reports need clarification

If you file 15 bug reports, no more than one should come back with a 'needs more info' comment, meaning your steps to reproduce and details are usually spot on.

Adherence to Test Plans
How well you follow the established test plans and procedures, including using the right environments and data.
Target · No deviations from documented test plans unless approved

You're always testing on the correct server, using the specified test data, and following the step-by-step instructions in the test management tool.

Proactive Learning & Asking Questions
How actively you seek to understand new features, testing techniques, and the underlying systems, and how effectively you ask for help when stuck.
  • You'll ask thoughtful questions in daily stand-ups, seek out documentation, and proactively ask your mentor for explanations. You're not afraid to say 'I don't know' but follow it up with 'how can I find out?'
Team Collaboration & Communication
Your ability to work effectively with your immediate QA team and communicate clearly with developers and product owners.
  • You'll provide timely updates on your testing progress in team channels, participate constructively in bug triage meetings, and give clear, concise verbal explanations of issues you've found.
Attention to Detail in Execution
Your thoroughness in executing test cases, noting every detail, and not cutting corners.
  • You'll consistently attach relevant screenshots and logs to bug reports, double-check expected results against actual behaviour, and notice small UI glitches that others might miss.
Adaptability to Changing Priorities
How well you handle shifts in focus or urgent requests that might disrupt your planned testing activities.
  • When a 'hotfix' comes in, you're able to quickly pivot, understand the new priority, and pick up where you left off without much fuss. You'll ask for clarity on new priorities rather than just guessing.

5Would you like it

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

What people enjoy
Making Things Work Properly

You get a genuine kick out of finding a bug, reporting it clearly, and then seeing it fixed. You enjoy the satisfaction of knowing you've prevented a problem for a customer.

You've just spent an hour trying to break a new login flow, found a tricky edge case, reported it, and now it's fixed. That's a good day for you.

Learning and Developing New Skills

You're keen to absorb everything you can from your Senior QA Engineer and other team members. You actively seek out new tools and techniques, even if it's just reading up on them in your spare time.

You'll ask your mentor about API testing, read up on different test methodologies, and try to understand the 'why' behind what you're doing, not just the 'how'.

Being Part of a Team

You enjoy the camaraderie of working with developers and other testers towards a common goal. You're happy to help out where needed and contribute to team discussions.

You'll offer to help a colleague with a tricky test setup, participate actively in sprint retrospectives, and generally enjoy the collaborative buzz.

What frustrates people
  • Running the same 100+ manual regression tests for the third time this month.
  • A developer marking your bug as 'cannot reproduce' when you know it's there.
  • Test environments that are constantly flaky, slow, or full of bad data.
  • Being asked to test a feature with really vague or incomplete requirements.
  • The 'urgent' request that throws your whole day's plan out the window, only to be deprioritised later.
What this role does not give you
  • High-level strategic decision-making (not yet, anyway).
  • Building complex automation frameworks from scratch (you'll use them, but not build them).
  • Full autonomy over your work schedule and priorities (you'll have clear tasks and deadlines).
  • A quiet, solitary role – you'll be talking to people a lot.

6Who you work with

Your accurate testing and clear bug reports directly reduce the number of defects that slip into our live products. This means fewer customer complaints, less time spent on emergency fixes by developers, and ultimately, a better reputation for our software. You're building the trust our customers have in us, one bug at a time.

Inside the business
  • Senior QA Engineers and QA Leads (your immediate team, they'll guide you)
  • Software Developers (you'll be telling them what's broken, so good communication is key)
  • Product Owners (they define what needs building, you'll help ensure it works as intended)
  • Technical Support (they're on the front line with customers, so your work helps them)

7What you need before you start

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

  • A genuine curiosity about how software works (and breaks!).
  • Strong attention to detail – you're the person who notices the typo on a menu.
  • Good communication skills, both written and verbal, for talking to developers and writing bug reports.
  • Basic computer literacy, including using common office software and web browsers.
  • A logical and methodical approach to tasks – you like following steps and seeing things through.
  • A proactive attitude towards learning and asking questions when you're unsure.

8What to practise next

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

Basic Automation Script Understanding

Automation is key to faster, more reliable testing. Even if you're not writing scripts from scratch, understanding how they work will help you debug failures, provide better context to automation engineers, and eventually, contribute to them.

Locators (ID, XPath, CSS Selectors) · Basic Programming Logic · Test Framework Structure

  • This week: Ask an automation engineer to walk you through a simple automated test script for 15 minutes.
  • This month: Spend an hour or two trying out Selenium IDE to record and play back a simple user flow.
  • Month 2: Try to make a tiny, guided change to an existing automated test script (e.g., changing a piece of text it's looking for).
  • Month 3: Read some basic tutorials on Python or JavaScript syntax – just enough to understand the basics of code.

Quick win: When an automated test fails, try to look at the error logs and the script itself (with guidance) to understand *why* it failed, rather than just reporting the failure.

Advanced API Testing Concepts

More and more applications are built on APIs. Being able to test these directly, without needing a UI, is incredibly efficient for finding bugs earlier. You'll move beyond just running pre-written requests.

Authentication & Authorisation · Chaining Requests · Response Validation (Schema)

  • This week: Take a free online course on HTTP methods and REST APIs.
  • This month: In Postman, try to create a simple GET request from scratch to a public API (e.g., a weather API).
  • Month 2: Learn how to pass a variable from one Postman request to another.
  • Month 3: Work with a Senior QA Engineer to understand how they test a more complex API endpoint.

Quick win: Whenever you're testing a new feature, ask the developers if there are any APIs you can use to check the backend data directly, even if it's just running a simple pre-written query.

9Staying current once you are in

What people here do to keep up
  • Completing online courses in software testing fundamentals (e.g., on Udemy, Coursera, LinkedIn Learning).
  • Attending local QA meetups or webinars to learn from others in the industry.
  • Practising your bug reporting skills on open-source projects or 'bug bounty' platforms (even if it's just for learning).
  • Reading blogs and articles from experienced testers to keep up with industry best practices.
  • Getting hands-on with basic SQL tutorials to improve your database querying skills.

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 & AI Tool Interaction

AI tools, like ChatGPT or similar internal assistants, are becoming incredibly powerful for tasks like drafting bug reports, generating test data, or summarising documentation. Testers who can 'talk' to these AIs effectively will be far more productive.

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

Your PlanIllustration

Built for Junior Software Testing Assistant

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

  1. Testing Engineering SoftwareETC Awards Limited · covers 3 of 5 standardsLevel 3
  2. Assist in the Tests and Checks of Telecoms EquipmentETC Awards Limited · covers 1 of 5 standardsLevel 2
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 & AI Tool Interaction

AI tools, like ChatGPT or similar internal assistants, are becoming incredibly powerful for tasks like drafting bug reports, generating test data, or summarising documentation. Testers who can 'talk' to these AIs effectively will be far more productive.

  • Clear Prompting
  • Context Provision
  • Output Validation
  • Ethical Use

What you’ll use

Skills this role draws on

Technical

  • Manual Testing Techniques
  • Bug Reporting & Triage Fundamentals
  • Software Development Life Cycle (SDLC) Awareness
  • Basic Test Case Design Concepts

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/IT)

    0-1 year post-graduation

    Skills to master

    • Translating theoretical knowledge into practical testing scenarios, understanding real-world software development cycles, and adapting to team-specific tools and processes.

    You're ready to move on when

    • Completed relevant coursework or projects in software quality or testing.
    • Demonstrated ability to learn new programming languages or technical concepts quickly.
    • Strong academic record, especially in problem-solving subjects.
  2. 2

    Apprenticeship Programme

    Upon completion of a Level 3 or 4 IT/Software apprenticeship

    Skills to master

    • Applying learned principles in a commercial setting, working effectively within a professional team, and developing strong communication skills for bug reporting.

    You're ready to move on when

    • Successful completion of apprenticeship modules related to software testing.
    • Positive feedback from apprenticeship mentors and supervisors.
    • A portfolio of practical work or projects demonstrating testing aptitude.
  3. 3

    Career Changer (from a detail-oriented role)

    1-2 years of self-study or relevant previous experience

    Skills to master

    • Acquiring fundamental software testing concepts, learning technical tools (Jira, SQL basics), and understanding the software development lifecycle.

    You're ready to move on when

    • Evidence of strong attention to detail and process adherence in previous roles (e.g., administrative, data analysis).
    • Completed online courses or personal projects in software testing.
    • Clear articulation of why they want to move into software testing.

11Where this role leads

The long view:Your journey starts here, with a solid foundation in software quality. We're committed to helping you grow, learn, and build a rewarding career in technical roles. If you're keen to learn, meticulous, and enjoy making things work perfectly, you'll thrive with us.

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 Junior Software Testing Assistant 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

The record names a next step, but the catalogue has no page for it yet:

  • QA Analyst / Software Tester (Level 2)

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 Junior Software Testing Assistant

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 Junior Software Testing Assistant

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.

  • Test Case Execution RateThe percentage of assigned test cases you complete within a given sprint or release cycle.If you're given 50 test cases for a sprint, you should aim to run at least 48 of them, marking each step accurately as pass or fail.Consistently above 95%
  • Valid Bug Find RateThe proportion of bugs you report that are accepted by the development team as genuine defects, not 'works as designed' or 'cannot reproduce'.Out of 20 bugs you report in a month, at least 17 should be accepted by developers for fixing, showing your reports are clear and valid.Above 85% after your first three months
  • Bug Report Clarity ScoreHow often your bug reports are returned by developers asking for more information or clarification.If you file 15 bug reports, no more than one should come back with a 'needs more info' comment, meaning your steps to reproduce and details are usually spot on.Fewer than 10% of your bug reports need clarification
  • Adherence to Test PlansHow well you follow the established test plans and procedures, including using the right environments and data.You're always testing on the correct server, using the specified test data, and following the step-by-step instructions in the test management tool.No deviations from documented test plans unless approved
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 Junior Software Testing Assistant to QA Analyst / Software Tester (Level 2), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ QA Analyst / Software Tester (Level 2)→ your design
Where this takes you

Your journey starts here, with a solid foundation in software quality. We're committed to helping you grow, learn, and build a rewarding career in technical roles. If you're keen to learn, meticulous, and enjoy making things work perfectly, you'll thrive with us.

See Your Progress GrowIllustration
Junior Software Testing Assistant
  • Manual Testing Techniques
  • Bug Reporting & Triage Fundamentals
  • Software Development Life Cycle (SDLC) Awareness
  • Basic Test Case Design Concepts
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

Junior Software Testing Assistant is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. QA Analyst / Software Tester (Level 2)

    After 2-3 years in the Junior role

    This is your natural next step, moving from executing tasks to owning smaller features and beginning to design your own test cases. You'll have more autonomy and start to guide new juniors.

    • Test Case Design: Writing comprehensive test cases for new features based on acceptance criteria.
    • Exploratory Testing Mastery: More advanced, structured exploratory testing.
    • Basic API Test Scripting: Writing simple API tests in Postman or Insomnia.
    • Intermediate SQL: Writing more complex queries to set up and verify test data.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, some parts of testing can be a bit repetitive. Good news: AI is here to help! We're not talking about robots taking over your job, but rather smart tools that can take the grunt work out of your day, letting you focus on the interesting stuff – like actually breaking things.

Even as a Junior Software Testing Assistant, you'll find AI can give you a real edge. Think of it as having a super-efficient personal assistant for your daily testing tasks. It means less time on manual data entry or sifting through logs, and more time learning and applying your critical thinking.

AI-Assisted Bug Reporting

Use an AI assistant to draft perfectly formatted bug reports from your rough notes or a screen recording. It can automatically populate environment details, format steps, and suggest a clear, concise title. This means less time fiddling with formatting and more time finding the next bug.

Automated Test Data Generation

Instead of manually creating a few dozen test users or scenarios, use AI tools to generate thousands of realistic and diverse data sets for testing forms and databases (e.g., names, addresses, emails, edge-case numbers). This saves you hours and gives you much better test coverage.

Visual Regression Testing (Basic)

Leverage AI-powered tools that take screenshots of the application and automatically detect unintended visual changes (e.g., a button moved, a colour changed, text overflow). As a junior, you'll learn to interpret the AI's findings, saving you from tedious pixel-by-pixel comparisons across dozens of pages.

Log Analysis & Anomaly Detection

AI can quickly sift through huge log files, highlighting unusual patterns or error messages that a human might miss. You'll use these AI insights to pinpoint potential bug causes much faster, helping you provide better context in your bug reports.

Common questions

Common questions

How do you become a Junior Software Testing Assistant?

Common routes in include University Graduate (Computer Science/IT) (0-1 year post-graduation), Apprenticeship Programme (Upon completion of a Level 3 or 4 IT/Software apprenticeship) and Career Changer (from a detail-oriented role) (1-2 years of self-study or relevant previous experience). Times vary with prior experience.

Where can a Junior Software Testing Assistant progress to?

This role can lead on to QA Analyst / Software Tester (Level 2) (After 2-3 years in the Junior role), depending on the skills you build.

What level is a Junior Software Testing Assistant 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 a Junior Software Testing Assistant?

Increasingly, Prompt Engineering & AI Tool Interaction. 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 Junior Software Testing Assistant, 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 5 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 Junior Software Testing Assistant: 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 in software testing are highly transferable across almost any industry that builds software – from FinTech to healthcare, e-commerce to gaming. Quality is always in demand, so your career options will be wide open.

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.