UK

United Kingdom · Technology and data · Lead (8-12 years)

Staff Full Stack Developer

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 Automation Fluency module

As a Staff Full Stack Developer, a good place to start on Prompt Engineering & LLM Integration for Architecture is Planning Automation Across a Department, a free Future Fluency module at Level 5. You'd practise working out what in your department's work could be automated, what should not be, and what to recommend.

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 bandLead (8-12 years)
  • Direct reports3-8 reports
  • Reports toDirector of Engineering
  • UK framework levelUsually a manager, or the deepest specialist in a team

Also advertised as Lead Full Stack Developer · Principal Software Engineer (Individual Contributor) · Senior Staff Engineer · Technical Lead Developer

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 2 Certificate In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 1 standard
EAL Level 2 Diploma In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 1 standard
EAL Level 2 Certificate in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 1 standard
EAL Level 2 First Certificate in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 1 standard
EAL Level 2 Diploma in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 1 standard
EAL Level 2 First Diploma in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 1 standard

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

The units you would start with

Leading a team in Engineering EAL Level 2 Certificate In Engineering Technologies

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Systems Fluency seeing the whole picture

2AI and this work

Will AI change your work as a Staff Full Stack Developer?

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

The new skill this role is being asked for

  • Prompt Engineering & LLM Integration for Architecture
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 Staff Full Stack Developer plan as you set up, starting with the free Automation 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 Staff Full Stack Developer designs solid systems, solves complex technical problems, and guides technical decisions across projects.

4What you'd actually use

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

React.js/Next.js Advanced

Designing and optimising complex component hierarchies, managing global state (Redux Toolkit, Zustand), and implementing performance enhancements (memoization, lazy loading) for critical user-facing applications. You'll also be evaluating and selecting appropriate frontend patterns for new projects.

Node.js (Express/NestJS) Advanced

Designing and building robust, scalable APIs for new microservices. Implementing advanced authentication/authorization mechanisms (JWT, OAuth), integrating with complex third-party services, and optimising backend performance for high-throughput applications.

PostgreSQL Advanced

Designing and optimising complex database schemas for new services, writing highly performant queries with intricate joins and aggregations, and implementing advanced indexing strategies. You'll also be involved in database migration planning and performance tuning.

AWS (Lambda, SQS, ECS, Terraform) Advanced

Implementing serverless functions, setting up and managing container orchestration (EKS/ECS), and configuring robust CI/CD pipelines using Infrastructure as Code (Terraform/CloudFormation). You'll be making decisions on AWS service selection for new architectures and optimising existing deployments.

Docker & Kubernetes (K8s) Advanced

Writing multi-stage Dockerfiles for production-grade applications, deploying and managing complex microservices on a Kubernetes cluster (or managed equivalent like EKS/GKE), and troubleshooting containerisation issues in production. You'll also be involved in defining containerisation standards.

Jest & Cypress Advanced

Designing and implementing comprehensive testing strategies across unit, integration, and end-to-end (E2E) tests. You'll be responsible for ensuring high test coverage, effective mocking of APIs and dependencies, and setting up automated testing in CI/CD pipelines.

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
Technical Approach for a New Feature Follows established patterns, escalates if unclear. Chooses from known patterns, proposes minor adaptations, consults senior on novel approaches. Designs and proposes the optimal technical approach, considering trade-offs, consults Staff/Lead on significant architectural implications.
Production Incident Response Executes runbook steps, escalates immediately if not resolved. Diagnoses common issues, applies standard fixes, escalates complex or novel problems. Leads incident response for complex issues, identifies root cause, implements hotfixes, and proposes long-term solutions.
Hiring for Engineering Roles Not involved in hiring decisions. Participates in technical interviews, provides feedback on candidate skills. Leads technical interview loops, assesses technical fit and cultural alignment, makes recommendations to hiring manager.
Budget Allocation (e.g., tooling, cloud spend) No budget authority. Proposes small tool purchases (under £1K) to manager. Recommends tooling or cloud resource optimisations up to £5K, requiring manager approval.

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.

