UK

United Kingdom · Technology and data · Mid-Level (2-5 years)

Telecom Engineer

Here is the whole job, in plain words. What it is, 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.

See how AI is changing this job, and get the full read by email.

Start my free AI Fluency module

The first step towards SD-WAN & SASE Architectures is getting confident with the AI tools already in your week, so start with Using and Checking AI Tools in Daily Work, free.

Free to start, no card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, the new skills it asks for, where it leads, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Your employer, or 'self-employed'

Leading a team? Try this with up to five of them for 14 days, free.

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Telecom Engineer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Network Engineer (Telecoms) · Voice Engineer · Unified Communications Engineer · Mid-Level Telecommunications Specialist

Built on 43,079 real UK job descriptions we analysed · grounded in what real qualifications cover

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

EAL Level 3 Diploma in Rail Engineering Technician Competence Excellence, Achievement & Learning Limited · Level 3 · covers 8 of 10 standards
Pearson BTEC Level 3 Diploma in ICT Systems and Principles Pearson Education Ltd · Level 3 · covers 2 of 10 standards
ETCAL Level 2 Diploma in Rail Engineering (Competence) ETC Awards Limited · Level 2 · covers 6 of 10 standards
EAL Level 2 Diploma in Rail Engineering Operative Competence Excellence, Achievement & Learning Limited · Level 2 · covers 6 of 10 standards
Pearson BTEC Level 3 Certificate in ICT Systems and Principles Pearson Education Ltd · Level 3 · covers 1 of 10 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Contribute to technical leadership of signal engineering activities EAL Level 3 Diploma in Rail Engineering Technician Competence
Telecommunications Technology Pearson BTEC Level 3 Diploma in ICT Systems and Principles
Assist in the Tests and Checks of Telecoms Equipment ETCAL Level 2 Diploma in Rail Engineering (Competence)
Installation of telecoms equipment using non complex processes EAL Level 2 Diploma in Rail Engineering Operative Competence
Fault Diagnosis and Maintenance of Communications Equipment Pearson BTEC Level 3 Certificate in ICT Systems and Principles

The future skills this job leans on

Automation Fluency building AI into how work runs
Change Fluency taking people through change
Trust Fluency keeping the digital world safe
Your Plan Illustration

Built for Telecom Engineer

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

  1. Contribute to technical leadership of signal engineering activities Excellence, Achievement & Learning Limited · covers 8 of 10 standards Level 3
  2. Telecommunications Technology Pearson Education Ltd · covers 2 of 10 standards Level 3
  3. Assist in the Tests and Checks of Telecoms Equipment ETC Awards Limited · covers 6 of 10 standards Level 2
  4. Installation of telecoms equipment using non complex processes Excellence, Achievement & Learning Limited · covers 6 of 10 standards Level 2
  5. Fault Diagnosis and Maintenance of Communications Equipment Pearson Education Ltd · covers 1 of 10 standards Level 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.

2AI and this work

Will AI change your work as a Telecom Engineer?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • SD-WAN & SASE Architectures
  • Network Automation & Scripting (Basic)
Why each one is rising

The future skills this job leans on

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

What happens when you start

Next, a free account. We build your Telecom Engineer plan as you set up, starting with the free AI Fluency module. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Ready to pay? Subscribe for £70 a month

Keep this read. One email with what AI is changing in this job, the new skills it asks for and where to start free. Nothing else follows unless you confirm your address.

3What this role really is

A Telecom Engineer keeps communication systems running, from phone lines to video conferencing and network links between offices.

4What you'd actually use

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

SolarWinds NPM or PRTG Network Monitor Intermediate

Monitoring network device health, checking interface statistics, responding to basic alerts, and pulling standard performance reports.

Cisco Unified Communications Manager (UCM) Intermediate

Provisioning new users, making phone number changes, adjusting call routing for specific extensions, and troubleshooting basic voice issues.

Microsoft Teams Admin Centre Intermediate

Managing Teams users, configuring voice policies, setting up direct routing, and troubleshooting Teams calling issues.

Cisco IOS/NX-OS (Basic Configuration) Intermediate

Performing basic configuration checks on switches and routers, verifying interface status, and troubleshooting connectivity issues via CLI.

AWS VPC / Azure VNet (Basic Concepts) Basic

