UK

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

Associate Technical Director

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

Also advertised as Junior Technical Director · Technical Assistant · Technical Support Engineer (Entry) · Technical Coordinator

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 Technical Director

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 about leading a team just yet; it's about getting your hands dirty and learning the ropes. You'll be the person supporting our core technical operations, making sure everything runs smoothly under the watchful eye of a more experienced Technical Director. Think of it as your technical apprenticeship, where you'll build foundational skills and really understand how our systems tick. We're looking for someone keen to learn, eager to contribute, and ready to absorb everything about our technical landscape. It's a proper entry point into a challenging, but ultimately rewarding, technical career.

2What you'd actually use

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

Cloud Platforms (AWS, GCP, or Azure)Basic

You'll be deploying simple applications to pre-configured services like EC2 instances or S3 buckets, and navigating the console to check logs or resource status. You'll follow existing infrastructure patterns.

Containerization (Docker)Basic

You'll write basic Dockerfiles for your applications and understand how to build and run containers locally. You might deploy services using existing Helm charts or Kubernetes manifests under supervision.

CI/CD & DevOps (GitLab CI or GitHub Actions)Basic

You'll commit code that triggers existing pipelines, understand the different build and test stages, and be able to fix a simple broken build if it's related to your changes.

Observability (Prometheus/Grafana or Datadog)Basic

You'll use pre-built dashboards to monitor application health, add custom metrics or logs to your code, and respond to basic alerts by checking runbooks.

Infrastructure as Code (Terraform)Basic

You'll make minor, guided modifications to existing Terraform modules or Pulumi stacks, understanding the basic syntax and how changes are applied.

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
Technical Approach for a Small TaskPropose an approach to your Technical Director, but they'll make the final call. You'll explain your reasoning.Decide on the approach for routine tasks within established patterns; consult your manager on novel situations.Make independent technical decisions for entire workstreams, consulting with peers for complex trade-offs.
Production System ChangesNever make changes to production systems without explicit, step-by-step guidance and direct supervision from a senior engineer. All changes must be reviewed and approved.Execute pre-approved, well-documented changes to production systems. Escalate any unexpected behaviour immediately.Approve and oversee significant changes to production systems, including rollback plans and impact assessments.
Tool/Library Selection for a ProjectSuggest tools you've learned about, but the decision rests with your Technical Director or the project lead.Recommend tools/libraries for specific project components, providing a brief justification. Decision still needs team consensus.Make final decisions on tool/library selection for workstreams, considering long-term maintenance and team expertise.

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.

Task Completion Rate
How many of your assigned technical tasks do you actually finish within the agreed timeframe?
Target · Consistently above 90% of assigned tasks

If you're given 10 tasks in a week, you should aim to complete at least 9 of them. If you're stuck, you'll ask for help before the deadline, not after.

Code/Configuration Quality
The number of critical or major issues raised during code or infrastructure configuration reviews by senior team members.
Target · Fewer than 5 critical/major comments per pull request or configuration change

You submit a configuration change for review. If a senior engineer finds only minor stylistic suggestions, that's great. If they find a security vulnerability or a major logical error, that would count as a critical comment.

Learning Goal Achievement
How consistently you hit your agreed-upon learning objectives and skill development targets.
Target · Achieve 1-2 new certifications or demonstrate proficiency in new tools/technologies annually

You set a goal to get your AWS Cloud Practitioner certification. Successfully passing that exam and then applying some basic AWS concepts in a project would be a win.

Proactive Learning & Questioning
How often you seek out knowledge, ask clarifying questions, and show initiative in understanding complex topics rather than waiting to be told.
  • You'll be asking 'why' a lot, suggesting small improvements (even if they're not taken up), and bringing new ideas you've learned to team discussions. Your Technical Director will notice you're actively trying to connect the dots and understand the bigger picture, not just follow instructions blindly.
Team Collaboration & Support
Your willingness to help out team members, share what you've learned, and contribute positively to the team environment.
  • You'll offer to help a peer with a task if your own work is done, share useful resources you've found, and participate constructively in team meetings. People will feel comfortable asking you for a hand with something basic, and you'll be seen as a helpful presence.
Adherence to Standards & Best Practices
How well you follow our established coding standards, documentation guidelines, and operational procedures.
  • Your pull requests will consistently meet our style guides, your documentation will be clear and follow templates, and you'll stick to the agreed processes for deployments or incident response. This shows you're internalising our way of working and building good habits from the start.