System Reliability (Uptime/SLOs)
The percentage of time critical systems or services you've architected or significantly contributed to are operational and meeting their Service Level Objectives (SLOs).
Target · 99.95%+ uptime for owned services

Your designed microservice for user authentication maintains 99.98% uptime over Q3, exceeding its 99.95% SLO, meaning fewer than 2.5 hours of downtime across the quarter.

Technical Debt Reduction & Velocity Improvement
Leading initiatives that measurably reduce code complexity, eliminate legacy systems, or refactor critical components, resulting in improved team velocity or reduced bug rates.
Target · Improve team velocity by >10% or reduce critical bugs by >15% post-initiative.

After leading the refactoring of our payment processing module, the team's average cycle time for related features dropped from 5 days to 4 days, a 20% improvement, and critical bugs in that area halved.

Lead Time for Changes (Team-wide)
The average time it takes for a code commit to be deployed to production across the teams you influence or lead, reflecting efficiency in CI/CD and architectural simplicity.
Target · Reduce average lead time by 15% within 12 months.

By optimising the CI/CD pipeline and standardising deployment practices, the average lead time for your team's services decreases from 45 minutes to 38 minutes over two quarters.

Mentorship Impact & Junior Development
The demonstrable growth and increased responsibility of junior developers you mentor, evidenced by their ability to take on more complex tasks independently or formal promotions.
Target · At least one mentored junior developer takes on significantly more responsibility or is promoted within a year.

After 9 months of your mentorship, a junior developer you've been guiding successfully leads the implementation of a new feature end-to-end, a task they couldn't have handled previously, leading to their promotion to Mid-Level Developer.

Architectural Soundness & Adoption
The quality, scalability, and maintainability of the architectural designs you propose and implement, as evidenced by peer reviews and their successful adoption by other teams.
  • Your architectural proposals are consistently approved with minimal revisions
  • other teams actively seek to adopt your design patterns
  • systems you design prove resilient under load and are easy to extend
  • you receive positive feedback during peer architectural reviews.
Cross-Team Technical Influence
Your ability to influence technical decisions and best practices across different engineering teams, leading to more consistent and effective solutions company-wide.
  • You're regularly consulted by other teams for technical advice
  • your recommendations are frequently adopted in cross-team projects
  • you proactively identify and address technical silos
  • you lead technical working groups that drive company-wide standards.
Depth of Problem-Solving
Your effectiveness in diagnosing and resolving the most complex and ambiguous technical challenges, often those that stump others.
  • You're the go-to person for critical production incidents
  • you can debug issues across multiple system layers (frontend, backend, database, infrastructure)
  • you propose novel and effective solutions to long-standing technical problems
  • your post-mortems are thorough and lead to lasting fixes.
Strategic Technical Communication
Your ability to clearly articulate complex technical concepts, trade-offs, and risks to both technical and non-technical audiences, influencing strategic decisions.
  • Your technical design documents are clear, concise, and well-understood
  • you can effectively present architectural proposals to senior leadership
  • you translate technical constraints into business implications that Product Managers can act on
  • you lead productive technical discussions that move projects forward.

7Would you like it

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

What people enjoy
Solving Deep Technical Challenges

You'll find immense satisfaction in debugging a tricky distributed system issue that's been baffling the team for days, or in designing a new microservice architecture that dramatically improves performance. You love the intellectual puzzle of engineering.

Spending an entire afternoon tracing a memory leak across three different services, finally pinpointing the obscure library causing it, and then implementing a fix that prevents future outages.

Building Impactful Systems

You're driven by the desire to build robust, scalable, and maintainable systems that genuinely move the business forward. You want to see your architectural decisions translate into tangible improvements for our users and our developers.

Leading the design and implementation of a new API gateway that standardises authentication and authorisation across all our client applications, simplifying development for multiple teams.

Mentoring & Elevating Others

You get a real buzz from helping junior developers grow, whether it's through detailed code reviews, pair programming on a tough problem, or guiding them through their career development. You want to leave a legacy of strong engineering talent.

A junior developer you've been mentoring for six months successfully delivers a complex feature independently, attributing their success to your guidance and support.

