UK

United Kingdom · Technical roles · Mid-Level (2-5 years)

Software 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 bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Software Engineer or Staff Software Engineer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Mid-Level Developer · Backend Engineer · Software Developer

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 Software 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

You'll be building and shipping features, fixing gnarly bugs, and generally making sure our core services run smoothly. This isn't about just executing tasks; it's about taking ownership of chunks of work, seeing them through from design to deployment, and learning a ton along the way. Think of yourself as a key contributor, someone who can tackle a problem and deliver a solid solution without needing constant hand-holding.

2What you'd actually use

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

Go (Programming Language)Intermediate

You'll be writing and debugging complex, concurrent services and API endpoints in Go. You're comfortable with its concurrency primitives (goroutines, channels) and standard library. You'll also be optimising existing Go code for performance.

Python (Programming Language)Intermediate

Used for scripting, data processing, and sometimes for specific microservices where its ecosystem shines. You'll write clean, idiomatic Python code and use common libraries like `requests` or `pandas` (if data-related).

AWS (Cloud Provider)Intermediate

You'll be deploying and managing services on AWS. This means working with services like EC2, S3, Lambda, DynamoDB, SQS, and understanding basic networking concepts (VPCs, security groups). You can troubleshoot issues in the AWS console.

Docker & Kubernetes (Containerization)Intermediate

You'll write Dockerfiles for your applications and use `docker-compose` for local development. You'll also be deploying and debugging your services within our Kubernetes clusters, writing and understanding basic Kubernetes manifests (Deployments, Services, Ingress).

GitLab CI / GitHub Actions (CI/CD)Intermediate

You'll be designing and building CI/CD pipelines for your features. This includes setting up automated testing, security scanning, and deployment strategies (like canary releases). You can troubleshoot pipeline failures effectively.

Terraform (Infrastructure as Code)Intermediate

You'll write reusable Terraform modules from scratch to provision and manage cloud resources. You'll understand state management and be able to safely run `plan` and `apply` for infrastructure changes.

Datadog (Observability)Intermediate

You'll create sophisticated monitors and alerts for your services. You'll build comprehensive dashboards to track key metrics and use APM (Application Performance Monitoring) to trace requests and pinpoint performance bottlenecks in distributed systems.

PostgreSQL (Database)Intermediate

You'll design database schemas for new services, write optimised SQL queries, and understand execution plans. You'll also manage database migrations and indexing strategies to keep things fast.

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 New FeatureProposes options, needs guidance and approval from Senior Engineer.Designs and proposes a detailed technical approach, consults with Senior Engineer, then proceeds independently.Defines the technical approach, gets high-level buy-in, and guides others on implementation.
Production Incident ResolutionAssists with data gathering and debugging under direct supervision.Diagnoses root cause, proposes and implements fix for known issues; escalates novel or high-impact issues to Senior Engineer.Leads incident response, identifies root cause, implements fix, and drives preventative measures.
Code Review FeedbackFocuses on basic correctness and adherence to style guides.Provides constructive feedback on design, logic, test coverage, and potential edge cases.Reviews for architectural soundness, performance implications, and long-term maintainability, mentoring the author.
Tool/Library Selection (within a feature)Suggests options, needs approval.Researches and recommends a tool/library, justifies choice, gets approval from Senior Engineer.Evaluates, selects, and champions new tools/libraries for team-wide adoption.

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.

Cycle Time (Commit to Deploy)
This measures how quickly your code goes from being committed to Git to actually running in production. It's a key indicator of efficiency and how smoothly our CI/CD pipeline works.
Target · < 24 hours (for most features)

You push a feature branch on Monday morning, it's reviewed by lunch, merged and deployed by Tuesday morning. That's a great cycle time.

Pull Request Rework Rate
This isn't about minor nits; it's about how often your code needs significant changes or a complete rethink after a review. We're looking for well-thought-out solutions from the start.
Target · < 15% of PRs require major re-architecture post-review