Understanding basic cloud networking concepts, checking security group rules, and verifying network ACLs in cloud environments.

Tangoe or Calero-MDSL (TEM Platform) Intermediate

Processing telecom invoices, auditing against inventory, identifying basic billing errors, and generating standard cost reports.

ServiceNow ITSM Intermediate

Managing incident tickets, documenting troubleshooting steps, creating knowledge base articles, and submitting change requests for network modifications.

5What 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 in Where you are nowThe step above
Troubleshooting & Incident Resolution Escalate all but the most basic, documented issues to a senior engineer. Follow step-by-step guides. Independently diagnose and resolve Tier 2 incidents within defined SLAs. Consult senior engineers for complex, novel, or widespread issues. Decide on the best troubleshooting approach. Lead resolution of critical incidents, often coordinating multiple teams. Make decisions on temporary workarounds or failover strategies. Define incident response procedures.
Configuration Changes (Routine) Perform changes only under direct supervision, following explicit instructions and templates. Execute routine configuration changes (e.g., user MACDs, minor QoS adjustments) independently, following change management processes. Seek approval for changes impacting more than a small group of users. Approve and implement complex configuration changes for major systems. Design and review change plans for junior engineers. Decide on optimal configuration standards.
Tool Selection & Methodology Use tools and methodologies as directed by senior staff. Propose alternative troubleshooting tools or minor process improvements for review. Select appropriate methods for solving routine technical problems. Recommend and evaluate new tools or methodologies for the team. Make technical decisions on the best approach for project implementation within your workstream.
Budget & Procurement No authority. Flag needs to supervisor. Identify equipment or software needs for specific tasks and present a justification to a senior engineer. No direct purchasing authority. Recommend procurement of equipment or services up to £5K. Provide technical input for larger budget requests. Influence vendor selection for projects.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Ticket Resolution Time (Telecoms)
How quickly you close out support tickets related to telecom issues, from a dodgy phone line to a conference call not connecting.
Target · Resolve 90% of Tier 2 telecom tickets within the 8-hour SLA.

If 10 out of 11 tickets are resolved within 8 hours, that's a 90.9% resolution rate. We're looking for consistent performance here.

MACD Accuracy
The precision of your Moves, Adds, Changes, and Deletes (MACDs) for user provisioning on our phone systems and collaboration platforms. Basically, did you set up that new user's phone correctly the first time?
Target · Achieve >98% accuracy on all telecom-related MACDs.

Out of 50 new user setups or phone changes, only one had to be revisited due to an error. That's 98% accuracy – pretty good, but we always aim higher.

System Uptime for Assigned Nodes
The availability of the specific network and unified communications components you're responsible for. We're talking about the uptime of a regional office's LAN switch or a specific voice gateway.
Target · Maintain 99.9% uptime for all assigned network and UC nodes.

If a specific voice gateway has 43 minutes of downtime in a month, that's roughly 99.9% uptime. We're looking for you to keep those numbers high and investigate any dips.

Configuration Error Rate
The number of times a change you've made to a device or system causes an unintended outage or service degradation.
Target · Fewer than 1 critical configuration error per quarter.

You updated the firmware on a router, and it caused a 15-minute outage for a small office. That counts. We expect you to learn from these, but minimise them.

Proactive Problem Solving
You're not just waiting for tickets to come in; you're spotting potential issues before they become full-blown problems. This means digging into alerts and logs, and fixing things quietly in the background.
  • You'll be flagging potential issues in daily stand-ups, suggesting preventative maintenance, or implementing minor fixes that stop recurring problems. Your manager will notice you’re not just reactive, you’re thinking ahead.
Quality of Documentation
The clarity and completeness of the technical documentation you create or update, whether it's network diagrams, troubleshooting guides, or configuration notes. Honestly, good documentation saves everyone a lot of grief.
  • Other team members can easily follow your guides to resolve issues. New joiners can get up to speed faster because your notes are clear. Your documentation is regularly updated and accurate, not just a 'tick-box' exercise.
Collaboration & Knowledge Sharing
How well you work with the wider IT team, sharing what you've learned, helping others, and asking for help when you need it. No one's an island here.
  • You're actively contributing to team knowledge base articles, helping the Service Desk understand common issues, and offering a hand to other engineers when they're stuck. People come to you for advice on specific telecom systems.