5Would you like it

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

What people enjoy
Mastering New Technologies

You'll be spending a good chunk of your week digging into new tools, frameworks, and cloud services. This might mean following online courses, reading technical blogs, or just messing around with new code in a sandbox environment.

You're excited to learn Terraform and spend your lunch breaks watching tutorials, then volunteer to make a small change to an existing module.

Solving Tangible Technical Puzzles

You'll be given specific, well-defined technical problems to solve, like fixing a bug in a script, optimising a small piece of configuration, or setting up a new service using existing patterns. You love the feeling of getting something to work.

You're given a bug report about a service not starting correctly. You methodically go through the logs, trace the issue, and implement a fix that gets it running again.

Being Part of a Supportive Technical Team

You'll be working closely with your Technical Director and other engineers, participating in daily stand-ups, asking questions, and getting regular feedback. You value the camaraderie and the chance to learn from experienced professionals.

You actively participate in code reviews, both giving and receiving feedback, and feel comfortable asking your manager for help when you're genuinely stuck.

What frustrates people
  • Getting stuck on a bug for hours with no clear path forward, even after trying everything you know.
  • Having to ask for help on something you feel you 'should' know, but just haven't learned yet.
  • The sheer volume of new information to absorb; it can feel like drinking from a firehose sometimes.
  • Dealing with legacy systems that are poorly documented and hard to understand.
  • The 'boring' but essential tasks like updating documentation or running routine checks.
What this role does not give you
  • High-level strategic decision-making or budget control.
  • Leading a team or managing direct reports.
  • Complete autonomy over your projects from inception to delivery.
  • A quiet, predictable environment where nothing ever changes.

6Who you work with

Your impact, while foundational, is crucial. You'll be directly supporting the smooth running of our technical infrastructure and projects. Essentially, you're helping to build the bedrock that allows our more complex technical initiatives to succeed. Getting things right means less friction for everyone else; getting them wrong could mean small delays that add up.

Inside the business
  • Your immediate Technical Director and the wider Technical_roles team
  • Senior Technical Directors, who you'll occasionally support with specific tasks
  • Development teams, who you'll help by fixing smaller issues or providing basic support
  • Operations teams, as you'll assist in monitoring and maintaining live systems
Outside the business
  • None directly. Your focus will be internal, learning our systems and processes.