Out of 10 PRs, only one needed a fundamental change to its approach after review, rather than just small tweaks. That's hitting the target.

Bug Introduction Rate
We're tracking how many bugs you introduce into the codebase that make it past testing and into production. We all make mistakes, but we want to learn from them and reduce them over time.
Target · < 3 bugs per 1,000 lines of code (in services you own)

In a quarter, you contributed 2,000 lines of code to a service, and only 4 production bugs were traced back to your changes. That's a good result.

Test Coverage & Quality
It's not just about the percentage, but also the quality of your tests. Do they actually catch regressions? Are they readable and maintainable?
Target · Maintain 80%+ test coverage for new features; tests are clear and provide good feedback.

You implement a new API endpoint, and your PR includes unit and integration tests that cover all major use cases, including edge cases, and they're easy for another engineer to understand.

Code Quality & Maintainability
This is about how clean, readable, and well-structured your code is. Can another engineer pick it up and understand it quickly? Is it easy to extend or debug?
  • Consistent positive feedback in code reviews about clarity and structure
  • minimal refactoring needed by others on your contributions
  • adherence to team coding standards without prompting.
Collaboration & Communication
How well do you work with others? Do you explain your technical decisions clearly? Are you open to feedback and proactive in helping teammates?
  • Active and constructive participation in sprint ceremonies
  • clear explanations of technical designs to Product Managers
  • positive feedback from peers on code review interactions
  • proactive offers to pair program or unblock teammates.
Problem Solving & Debugging
When things break (and they will), how effectively do you diagnose and fix issues? Do you approach problems systematically, or do you jump to conclusions?
  • Successfully debugging complex issues in production or staging environments
  • clear explanations of root causes and preventative measures in post-mortems
  • ability to break down large problems into smaller, manageable pieces
  • using tools like profilers and debuggers effectively.
Ownership & Initiative
Do you take responsibility for your work from start to finish? Do you spot problems and suggest solutions, rather than waiting to be told what to do next?
  • Proactively identifying potential issues in feature designs
  • taking a feature from initial spec to deployment without constant oversight
  • suggesting improvements to existing systems or processes
  • following up on your work even after it's 'done' to ensure it's stable.

5Would you like it

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

What people enjoy
Seeing Your Code in Production

You get a real buzz from knowing that the feature you built yesterday is now being used by thousands of customers today. You'll be checking logs and metrics to see its impact.

The new checkout flow you worked on went live, and you're excited to see the conversion rates improve, knowing your code made that happen.

Solving Tricky Technical Problems

You enjoy the challenge of a complex bug or a performance bottleneck. You're not afraid to dive into unfamiliar code or spend a day debugging a distributed system.

You've been handed a bug report that's stumped everyone for a week. You systematically dig in, find the obscure race condition, and get it fixed. That's a good day for you.

Continuous Learning & Growth

You're always looking for new technologies, better ways to write code, or deeper understandings of how our systems work. You'll spend personal time exploring new tools or concepts.

You've just finished a project and you're already looking at ways to improve your Go skills, perhaps by reading a new book or trying out a different framework. You're always pushing yourself.

What frustrates people
  • The Undocumented Legacy System: You'll inherit a critical service written years ago with no tests, no documentation, and everyone's too scared to touch it.
  • Mid-Sprint Requirement Changes: You're nearly done with a feature, and suddenly the goalposts move, invalidating your technical approach.
  • The 3 AM On-Call Alert: The pager will go off for a cascading failure, usually due to something silly like an expired certificate.
  • Pull Request Purgatory: Your PR sits for days, bogged down by endless debates over minor stylistic points, while the core logic is solid.
  • Dependency Hell: Spending half a day trying to get the project to build on your machine because of conflicting library versions and an outdated README.
What this role does not give you
  • A perfectly clean, greenfield project every time.
  • Complete freedom from legacy code or technical debt.
  • A role where you only write code and don't need to communicate with others.
  • Guaranteed 9-to-5 work; sometimes production issues mean late nights or early mornings.

6Who you work with