Adherence to Best Practices
You're following our established procedures for change management, incident response, and security, even when it feels like a bit of a faff. It's about keeping things stable and secure.
  • Your change requests are properly documented and approved. You follow the incident management process during outages. Security configurations are always applied according to policy. Your manager isn't chasing you for process steps.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Complex Technical Puzzles

You get a real kick out of figuring out why a specific routing protocol isn't behaving or why voice packets are dropping. The more obscure the problem, the more satisfying the fix. You're happiest when you've got a tricky network issue to unpick.

Spending an afternoon troubleshooting a mysterious VPN tunnel issue, finally pinpointing a misconfigured ACL, and getting it working perfectly again. That's your kind of day.

Seeing Your Work Directly Impact Users

You like knowing that because you fixed that phone system glitch, a whole department can now communicate properly. You appreciate the tangible outcome of your efforts and the positive feedback from colleagues.

Getting a 'thank you' email from a user whose video conferencing issues you resolved, making their important client meeting possible. That's a direct win.

Continuous Learning and Skill Development

You're always looking for new certifications to pursue, new technologies to explore, or deeper dives into existing systems. You enjoy expanding your technical toolkit and becoming more proficient.

Volunteering to take on a new project involving a technology you've only read about, or spending time outside of work hours to prepare for a new networking certification.

What frustrates people
  • Spending hours on the phone with carrier support, only to be bounced between departments or have them blame your internal network.
  • Dealing with legacy systems that are barely held together with sticky tape and prayers, making any change a high-risk operation.
  • Being asked to 'just quickly fix' something that you know will take days of careful planning and implementation.
  • Users complaining about 'slow internet' when the issue is actually their old laptop or a dodgy Wi-Fi signal, not the core network.
  • The constant pressure to reduce costs while simultaneously being asked for more bandwidth and new services.
  • Working on a critical fix late at night, only for a last-minute change request to come in and mess up your careful plan.
What this role does not give you
  • A quiet, predictable 9-to-5 where nothing ever breaks.
  • A role where you're always building shiny new things from scratch, rather than maintaining and improving existing infrastructure.
  • Complete freedom from administrative tasks or documentation.
  • A job where you never have to deal with demanding users or external vendors.

8Who you work with

Your work directly impacts our operational efficiency and our ability to communicate internally and externally. Get it right, and our sales team can close deals, our support team can help customers, and everyone stays connected. Get it wrong, and it's a real headache for everyone, costing us time and potentially money. You're essentially the quiet hero behind every successful phone call and video meeting.