7What you need before you start

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

  • A foundational grasp of at least one modern programming language (e.g., Python, Java, Go, C#) – you should be able to write basic programs, understand control flow, and use data structures.
  • Familiarity with command-line interfaces and basic Linux commands.
  • An understanding of fundamental computer science concepts like data structures, algorithms, and object-oriented programming (if applicable to your language).
  • Experience with Git for version control, even if it's just for personal projects.
  • A genuine passion for technology and a demonstrable history of self-learning (e.g., personal projects, online course completions, open-source contributions).

8What to practise next

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

Deepening Programming & Scripting Expertise

You'll move beyond basic syntax to writing more efficient, robust, and testable code. You'll learn advanced language features and design patterns to solve more complex problems.

Unit & Integration Testing · Code Optimisation · API Design Principles

  • This week: Focus on writing unit tests for every new function you create.
  • This month: Read up on common design patterns in your primary programming language.
  • Month 2: Volunteer to refactor a small, inefficient piece of existing code.
  • Month 3: Take an online course on advanced topics in your chosen language.

Quick win: Start writing comments that explain the 'why' behind your code, not just the 'what'. This forces you to think more deeply about your design.

Advanced Cloud Service Understanding

You'll need to understand a wider array of cloud services and how to combine them effectively to build resilient and scalable applications. This moves beyond just 'using' a service to 'designing with' it.

Serverless Architectures · Managed Database Services · Networking & Security in the Cloud

  • This week: Pick one new cloud service you haven't used and read its documentation.
  • This month: Try to build a small, simple application using a serverless approach.
  • Month 2: Explore the networking configurations of one of our existing cloud environments.
  • Month 3: Aim for a more advanced cloud certification (e.g., AWS Solutions Architect Associate).

Quick win: Whenever you encounter a new cloud service in our infrastructure, take five minutes to look up what it does and why we use it.

9Staying current once you are in

What people here do to keep up
  • Actively participate in online technical communities and forums (e.g., Stack Overflow, Reddit's r/devops).
  • Contribute to open-source projects, even if it's just fixing a typo or improving documentation.
  • Attend virtual tech meetups, webinars, or conferences to stay current with industry trends.
  • Dedicate time each week to personal learning projects, experimenting with new technologies or building small applications.
  • Engage in pair programming sessions with senior engineers to learn directly from their experience.

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 Technical Tasks

AI co-pilots are changing how we write code, debug, and understand complex systems. Learning to talk to these tools effectively—to get the best, most accurate, and most useful output—is quickly becoming a core technical skill. It's about being able to instruct an AI to do exactly what you need.

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

Your PlanIllustration

Built for Associate Technical Director

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

  1. Assisting in Producing Technical Information for Engineering ActivitiesPearson Education Ltd · covers 1 of 1 standardsLevel 2
  2. Producing Technical Information for Engineering ActivitiesExcellence, Achievement & Learning Limited · covers 1 of 1 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.

Prompt Engineering for Technical Tasks

AI co-pilots are changing how we write code, debug, and understand complex systems. Learning to talk to these tools effectively—to get the best, most accurate, and most useful output—is quickly becoming a core technical skill. It's about being able to instruct an AI to do exactly what you need.

  • Clear & Concise Prompting
  • Context Provision
  • Iterative Prompting
  • Output Validation

Basic Cloud Cost Awareness (FinOps)

Cloud costs can spiral out of control if not managed. Even at an Associate level, understanding that every resource you spin up has a cost, and knowing how to identify basic inefficiencies, will become increasingly valuable. It's about being a responsible cloud citizen.

  • Resource Tagging
  • Cost of Idle Resources
  • Basic Pricing Models
  • Monitoring Cloud Spend

What you’ll use

Skills this role draws on

Technical

  • Basic Programming & Scripting
  • Version Control (Git)
  • Linux/Unix Fundamentals
  • Networking Basics
  • Software Development Lifecycle (SDLC)

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

    0-1 year post-graduation

    Skills to master

    • Translating academic theory into practical application, understanding real-world system constraints, collaborating in a professional team environment, and learning specific industry tools.

    You're ready to move on when

    • Completed relevant internships during university.
    • Strong academic record in technical subjects.
    • Demonstrable personal projects or contributions to open source.
    • A clear understanding of basic software development processes.
  2. 2

    Coding Bootcamp / Apprenticeship Graduate

    0-1 year post-programme completion

    Skills to master

    • Deepening practical coding skills, understanding system architecture beyond isolated projects, building resilience in a professional setting, and adapting to specific company tech stacks.

    You're ready to move on when

    • Strong portfolio of projects from the bootcamp/apprenticeship.
    • Positive recommendations from programme instructors.
    • Ability to articulate technical concepts clearly.
    • Demonstrated ability to learn quickly and adapt to new challenges.
  3. 3

    Self-Taught Developer / Career Changer

    1-2 years of self-directed learning or prior relevant experience

    Skills to master

    • Formalising self-taught knowledge, understanding enterprise-level systems, working within structured teams and processes, and filling any gaps in foundational computer science concepts.

    You're ready to move on when

    • An impressive portfolio of personal projects, showcasing diverse technical skills.
    • Active contributions to open-source projects or a strong online technical presence.
    • Ability to explain complex technical topics clearly and concisely.
    • A clear narrative about why you're transitioning into a technical role.

11Where this role leads

The long view:Your journey starts here. We're looking for someone who sees this Associate role not just as a job, but as the first exciting step in a long and impactful technical career. We'll provide the opportunities, the challenges, and the support; you bring the curiosity, the drive, and the willingness to learn. Let's build something great together.

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 Technical Director 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:

  • Technical Director (Mid-Level)

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:

Assisting in Producing Technical Information for Engineering ActivitiesLevel 2

Applied to your work in Associate Technical Director

This unit aims to equip learners with the skills to assist in producing technical information for engineering activities, underpinned by the knowledge of technical documentation requirements.

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 Technical Director

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.

  • Task Completion RateHow many of your assigned technical tasks do you actually finish within the agreed timeframe?If you're given 10 tasks in a week, you should aim to complete at least 9 of them. If you're stuck, you'll ask for help before the deadline, not after.Consistently above 90% of assigned tasks
  • Code/Configuration QualityThe number of critical or major issues raised during code or infrastructure configuration reviews by senior team members.You submit a configuration change for review. If a senior engineer finds only minor stylistic suggestions, that's great. If they find a security vulnerability or a major logical error, that would count as a critical comment.Fewer than 5 critical/major comments per pull request or configuration change
  • Learning Goal AchievementHow consistently you hit your agreed-upon learning objectives and skill development targets.You set a goal to get your AWS Cloud Practitioner certification. Successfully passing that exam and then applying some basic AWS concepts in a project would be a win.Achieve 1-2 new certifications or demonstrate proficiency in new tools/technologies annually
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 Technical Director to Technical Director (Mid-Level), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Technical Director (Mid-Level)→ your design
Where this takes you

Your journey starts here. We're looking for someone who sees this Associate role not just as a job, but as the first exciting step in a long and impactful technical career. We'll provide the opportunities, the challenges, and the support; you bring the curiosity, the drive, and the willingness to learn. Let's build something great together.

See Your Progress GrowIllustration
Associate Technical Director
  • Basic Programming & Scripting
  • Version Control (Git)
  • Linux/Unix Fundamentals
  • Networking Basics
  • Software Development Lifecycle (SDLC)
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 Technical Director is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Technical Director (Mid-Level)

    2-3 years in the Associate role

    You'll move from executing guided tasks to taking ownership of small-to-medium projects and making routine technical decisions independently.

    • Advanced Cloud Architecture: Designing and implementing solutions using a wider range of cloud services.
    • CI/CD Pipeline Ownership: Building and maintaining sections of our automated deployment pipelines.
    • Advanced Scripting & Automation: Writing more complex scripts to automate operational tasks.
    • Basic System Design: Contributing to the design of smaller system components.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, as an Associate Technical Director, you've got a lot to learn. AI isn't here to replace you; it's here to be your ultimate co-pilot, helping you learn faster, get unstuck quicker, and tackle those routine tasks with more efficiency. Think of it as having a super-smart assistant available 24/7.

We're embedding AI tools directly into our workflows to help you accelerate your journey. You'll learn how to use these tools not just as a crutch, but as a genuine extension of your technical capabilities, freeing up your brain for the really interesting, complex problems.

Code & Configuration Co-Pilot

Use AI assistants like GitHub Copilot or similar tools to generate boilerplate code, suggest syntax, and even help you write infrastructure-as-code configurations. It's brilliant for getting started quickly and learning best practices by example, saving you from endless Stack Overflow searches.

Documentation & Summarisation Assistant

Fed up with reading through massive technical specs or API docs? Use AI to summarise lengthy documents, extract key information, or even draft initial versions of your own internal documentation. This means less time reading, more time doing, and better quality docs.

Debugging & Error Explainer

When your code inevitably throws an obscure error, paste it into an AI tool (carefully, minding sensitive data!) and get instant explanations and potential fixes. It's like having a senior engineer looking over your shoulder, offering hints without judgment. Great for unblocking yourself faster.

Learning & Concept Accelerator

Struggling with a complex technical concept? Ask an AI to explain it in simpler terms, provide code examples, or even simulate scenarios. It's a personalised tutor that can adapt to your learning style and help you grasp new ideas much faster than traditional methods.

Common questions

Common questions

How do you become an Associate Technical Director?

Common routes in include University Graduate (Computer Science/Engineering) (0-1 year post-graduation), Coding Bootcamp / Apprenticeship Graduate (0-1 year post-programme completion) and Self-Taught Developer / Career Changer (1-2 years of self-directed learning or prior relevant experience). Times vary with prior experience.

Where can an Associate Technical Director progress to?

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

What level is an Associate Technical Director 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 Technical Director?

Increasingly, Prompt Engineering for Technical Tasks and Basic Cloud Cost Awareness (FinOps). 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 Technical Director, 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 1 national skill standard. 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 Technical Director: 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 as an Associate Technical Director are highly transferable. You'll be building a foundation in cloud computing, modern software development, and DevOps practices, which are in demand across virtually every industry sector that relies on technology. Whether you want to stay in our industry or move into FinTech, HealthTech, or E-commerce, your technical base will be solid.

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.