UK

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

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

Also advertised as Junior Robotics Engineer · Robotics Technician · Robotics 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 Robotics Engineer

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

Start the check, free

1What this role really is

As an Associate Robotics Engineer, you'll be diving headfirst into the practical side of robotics. Think of yourself as an apprentice, learning the ropes from seasoned engineers. You'll be working on specific, well-defined tasks that contribute to larger robotics projects, helping us build and test the next generation of automated systems. It's a hands-on role where you'll get to see your code and designs come to life, usually within a few weeks of starting.

2What you'd actually use

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

ROS/ROS2 (Robot Operating System)Intermediate

Creating and debugging basic nodes, topics, and services for specific robot tasks. You'll be working with this every day.

Gazebo/NVIDIA Isaac SimIntermediate

Building and running basic simulations for component testing and validating simple robot behaviours. This helps us test without breaking real hardware.

SolidWorks/Fusion 360Intermediate

Designing parts and simple assemblies, modifying existing CAD models, and preparing files for 3D printing or fabrication.

InOrbit/Formant (Fleet Management)Basic User

Monitoring dashboards to check robot status, review logs, and understand basic fleet performance. You'll be reporting on what you see here.

AWS RoboMaker/Azure IoTBasic

Deploying pre-packaged applications to cloud-connected robots and monitoring basic telemetry data. You'll learn how cloud services support our robots.

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 TaskPropose an approach, but require approval from Senior Engineer.Choose approach for routine tasks, consult on novel ones.Define technical approach for workstreams, consult Director on major deviations.
Component Selection (Minor)Research options and recommend to Senior Engineer.Select components within pre-approved list, consult on new ones.Approve component selections within budget, define preferred vendor list.
Code Changes to Production SystemRequire full review and approval by Senior Engineer.Require peer review and Manager approval.Approve changes after peer review, accountable for impact.
Project Timeline AdjustmentsInform Senior Engineer of potential delays.Propose minor adjustments to Manager, inform stakeholders.Approve timeline adjustments within workstream, inform Director.

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 tasks (like coding a specific robot behaviour or designing a small component) you finish within the agreed timeframe.
Target · >80% of assigned tasks completed on time

If you're given five tasks this week, we'd expect you to get at least four of them done by Friday. We know things pop up, but consistent delivery is key.

Code Review Turnaround Time
The speed at which you respond to feedback on your code from senior engineers and make the necessary changes.
Target · < 1 business day for minor feedback, < 2 days for major

If a senior engineer reviews your code on Tuesday morning and flags a few things, we'd hope to see those changes pushed for re-review by Wednesday morning, or at least a clear plan of action.

Critical Bug Resolution Time
How quickly you fix any critical bugs or issues that are directly traced back to your work once they're identified.
Target · < 24 hours for critical bugs (with guidance)

If a robot stops moving because of a small error in your navigation code, we'd expect you to work with your senior engineer to get that fixed and tested within a day.

Documentation Adherence
How well you follow our established documentation templates and guidelines for your code, designs, and test results.
Target · Consistent adherence to 95% of documentation standards

Every piece of code you write should have clear comments, and any design work should be logged in our system using the right format. It's boring, but it saves future-you a headache.

Proactive Learning & Questioning
Your willingness to seek out knowledge, ask clarifying questions when unsure, and learn from mistakes without needing constant prompting.
  • You're asking 'why' something is done a certain way, suggesting alternative approaches (even if they're wrong, it shows thought), and you're not making the same mistake twice. You're also taking notes and referring back to them.
Collaboration & Team Fit
How well you work with the rest of the engineering team, contributing to a positive and productive environment.
  • You're offering to help teammates when your own tasks are done, you're receptive to feedback, and you're communicating clearly about your progress and any blockers. People actually enjoy working with you.
Problem-Solving Approach
How you approach challenges, from understanding the problem to proposing potential solutions (even if they need refinement).
  • When you hit a wall, you don't just stop. You've tried a few things, you can explain what didn't work, and you come to your senior engineer with a 'here's what I've tried' rather than just 'it's broken'.
Attention to Detail
The care you take in your work, catching small errors before they become bigger problems.
  • Your code compiles cleanly most of the time, your designs meet the specified tolerances, and you're double-checking your own work before submitting it for review. You spot the missing semi-colon that would have crashed the robot.