Your work directly contributes to the reliability, scalability, and feature set of our core products. You're not just writing code; you're building the foundations that our business runs on. Get it right, and we keep growing. Get it wrong, and we slow down, plain and simple.

Inside the business
  • Your Engineering Manager (for career development and priorities)
  • Product Managers (to understand what needs building)
  • QA Engineers (to ensure what you build actually works)
  • Other Software Engineers (for code reviews and collaboration)
  • Site Reliability Engineers (to ensure your services are stable)
Outside the business
  • Occasionally, you might interact with external vendors if we're integrating a new tool, but this isn't a core part of the job.

7What you need before you start

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

  • At least 2 years of professional experience building and deploying software in a team environment, preferably with Go or Python.
  • A solid grasp of data structures, algorithms, and object-oriented design principles.
  • Experience with cloud platforms (ideally AWS) and containerisation technologies (Docker, Kubernetes).
  • A proven track record of debugging complex issues in distributed systems.
  • Experience with writing comprehensive tests (unit, integration).

8What to practise next

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

Advanced Distributed Systems Design

Our systems are only getting more complex and distributed. You'll need to move beyond just understanding microservices to designing truly resilient, scalable, and observable distributed systems from the ground up.

Event-Driven Architectures · Fault Tolerance & Resilience Patterns · Consistency Models (CAP Theorem) · Distributed Tracing & Observability

  • This quarter: Read 'Designing Data-Intensive Applications' by Martin Kleppmann.
  • Next quarter: Take ownership of a service's reliability, focusing on improving its SLOs and error budget.
  • Month 6: Lead the design of a new, moderately complex microservice, ensuring it adheres to our resilience patterns.
  • Ongoing: Actively participate in system design discussions, even for projects you're not directly working on, to learn from others.

Quick win: Start identifying potential single points of failure in services you work on and propose small, incremental improvements to your team.

Cloud Cost Optimisation (AWS Focus)

Cloud costs are a significant overhead. As you take on more responsibility, you'll need to think about not just building things, but building them *efficiently*. This isn't just for finance; it's a core engineering skill.

EC2 Instance Optimisation · Serverless Cost Management · Storage Optimisation (S3, DynamoDB) · Networking & Data Transfer Costs

  • This month: Review the AWS billing dashboard for services your team owns. Identify the top 3 cost drivers.
  • Next month: Propose one small change (e.g., rightsizing an EC2 instance, optimising a DynamoDB table) that could save us money.
  • Month 3: Work with your team to implement a cost-saving measure and track its impact.
  • Ongoing: Integrate cost considerations into your technical designs for new features.

Quick win: Look for unused or underutilised resources in your AWS account and suggest their removal or reduction. It's often easier than you think.

9Staying current once you are in

What people here do to keep up
  • Regularly contribute to open-source projects or maintain a personal technical blog to showcase your skills and learning.
  • Attend industry conferences (e.g., GopherCon, KubeCon) or local meetups to network and stay current with trends.
  • Complete online courses or specialised bootcamps in areas like advanced Go programming, distributed systems, or cloud security.
  • Actively participate in internal knowledge-sharing sessions or 'lunch and learns' within our engineering team.
  • Mentor junior engineers or new starters informally, helping them navigate the codebase and solve problems.

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 & LLM Integration (for developers)

Honestly, competitors are already using tools like GPT to draft code, generate tests, and summarise complex documentation in minutes. Engineers who figure this out will outproduce their peers significantly. Your value will shift to validating, interpreting, and knowing when *not* to trust the AI's output.

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

Your PlanIllustration

Built for Software Engineer

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

  1. Testing engineering softwareExcellence, Achievement & Learning Limited · covers 8 of 15 standardsLevel 3
  2. Engineering software testingExcellence, Achievement & Learning Limited · covers 4 of 15 standardsLevel 4
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 & LLM Integration (for developers)