Inside the business
  • Senior Telecom Engineer (your direct boss)
  • IT Service Desk (they'll pass you tickets)
  • Network Operations Team (you'll work closely with them on infrastructure)
  • Information Security (making sure everything's secure)
  • Office Managers (for new office setups or moves)
  • End-users (when they can't make a call, you're their hero)
Outside the business
  • Telecom Carrier Support (when things go wrong with the lines)
  • Equipment Vendors (for hardware or software issues with our kit)
  • Managed Service Providers (if we outsource parts of our network)

9What you need before you start

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

  • At least 2 years of hands-on experience in a network support, telecom technician, or junior network engineer role.
  • Demonstrable experience troubleshooting network connectivity and voice quality issues.
  • Familiarity with command-line interfaces (CLI) for network devices (e.g., Cisco IOS).
  • A solid grasp of TCP/IP fundamentals and basic routing concepts.
  • Experience working with an IT Service Management (ITSM) platform, like ServiceNow, for ticket management.
  • A genuine interest in telecommunications technology and a drive to keep learning.

10What to practise next

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

Advanced Cloud Networking (AWS/Azure)

More and more of our infrastructure and applications are moving to the cloud. You'll need to understand how to design, implement, and troubleshoot robust and secure network connectivity within and between cloud providers.

Hub-and-spoke architectures in cloud · VPN gateways and Direct Connect/ExpressRoute · Cloud-native security groups and network ACLs · Inter-VPC/VNet peering and transit gateways · Cost optimisation for cloud networking

  • This month: Complete an online course on AWS VPC or Azure VNet fundamentals.
  • Month 2: Set up a basic hub-and-spoke network in a lab environment within one cloud provider.
  • Month 3: Experiment with site-to-site VPNs between your on-prem lab and a cloud VPC/VNet.
  • Month 4: Understand how to monitor cloud network performance and troubleshoot connectivity issues.

Quick win: Get familiar with the networking sections of our existing AWS or Azure environments. Ask your senior about our cloud connectivity strategy.

Deep Dive Voice Troubleshooting & QoS

Voice is still critical, and as more people work from varied locations, voice quality issues become more complex. You'll need to master the art of diagnosing and resolving even the trickiest jitter and packet loss problems.

Packet analysis (Wireshark for VoIP) · Advanced QoS configuration and tuning · SIP trunking and Session Border Controllers (SBCs) · Voice codec optimisation · Network latency and its impact on voice

  • This month: Get proficient with Wireshark for analysing VoIP traffic.
  • Month 2: Study advanced QoS concepts and how they apply to our specific network devices.
  • Month 3: Understand the role of SBCs in our voice architecture and their basic configuration.
  • Month 4: Take ownership of resolving all voice quality tickets, seeking expert advice only when truly stuck.

Quick win: Set up Wireshark on your machine and capture some internal VoIP calls. See if you can identify any basic issues.

11Staying current once you are in

What people here do to keep up
  • Attending industry webinars and virtual conferences on emerging telecom technologies (e.g., SD-WAN, 5G enterprise use cases).
  • Participating in online technical forums and communities to learn from peers and share your own knowledge.
  • Undertaking vendor-specific training courses for our core platforms (e.g., advanced Cisco UCM courses, cloud networking specialisations).
  • Building a home lab environment to experiment with new configurations or test out troubleshooting scenarios without impacting production systems.
  • Reading technical blogs and whitepapers from leading telecom and network vendors.

12The rising capability

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.

SD-WAN & SASE Architectures

Traditional WANs are becoming obsolete. Businesses need more agile, secure, and cost-effective ways to connect offices and cloud resources. SD-WAN and SASE are the future, offering better performance and security for distributed workforces.

  • Software-Defined Networking principles
  • Zero Trust Network Access (ZTNA)
  • Cloud-native security services (CASB, SWG, FWaaS)
  • Application-aware routing
  • Orchestration and automation platforms

Network Automation & Scripting (Basic)

Manual configuration is slow, error-prone, and doesn't scale. Automating repetitive tasks using scripts saves time, reduces mistakes, and allows engineers to focus on more strategic work. It's becoming a fundamental skill.

  • Python basics for network automation
  • REST APIs for network devices
  • Configuration management tools (e.g., Ansible, bas
  • Version control (e.g., Git basics)
  • Idempotence in network changes

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Network Architecture & Design (Foundational)
  • Unified Communications (UC) Management
  • Carrier Relationship & Contract Understanding
  • Telecom Expense Management (TEM) Operations
  • Regulatory & Compliance Awareness (Basic)
  • ITIL Framework Application (Operational)

14The pathway

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

    Associate Telecom Analyst (L1)

    1-2 years

    Skills to master

    • Basic troubleshooting, user MACDs, network monitoring, adherence to documentation, foundational TCP/IP knowledge.

    You're ready to move on when

    • Consistently resolves Tier 1 tickets within SLA.
    • Can independently perform routine user provisioning and device monitoring.
    • Demonstrates a solid understanding of basic network commands and concepts.
    • Proactively seeks to learn more complex systems and asks insightful questions.
  2. 2

    IT Support Engineer (with Telecom Focus)

    2-3 years

    Skills to master

    • Broader IT troubleshooting (desktops, applications), basic network diagnostics, strong customer service skills, understanding of IT infrastructure.

    You're ready to move on when

    • Successfully troubleshoots and resolves a wide range of IT issues, including basic telecom problems.
    • Shows a keen interest in specialising in network and voice technologies.
    • Can clearly communicate technical issues to both users and senior engineers.
    • Has taken initiative to learn more about telecom systems in their current role.
  3. 3

    Apprenticeship in Network/Telecoms

    3-4 years (post-apprenticeship)

    Skills to master

    • Practical application of networking theory, hands-on experience with equipment, professional workplace behaviour, project-based learning.

    You're ready to move on when

    • Successfully completed all apprenticeship modules and gained relevant certifications.
    • Demonstrates practical experience with various network and telecom technologies.
    • Can work independently on assigned tasks and solve problems systematically.
    • Has a strong portfolio of project work and practical implementations.

15Where this role leads

The long view: This work can lead to network engineering, cloud infrastructure or IT security roles, or into specialist telecom architecture and leadership positions.

16Pay and demand

ONS's coding index maps “Telecom Engineer” to more than one occupation, so there is no one median to quote. Rather than pick, here is each one it could be, with its own figure:

  • Electronics engineers £52,518 a year
  • Telecoms and related network installers and repairers £39,998 a year

ONS Annual Survey of Hours and Earnings, from the April 2025 survey, about six months old when published, as ASHE always is, under the Open Government Licence.

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 Telecom Engineer is actually changing.

Where it leads

Roles this leads to

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

  • Senior Telecom Engineer (L3)

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Contribute to technical leadership of signal engineering activities, worked against Telecom Engineer.

Contribute to technical leadership of signal engineering activities Level 3

Applied to your work in Telecom Engineer

The objective of this unit is to enable learners to contribute to the technical leadership of signal engineering activities while adhering to safety procedures. Learners will assess the suitability and technical feasibility of work methods and procedures for various types of signalling equipment, anticipating potential problems and choosing appropriate solutions.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 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.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

See Your Progress Grow Illustration
Telecom Engineer
  • Network Architecture & Design (Foundational)
  • Unified Communications (UC) Management
  • Carrier Relationship & Contract Understanding
  • Telecom Expense Management (TEM) Operations
  • Regulatory & Compliance Awareness (Basic)
  • ITIL Framework Application (Operational)
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.

17The 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

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

  1. Senior Telecom Engineer (L3)

    3-5 years in current role

    You'll move from owning specific systems to leading entire workstreams and projects. You'll become a technical expert and a mentor.

    • Designing and implementing complex call flows and network segments.
    • Advanced troubleshooting of inter-system integrations (e.g., Teams Direct Routing with SBCs).
    • Leading office build-outs and major equipment upgrades.
    • Making technical decisions within project scope and influencing architectural choices.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, some parts of telecom engineering can be a bit of a slog. But what if you could cut down on the repetitive stuff and focus on the really interesting technical challenges? That's where AI comes in. We're investing in tools that help you work smarter, not just harder.

In this role, you'll be encouraged to use AI tools to streamline your daily tasks, from spotting network anomalies to drafting incident reports. It's not about replacing your expertise; it's about giving you superpowers to be more efficient and proactive. Think of it as having a really smart assistant who handles the grunt work.

Proactive Outage Prevention

Imagine using AIOps features within our network monitoring platforms (like Datadog or ServiceNow) to analyse network telemetry. This helps you predict anomalies and automatically pinpoint the root causes of performance degradation before they turn into full-blown outages. Less firefighting, more proactive fixing.

Automated Invoice Auditing

Say goodbye to manually sifting through mountains of carrier invoices. You'll use AI-powered TEM tools to scan and analyse complex bills, automatically flagging billing errors, unused circuits, and optimisation opportunities that are almost impossible for a human to spot at scale. This saves you a load of time and helps us save money.

Vendor & Regulation Research

Need to quickly understand the key features of a new UCaaS provider or summarise the impact of a recent FCC ruling on our network? You can use AI assistants to rapidly distil complex vendor documentation or regulatory texts, getting you the key info you need in minutes, not hours.

Incident & Comms Drafting

After a tricky incident, you can use AI to generate the first draft of a technical Root Cause Analysis (RCA) document or to translate complex network performance data into a clear, concise internal update for non-technical teams. It's about getting your message across faster and more accurately.

Common questions

Common questions

How do you become a Telecom Engineer?

Common routes in include Associate Telecom Analyst (1-2 years), IT Support Engineer (with Telecom Focus) (2-3 years) and Apprenticeship in Network/Telecoms (3-4 years (post-apprenticeship)). Times vary with prior experience.

Where can a Telecom Engineer progress to?

This role can lead on to Senior Telecom Engineer (3-5 years in current role), depending on the skills you build.

What new skills matter most for a Telecom Engineer?

Increasingly, SD-WAN & SASE Architectures and Network Automation & Scripting (Basic). These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

18Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills involved apply across most industries. They can lead to broader network engineering, cloud infrastructure or IT security work, in sectors from finance to healthcare to media.

This role profile is © 2026 Growth 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. Start my free AI Fluency module What happens next: a free account, then we build your plan as you set up. 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.