5Would you like it

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

What people enjoy
Learning New Technologies

You'll be excited to pick up new programming languages, robotics frameworks, or design software. You'll probably spend evenings watching tutorials or reading documentation, just because you're genuinely interested.

You might spend an hour after work playing with a new feature in ROS2 or trying out a different simulation environment, just to see what it can do.

Seeing Your Work Come to Life

There's a real thrill in writing code or designing a part and then seeing it actually control a robot or fit perfectly into an assembly. You'll love the tangible nature of robotics.

The first time you see a robot arm move exactly as you programmed it, or a component you designed being 3D printed, you'll get a real kick out of it.

Solving Technical Puzzles

You enjoy the process of debugging, figuring out why a sensor isn't working, or optimising a motion path. It's like a complex puzzle where the solution makes a robot better.

Spending an afternoon tracking down a tricky bug in a control loop, and finally getting the robot to move smoothly, will feel like a real victory.

What frustrates people
  • Debugging someone else's messy code (it happens, a lot).
  • Spending hours on a task only for the requirements to change completely.
  • Waiting for hardware components to arrive or be fixed, which can hold up your software work.
  • Dealing with legacy systems or tools that aren't quite 'state-of-the-art' but still need maintaining.
  • The '99% problem' – getting a robot to work 99% of the time is relatively easy; getting it to 99.999% is incredibly hard and time-consuming.