Honestly, competitors are already using tools like GPT to draft code, generate tests, and summarise complex documentation in minutes. Engineers who figure this out will outproduce their peers significantly. Your value will shift to validating, interpreting, and knowing when *not* to trust the AI's output.

  • Context Windows & Token Limits
  • Temperature Settings for Code Generation
  • RAG (Retrieval Augmented Generation) for Proprietary Codebases
  • Output Validation & Hallucination Detection
  • Prompt Chaining for Complex Tasks

What you’ll use

Skills this role draws on

Technical

  • System Design & Architecture (Feature Level)
  • Agile/Scrum Methodologies
  • Test-Driven Development (TDD)
  • API Design (REST, gRPC)
  • Site Reliability Engineering (SRE) Principles (Basic)

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

    Junior Software Engineer (L1)

    2-3 years

    Skills to master

    • Solidify core programming in Go/Python, understand our codebase structure, master Git, write comprehensive tests, basic cloud operations (AWS console).

    You're ready to move on when

    • Consistently delivers small, well-defined features with minimal supervision.
    • Provides constructive feedback in code reviews.
    • Can debug common issues independently.
    • Demonstrates a proactive attitude to learning and taking on more complex tasks.
  2. 2

    Software Development Bootcamp Graduate + 1-2 years experience

    1-2 years post-bootcamp

    Skills to master

    • Translate bootcamp knowledge into production-grade code, adapt to enterprise development workflows, deepen understanding of distributed systems, learn our specific tech stack.

    You're ready to move on when

    • Has successfully shipped multiple features in a commercial setting post-bootcamp.
    • Demonstrates strong problem-solving skills and a systematic approach to coding.
    • Can articulate trade-offs in technical decisions.
    • Has a solid portfolio of work showing independent project completion.
  3. 3

    Self-Taught Developer with Strong Portfolio

    3-4 years equivalent experience

    Skills to master

    • Formalise knowledge of data structures/algorithms, gain experience with team collaboration tools (Jira, Git), understand professional software engineering practices (CI/CD, testing).

    You're ready to move on when

    • Maintains active, well-documented open-source projects or complex personal projects.
    • Demonstrates deep expertise in a relevant programming language and framework.
    • Can pass rigorous technical interviews and system design challenges.
    • Shows a strong understanding of software engineering best practices.

11Where this role leads

The long view:We're invested in your growth. This role is a stepping stone, and we'll work with you to craft a career path that aligns with your ambitions and our business needs. Your journey here is just beginning, and we're excited to see where you take it.

Pay & demand

Typical pay £56,914 a year Source: ONS Annual Survey of Hours and Earnings, 2025 (provisional), under the Open Government Licence v3.0

The figure is the median for full-time employees in the ONS occupation this job title codes to (Programmers and software development professionals), from the April 2025 survey — about six months old when published, as ASHE always is. It is that occupation's middle, not this role's. Half earn more.

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

Testing engineering softwareLevel 3

Applied to your work in Software Engineer

This unit aims to provide learners with the skills to plan and perform testing activities for engineering software, while maintaining a safe working environment and adhering to relevant health and safety regulations. Learners will also demonstrate the required occupational behaviours in line with their job role and company objectives.

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

  • Cycle Time (Commit to Deploy)This measures how quickly your code goes from being committed to Git to actually running in production. It's a key indicator of efficiency and how smoothly our CI/CD pipeline works.You push a feature branch on Monday morning, it's reviewed by lunch, merged and deployed by Tuesday morning. That's a great cycle time.< 24 hours (for most features)
  • Pull Request Rework RateThis isn't about minor nits; it's about how often your code needs significant changes or a complete rethink after a review. We're looking for well-thought-out solutions from the start.Out of 10 PRs, only one needed a fundamental change to its approach after review, rather than just small tweaks. That's hitting the target.< 15% of PRs require major re-architecture post-review
  • Bug Introduction RateWe're tracking how many bugs you introduce into the codebase that make it past testing and into production. We all make mistakes, but we want to learn from them and reduce them over time.In a quarter, you contributed 2,000 lines of code to a service, and only 4 production bugs were traced back to your changes. That's a good result.< 3 bugs per 1,000 lines of code (in services you own)
  • Test Coverage & QualityIt's not just about the percentage, but also the quality of your tests. Do they actually catch regressions? Are they readable and maintainable?You implement a new API endpoint, and your PR includes unit and integration tests that cover all major use cases, including edge cases, and they're easy for another engineer to understand.Maintain 80%+ test coverage for new features; tests are clear and provide good feedback.
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 Software Engineer to Senior Software Engineer (L3), and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Software Engineer (L3)→ your design
Where this takes you