What frustrates people
  • Vague Architectural Requirements: Getting a high-level business goal and being told to 'figure out the system design' with limited initial detail.
  • Architectural Compromises: Having to make trade-offs on an ideal technical solution due to budget, time, or legacy system constraints.
  • The Legacy Code Minefield: Being asked to integrate a new, elegant system with a decades-old, poorly documented codebase.
  • Too Many Meetings, Not Enough Deep Work: Spending significant time in cross-functional technical alignment meetings when you'd rather be deep in system design.
  • Lack of Strategic Impact: Feeling like your architectural contributions aren't being fully adopted or are being undermined by short-sighted decisions.
  • 'Urgent' Requests That Aren't: Dealing with last-minute, supposedly critical issues that derail your planned architectural work, only to find they weren't that urgent after all.
What this role does not give you
  • A purely individual contributor path without any mentorship or team leadership expectations.
  • A predictable, unchanging technical environment; we're always evolving.
  • The luxury of always building greenfield projects from scratch; you'll deal with existing systems.
  • A role where you can avoid presenting your ideas and designs to diverse audiences.

8Who you work with

Your work directly shapes the technical direction and architectural integrity of critical systems, influencing the efficiency and capabilities of multiple engineering teams. You'll solve problems that have a ripple effect across the organisation, improving everything from system uptime to developer velocity and, ultimately, customer satisfaction.

Inside the business
  • VP of Engineering
  • Peer Staff/Lead Developers
  • Product Managers (especially senior ones)
  • Other Engineering Teams (Frontend, Backend, DevOps)
  • Security Team
  • QA/Testing Leads
Outside the business
  • Strategic Technology Partners (e.g., cloud providers)
  • Key Vendors (for specific tooling or services)

9What you need before you start

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

  • Proven track record as a Senior Full Stack Developer or equivalent for at least 3-5 years, demonstrating strong independent delivery and technical leadership.
  • Deep understanding of computer science fundamentals: data structures, algorithms, operating systems, and networking.
  • Experience leading the design and implementation of significant features or small projects from conception to production.
  • Demonstrable ability to mentor junior engineers and provide impactful code reviews.
  • Strong understanding of cloud infrastructure (preferably AWS) and CI/CD pipelines.
  • Proficiency in at least one modern frontend framework (e.g., React, Vue) and one backend language/framework (e.g., Node.js, Python/Django, Go).

10What to practise next

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

Advanced Cloud-Native Optimisation & FinOps

As our cloud spend increases, optimising resource usage and cost efficiency becomes paramount. This isn't just about technical performance, but also about financial responsibility. You'll need to design systems that are not only performant but also cost-effective.

Serverless Cost Optimisation · Spot Instances & Savings Plans · Multi-Region/Multi-Cloud Architectures · Cost Monitoring & Alerting

  • This quarter: Take an AWS/Azure FinOps certification or a relevant online course.
  • Next quarter: Lead a review of one of our high-cost services and propose 2-3 cost-saving architectural changes.
  • Month 6: Implement a cost-tracking dashboard for your owned services.
  • Month 9: Present a 'FinOps Best Practices' session to the wider engineering team.

Quick win: Review your team's current cloud resource utilisation. Are there any idle resources? Can you switch to a cheaper instance type for development environments? Small changes add up.

Platform Engineering & Developer Experience (DX)

To scale our engineering organisation, we need to provide robust, self-service platforms that enable other developers to build and deploy quickly and safely. Your role will increasingly involve contributing to these internal platforms.

Internal Developer Platforms (IDP) · Service Mesh Technologies (e.g., Istio, Linkerd) · Golden Paths & Templates · Observability as a Service

  • This quarter: Read up on 'Team Topologies' and 'Platform Engineering' concepts.
  • Next quarter: Identify one area where our internal developer experience could be significantly improved and propose a solution.
  • Month 6: Contribute to an existing internal tool or build a small proof-of-concept for a new platform component.
  • Month 9: Advocate for and help implement a new 'golden path' for a common development task.

Quick win: Propose a new code template or a CI/CD pipeline snippet that simplifies a common task for your team. Small improvements to DX can have a big impact.