What this role does not give you
  • Full autonomy over project direction (you'll be guided, which is good for learning).
  • A quiet, predictable 9-to-5. Robotics can be a bit chaotic, especially during testing.
  • A role where you only ever work on the 'fun', cutting-edge stuff. There's plenty of essential but less glamorous work too.
  • Immediate recognition for major strategic decisions; your impact is more at the task level.

6Who you work with

Your work, though often focused on smaller pieces, is crucial for keeping our projects on track. You're helping to build the foundational elements that allow our more complex robotic systems to function. Get it right, and you're directly contributing to our ability to deliver reliable, efficient automation solutions to our clients. Get it wrong, and we might have to re-do work, which slows everyone down and costs us time and money.

Inside the business
  • Your Senior Robotics Engineer (for daily guidance)
  • The wider Robotics Engineering team (for collaboration and learning)
  • Manufacturing Operations (you'll sometimes get feedback from them on how your designs work in the real world)
Outside the business
  • Component suppliers (you might help research parts)
  • Academic partners (if we're working on a research project, you might help with data gathering)

7What you need before you start

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

  • A foundational understanding of linear algebra and calculus (you'll use it for kinematics and control).
  • Experience with at least one significant personal or academic robotics project (show us what you've built!).
  • Ability to read and interpret technical documentation and datasheets.
  • A genuine interest in robotics and automation—we want to see that spark!

8What to practise next

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

Advanced Control Theory & Optimisation

As robots become more complex and operate in dynamic environments, simple PID controllers won't cut it. We need more sophisticated control strategies to ensure precision, speed, and energy efficiency.

Model Predictive Control (MPC) · Optimal control techniques · Adaptive control systems · Reinforcement Learning for control policies · System identification and parameter tuning

  • This quarter: Take an online course on advanced control systems (e.g., from Coursera or edX).
  • Next quarter: Implement a basic MPC controller in a simulated environment.
  • Month 6: Read a few academic papers on how reinforcement learning is being used for robot control.
  • Month 9: Propose an optimisation for an existing robot's motion profile using a more advanced control technique.

Quick win: Start by deeply understanding the limitations of the current control systems we use. Ask your senior engineer for examples of where they fall short.

High-Fidelity Digital Twin Development

Digital twins are becoming essential for rapid prototyping, remote diagnostics, and even training. Moving beyond basic simulations to truly accurate virtual replicas is a game-changer for development cycles.

Physics-based simulation engines (e.g., Unreal Eng · Sensor modelling (simulating LiDAR, cameras, IMUs · Sim-to-real gap analysis and reduction techniques · Real-time data synchronisation between physical an · Creating realistic virtual environments

  • This quarter: Explore the advanced features of Gazebo or Isaac Sim, beyond basic component testing.
  • Next quarter: Try to create a more complex virtual environment that accurately reflects one of our real-world deployment sites.
  • Month 6: Experiment with integrating real robot sensor data into a digital twin for comparison.
  • Month 9: Propose a new use case for digital twins within our development process.

Quick win: Spend some time exploring the asset libraries and advanced rendering capabilities within our existing simulation tools. See what's possible.

9Staying current once you are in

What people here do to keep up
  • Participate in online robotics courses or MOOCs (e.g., from Coursera, edX) to deepen your knowledge.
  • Attend local robotics meetups or industry events (even virtual ones) to network and learn what's happening.
  • Contribute to open-source robotics projects (it's a great way to learn and build your portfolio).
  • Read industry publications and academic papers to stay on top of new developments.
  • Build your own small robotics projects at home—nothing beats hands-on 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 Robotics

Essential for future readiness in this role.

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

Your PlanIllustration

Built for Associate Robotics Engineer

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

  1. Producing Operating Programs for Industrial RobotsExcellence, Achievement & Learning Limited · covers 2 of 2 standardsLevel 3
  2. Preparing and using industrial robotsExcellence, Achievement & Learning Limited · covers 1 of 2 standardsLevel 2
  3. Producing operating programs for industrial robots:Excellence, Achievement & Learning Limited · covers 1 of 2 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 Robotics

Essential for future readiness in this role.

  • Context windows and token limits (how much info an
  • Temperature settings for creative vs. factual outp
  • RAG (Retrieval Augmented Generation) for using our
  • Output validation and hallucination detection (kno
  • Prompt chaining for multi-step tasks

Basic Cloud Robotics & Edge Compute

Essential for future readiness in this role.

  • IoT (Internet of Things) principles for device con
  • MQTT/AMQP protocols for messaging
  • Containerisation (Docker, Kubernetes) for deployin
  • Basic cloud services (AWS IoT Core, Azure IoT Hub)
  • Data logging and telemetry pipelines

What you’ll use

Skills this role draws on

Technical

  • Programming Fundamentals (Python, C++)
  • Basic Robotics Concepts
  • Mechatronics System Awareness
  • Version Control (Git)

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 (BSc/MSc)

    0-1 year post-graduation

    Skills to master

    • Applying theoretical knowledge to practical problems, basic project management, professional communication, debugging real-world systems.

    You're ready to move on when

    • Completed a significant final year project involving robotics.
    • Relevant internships or work placements during studies.
    • Strong academic record in core STEM subjects.
    • Can articulate how their academic learning applies to our specific challenges.
  2. 2

    Robotics Apprenticeship Programme

    Upon completion of a Level 3 or 4 apprenticeship

    Skills to master

    • Hands-on practical skills, adherence to industry standards, workplace safety, basic project execution, teamwork in an industrial setting.

    You're ready to move on when

    • Demonstrated proficiency in practical robotics tasks.
    • Strong understanding of safety protocols and best practices.
    • Positive feedback from apprenticeship mentors and supervisors.
    • Can show a portfolio of practical work completed during the apprenticeship.
  3. 3

    Career Changer (with relevant technical background)

    1-2 years of self-study or bootcamp experience

    Skills to master

    • Bridging previous technical skills (e.g., software development, mechanical design) to robotics, understanding robotics-specific frameworks (ROS), rapid learning of new domains.

    You're ready to move on when

    • Strong portfolio of self-taught robotics projects (e.g., personal robots, open-source contributions).
    • Demonstrated ability to learn complex technical subjects independently.
    • Previous experience in a related engineering or technical field.
    • Can clearly explain their motivation for moving into robotics.

11Where this role leads

The long view:Your journey starts here, but where it takes you is really up to you. We provide the tools, the mentorship, and the challenging projects. Your curiosity, drive, and willingness to learn will define how far and how fast you progress. We're excited to see what you'll build!

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 Robotics 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:

Producing Operating Programs for Industrial RobotsLevel 3

Applied to your work in Associate Robotics Engineer

The objective of this unit is to enable learners to produce operating programs for industrial robots. Learners will develop, simulate, test, and optimise robot programs using appropriate programming languages and tools, while also understanding robot types, programming principles, and safety considerations.

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

  • Task Completion RateHow many of your assigned tasks (like coding a specific robot behaviour or designing a small component) you finish within the agreed timeframe.If you're given five tasks this week, we'd expect you to get at least four of them done by Friday. We know things pop up, but consistent delivery is key.>80% of assigned tasks completed on time
  • Code Review Turnaround TimeThe speed at which you respond to feedback on your code from senior engineers and make the necessary changes.If a senior engineer reviews your code on Tuesday morning and flags a few things, we'd hope to see those changes pushed for re-review by Wednesday morning, or at least a clear plan of action.< 1 business day for minor feedback, < 2 days for major
  • Critical Bug Resolution TimeHow quickly you fix any critical bugs or issues that are directly traced back to your work once they're identified.If a robot stops moving because of a small error in your navigation code, we'd expect you to work with your senior engineer to get that fixed and tested within a day.< 24 hours for critical bugs (with guidance)
  • Documentation AdherenceHow well you follow our established documentation templates and guidelines for your code, designs, and test results.Every piece of code you write should have clear comments, and any design work should be logged in our system using the right format. It's boring, but it saves future-you a headache.Consistent adherence to 95% of documentation standards
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 Robotics Engineer to Robotics Engineer (Level 2), and whatever you decide comes after.

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

Your journey starts here, but where it takes you is really up to you. We provide the tools, the mentorship, and the challenging projects. Your curiosity, drive, and willingness to learn will define how far and how fast you progress. We're excited to see what you'll build!

See Your Progress GrowIllustration
Associate Robotics Engineer
  • Programming Fundamentals (Python, C++)
  • Basic Robotics Concepts
  • Mechatronics System Awareness
  • Version Control (Git)
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 Robotics Engineer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Robotics Engineer (Level 2)

    2-3 years in the Associate role

    You'll move from executing specific tasks to owning complete components or subsystems of a robot. You'll need less supervision and start making routine technical decisions independently.

    • Advanced ROS/ROS2 Development: Designing and implementing complex nodes and communication structures.
    • Full Subsystem Ownership: Taking responsibility for a complete part of the robot (e.g., the perception stack, a specific end-effector).
    • Data Analysis for Optimisation: Using fleet data to identify areas for improvement.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, some parts of robotics engineering can be a bit repetitive, especially when you're starting out. Imagine if you could offload some of that grunt work to an AI assistant. Well, you can. We're big believers in using AI to make our engineers more productive, not replace them.

As an Associate Robotics Engineer, AI tools can seriously speed up your learning curve and help you tackle tasks that might otherwise feel overwhelming. Think of it as having a super-smart, always-available assistant that handles the tedious bits, leaving you more time for the interesting, challenging work of actually building robots.

Code Generation & Debugging

Use AI tools like GitHub Copilot to suggest code snippets, complete functions, and even help you debug errors faster. It's like having a senior engineer looking over your shoulder, but without the awkward silence. This means less time staring at a blank screen and more time building.

Automated Test Scenario Generation

Instead of manually thinking up every possible test case for a robot's behaviour, AI can generate thousands of unique scenarios in simulation. This helps you find edge cases you might never have thought of, making your robot more robust before it even touches the real world. You'll be setting up the parameters, and the AI does the heavy lifting.

Documentation & Report Drafting

Need to summarise your test results or draft an explanation of a new module? AI can take your raw data and bullet points and turn them into a clear, concise first draft. You'll still need to review and refine it, but it saves you a ton of time staring at a blank page. Great for those less glamorous but essential tasks.

Intelligent Research Assistant

When you're researching new components or trying to understand a complex technical paper, AI can quickly summarise key points, extract relevant data, and even suggest related resources. This means you'll get up to speed on new topics much faster, which is invaluable in an entry-level role.

Common questions

Common questions

How do you become an Associate Robotics Engineer?

Common routes in include University Graduate (BSc/MSc) (0-1 year post-graduation), Robotics Apprenticeship Programme (Upon completion of a Level 3 or 4 apprenticeship) and Career Changer (with relevant technical background) (1-2 years of self-study or bootcamp experience). Times vary with prior experience.

Where can an Associate Robotics Engineer progress to?

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

What level is an Associate Robotics 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 Robotics Engineer?

Increasingly, Prompt Engineering for Robotics and Basic Cloud Robotics & Edge Compute. 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 Robotics 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 2 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 Robotics 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 various industries that use robotics, including logistics, manufacturing, healthcare, agriculture, and even space exploration. You won't be pigeonholed; the world will be your oyster, frankly.

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.