We're invested in your growth. This role is a stepping stone, and we'll work with you to craft a career path that aligns with your ambitions and our business needs. Your journey here is just beginning, and we're excited to see where you take it.

See Your Progress GrowIllustration
Software Engineer
  • System Design & Architecture (Feature Level)
  • Agile/Scrum Methodologies
  • Test-Driven Development (TDD)
  • API Design (REST, gRPC)
  • Site Reliability Engineering (SRE) Principles (Basic)
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

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

  1. Senior Software Engineer (L3)

    2-3 years in this role

    You'll move from owning features to leading entire projects or workstreams. You'll mentor junior engineers and start influencing technical direction at a team level.

    • Advanced System Design (multi-service architectures, resilience patterns)
    • Performance Optimisation (identifying and fixing bottlenecks across systems)
    • DevOps & SRE Practices (defining SLOs, managing error budgets, improving operational excellence)
    • Mentorship & Code Quality Stewardship (raising the bar for the whole team)
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, software engineering has its repetitive bits. Imagine if you could offload some of that grunt work and focus on the really interesting, challenging problems. Well, you can. We're embracing AI to make our engineers more productive, not replace them.

For a Software Engineer, AI isn't just a buzzword; it's a co-pilot. It means less time writing boilerplate, less time digging through logs, and more time designing elegant solutions. We're integrating AI tools directly into our workflow to help you ship faster and with higher quality.

Unit Test & Boilerplate Generation

Use tools like GitHub Copilot to automatically generate repetitive unit tests, mock data, and boilerplate code for new API endpoints. This frees you up to focus on the core business logic, not the setup. Honestly, it's a massive time-saver for those tedious bits.

AI-Powered Debugging

When you're faced with a complex stack trace or a cryptic error log, feed it into an AI tool like Sentry AI or a custom LLM. Get instant root cause hypotheses and suggested fixes for those tricky production bugs that used to take hours to unravel. It's like having an expert debugger always at your side.

Automated Tech Documentation

Stop dreading documentation updates. Tools like Mintlify or Copilot for Docs can auto-generate comprehensive documentation (READMEs, API specs, internal wikis) directly from your code and comments. This means your docs are always current, and you spend less time writing them. Future-you will thank you.

Intelligent Code Refactoring

Got a legacy code block that needs some love? Provide an AI assistant with the code and a prompt like 'Refactor this to be more idiomatic Go, add error handling, and improve performance.' It can accelerate modernization efforts, helping you clean up technical debt much faster than before.

Common questions

Common questions

How do you become a Software Engineer?

Common routes in include Junior Software Engineer (L1) (2-3 years), Software Development Bootcamp Graduate + 1-2 years experience (1-2 years post-bootcamp) and Self-Taught Developer with Strong Portfolio (3-4 years equivalent experience). Times vary with prior experience.

Where can a Software Engineer progress to?

This role can lead on to Senior Software Engineer (L3) (2-3 years in this role), depending on the skills you build.

What level is a Software Engineer in the UK?

This role aligns to RQF Level 3 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for a Software Engineer?

Increasingly, Prompt Engineering & LLM Integration (for developers). These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows a Software 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 15 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming a Software 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 3

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—especially in cloud-native development, distributed systems, and modern programming languages—are highly transferable across almost any tech-driven industry, from FinTech to e-commerce, or even deep tech startups. You'll be building a foundation that opens many doors.

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.