11Staying current once you are in

What people here do to keep up
  • Regularly contribute to open-source projects or maintain a strong technical blog to share your expertise and learn from the community.
  • Attend and speak at industry conferences, local meetups, or internal tech talks to stay current and build your professional network.
  • Actively participate in online technical communities (e.g., Stack Overflow, Reddit's r/ExperiencedDevs) to both learn and contribute.
  • Dedicate time each quarter to learning a new technology or diving deeper into an existing one that's relevant to our future roadmap.
  • Seek out mentorship from more senior engineers or technical leaders, and actively mentor junior colleagues yourself.

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.

Prompt Engineering & LLM Integration for Architecture

Large Language Models (LLMs) are rapidly transforming how we approach software design and development. Competitors are already using AI to generate architectural patterns, evaluate design trade-offs, and even scaffold complex microservices in minutes. Engineers who master this will significantly outproduce and out-innovate those who don't.

  • Context Windows & Token Limits
  • RAG (Retrieval Augmented Generation) Architectures
  • Output Validation & Hallucination Detection
  • Prompt Chaining for System Design

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Agile/Scrum Methodologies
  • Test-Driven Development (TDD)
  • API Design (REST & GraphQL)
  • CI/CD (Continuous Integration/Continuous Deployment)
  • System Design & Architecture
  • DevSecOps Principles

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

    Senior Full Stack Developer (Internal Promotion)

    3-5 years as a Senior Developer

    Skills to master

    • Leading complex features, mentoring junior developers, driving technical initiatives, strong understanding of system-level trade-offs, consistent high-quality delivery.

    You're ready to move on when

    • Consistently taking ownership of large, ambiguous technical problems and delivering robust solutions.
    • Proactively identifying and addressing technical debt or architectural weaknesses.
    • Receiving consistent feedback for strong mentorship and elevating team members.
    • Demonstrating influence on technical decisions beyond your immediate project scope.
  2. 2

    Senior Backend or Frontend Engineer (Specialist to Full Stack)

    4-6 years as a Senior Specialist

    Skills to master

    • Broadening expertise across the full stack (e.g., a backend specialist picking up advanced React/Next.js, or a frontend specialist diving deep into Node.js/cloud infrastructure), understanding how both sides interact at an architectural level.

    You're ready to move on when

    • Successfully leading projects that require significant contributions across both frontend and backend.
    • Demonstrating a strong understanding of the full system architecture, not just their specialisation.
    • Actively contributing to discussions and decisions on both frontend and backend technical roadmaps.
    • Building a portfolio of projects that showcase full-stack capabilities.
  3. 3

    Technical Lead (from another company)

    8-12 years total experience, with 3-5 years in a lead role

    Skills to master

    • Adapting to our specific tech stack and architectural patterns, understanding our business domain, quickly building trust and influence within our engineering teams.

    You're ready to move on when

    • Successfully onboarding and making significant technical contributions within the first 3-6 months.
    • Proactively identifying areas for improvement in our systems and proposing well-reasoned solutions.
    • Effectively mentoring our junior developers and integrating into our team culture.
    • Demonstrating a clear understanding of our product and business goals.

15Where this role leads

The long view: This role can lead into engineering leadership, such as Director of Engineering, or into deep technical specialism as a Distinguished Engineer.

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 Staff Full Stack Developer 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:

  • Principal Engineer (Individual Contributor Track)
  • Engineering Manager (Management Track)

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 Leading a team in Engineering, worked against Staff Full Stack Developer.

Leading a team in Engineering Level 2

Applied to your work in Staff Full Stack Developer

The objective of this unit is to equip learners with an understanding of the roles, responsibilities, knowledge, and skills required to effectively lead a team in an engineering environment. Learners will explore how to manage team workloads, allocate tasks, and contribute to achieving team goals through effective leadership practices.

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
Staff Full Stack Developer
  • Agile/Scrum Methodologies
  • Test-Driven Development (TDD)
  • API Design (REST & GraphQL)
  • CI/CD (Continuous Integration/Continuous Deployment)
  • System Design & Architecture
  • DevSecOps Principles
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.

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

Staff Full Stack Developer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Principal Engineer (Individual Contributor Track)

    3-5 years as a Staff Full Stack Developer

    From OFQUAL 7 to OFQUAL 7-8

    • Enterprise Architecture Design Designing systems that span multiple business domains and integrate complex legacy systems.
    • Technology Roadmap Definition Collaborating with executive leadership to define the company's multi-year technology roadmap.
    • Advanced Performance Engineering Optimising systems at an enterprise scale for extreme performance and cost efficiency.
    • Strategic Vendor Evaluation Assessing and selecting key technology partners and platforms at a company-wide level.

  2. Engineering Manager (Management Track)

    2-4 years as a Staff Full Stack Developer

    From OFQUAL 7 to OFQUAL 7-8

    • Budget Management Managing team budgets, including tooling, training, and headcount.
    • Process Optimisation Continuously improving team workflows, agile practices, and delivery processes.
    • Strategic Planning Translating business objectives into actionable engineering roadmaps and OKRs.
    • Stakeholder Management Building strong relationships with Product, Design, and other business units to ensure alignment.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, as a Staff Full Stack Developer, your time is precious. You're not just coding; you're architecting, mentoring, and solving the really hard problems. Imagine if you could offload the repetitive, time-consuming tasks and focus on the high-impact work. Well, you can. AI isn't just a buzzword here; it's a practical tool that'll make you a more effective and strategic engineer.

We're building an AI Productivity Hub specifically for our Technical_roles team. It's packed with ready-to-use tools and best practices that integrate seamlessly into your daily workflow. This isn't about replacing your job; it's about augmenting your abilities, freeing you up to tackle the truly challenging and rewarding aspects of being a Staff Developer. Think of it as having an incredibly smart, tireless assistant for all the grunt work.

Boilerplate & Test Generation

Use AI tools like GitHub Copilot or our internal code generation models to instantly scaffold new services, generate complex API endpoint handlers, data models, or comprehensive unit and integration test skeletons. This frees you up from the tedious, repetitive coding, allowing you to focus on the unique logic and architectural considerations.

Smart Debugging & Error Analysis

When you're faced with a cryptic error message from a distributed system or a complex performance issue, paste the logs or code snippets into an AI assistant (like ChatGPT-4 or Claude). Get plain-English explanations, potential root causes, and even suggested fixes, drastically cutting down on debugging time for even the most obscure problems.

Accelerated Architectural Research

Exploring new architectural patterns (e.g., event-driven vs. request-response), evaluating different cloud services, or diving into an unfamiliar framework? Ask an AI to provide concise summaries, compare trade-offs, generate reference architectures, and even suggest optimal design patterns for specific use cases. It's like having an expert consultant on demand.

Automated Documentation & Communication

Generate high-quality documentation (e.g., OpenAPI specs, architectural decision records, detailed READMEs) for your new systems or complex codebases with minimal effort. Use AI to draft clear, concise summaries for your architectural proposals, pull requests, and release notes, ensuring effective communication across technical and non-technical audiences.

Common questions

Common questions

How do you become a Staff Full Stack Developer?

Common routes in include Senior Full Stack Developer (Internal Promotion) (3-5 years as a Senior Developer), Senior Backend or Frontend Engineer (Specialist to Full Stack) (4-6 years as a Senior Specialist) and Technical Lead (from another company) (8-12 years total experience, with 3-5 years in a lead role). Times vary with prior experience.

Where can a Staff Full Stack Developer progress to?

This role can lead on to Principal Engineer (Individual Contributor Track) (3-5 years as a Staff Full Stack Developer) and Engineering Manager (Management Track) (2-4 years as a Staff Full Stack Developer), depending on the skills you build.

What new skills matter most for a Staff Full Stack Developer?

Increasingly, Prompt Engineering & LLM Integration for Architecture. 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

17Where to go from here

Other roles at Level 5

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 built in this role transfer across industries. Experience with distributed systems, cloud architecture, and leading technical initiatives applies in FinTech, HealthTech, E-commerce, SaaS, and other sectors. These skills suit significant technical challenges in most modern tech-driven companies.

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