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

Systems Analyst

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 Systems Analyst or Lead Systems Architect
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Application Specialist · IT Support Engineer (L2) · Technical Systems Administrator

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 Systems Analyst

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 the go-to person for keeping our core business systems humming. This isn't just about fixing things when they break; it's about making sure our colleagues can actually get their work done every day. You'll spend your time getting stuck into the details, sorting out tricky user issues, and making sure our systems are configured properly. Think of it as being the engine mechanic for our digital operations – you keep the parts moving smoothly.

2What you'd actually use

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

ServiceNow / Jira Service ManagementIntermediate

Managing your ticket queue, updating incident records, configuring basic workflows, creating simple reports, and searching the knowledge base.

Okta / Azure AD (Identity & Access Management)Intermediate

Provisioning and de-provisioning user accounts, resetting passwords, assigning users to existing groups, troubleshooting SSO/MFA issues.

NetSuite / SAP S/4HANA Cloud (ERP)Intermediate

Assisting users with navigation, performing data entry, running pre-built reports, configuring basic fields or workflows within specific modules (e.g., Finance, SCM).

Workday HCM / SAP SuccessFactors (HRIS)Intermediate

Processing employee data changes, pulling standard reports, configuring basic business processes (e.g., absence requests), and answering user 'how-to' questions.

Microsoft 365 / Google Workspace (Collaboration Suite)Intermediate

Administering user licenses, managing distribution lists, configuring shared drives, troubleshooting basic email or collaboration tool issues.

Datadog / New Relic (Observability & Monitoring)Basic

Monitoring dashboards for alerts, escalating issues based on runbooks, performing initial investigation into performance anomalies.

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
User Access ProvisioningFollows documented process, escalates any non-standard requests.Independently provisions/de-provisions users, troubleshoots access issues, makes routine group assignments. Escalates complex permission requests.Designs and optimises access roles and groups, manages complex permission matrices, audits access for compliance.
System Configuration ChangesExecutes changes as instructed, requires peer review for all changes.Makes routine configuration changes (e.g., adding fields, updating dropdowns) within approved change windows. Consults with senior on impact of non-routine changes.Designs and implements complex configurations, defines best practices for configuration management, approves changes made by junior staff.
Incident ResolutionResolves L1 incidents using runbooks, escalates L2/P1 incidents immediately.Independently resolves L2 incidents, performs initial root cause analysis, escalates P1 incidents with clear diagnostics. Decides on best resolution path for routine issues.Leads P1 incident resolution, coordinates multiple teams, makes critical decisions under pressure, defines incident management processes.
Vendor InteractionLogs support tickets with vendors, provides requested information.Engages directly with vendor support for L2/L3 issues, follows up on tickets, understands vendor documentation. Escalates unresolved vendor issues to manager.Manages vendor relationships for specific products, evaluates vendor performance, contributes to vendor selection processes.

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.

Ticket Resolution Time (L2)
The average time it takes you to resolve escalated L2 support tickets from when they land in your queue.
Target · Average resolution under 8 hours

If you close 10 tickets in a week, and the total time spent resolving them was 60 hours, your average resolution time is 6 hours. We're looking for consistent improvement here.

User Satisfaction (CSAT)
Feedback from users on the quality and helpfulness of your support after a ticket is closed.
Target · Maintain 90%+ positive feedback

If 95 out of 100 users rate your support as 'good' or 'excellent' after you've helped them, you're hitting the mark. It's about being helpful, not just fast.

Configuration Accuracy
How often system configurations or data entries you make are correct the first time, without needing rework or causing downstream issues.
Target · Less than 2% error rate on configurations

You set up 50 new user accounts and configure 20 application modules in a quarter. If only one of those configurations needs to be corrected later because of an error you made, that's a 1.4% error rate – spot on.

System Uptime Contribution
Your direct impact on preventing and resolving incidents that affect system availability for specific applications you support.
Target · Contribute to 99.9% uptime for assigned Tier 2 applications

You proactively spot a potential issue in Datadog, escalate it, and help resolve it before it becomes a major outage. That's a direct contribution to uptime.

Proactive Problem Identification
You don't just fix what's broken; you look for patterns, identify underlying issues, and suggest ways to prevent them from happening again.
  • You'll be bringing up recurring issues in team meetings, proposing small improvements to processes, or flagging potential system weaknesses to your manager before they blow up into bigger problems. We'll see you suggesting tweaks to our monitoring or runbooks.
Quality of Documentation
How well you update existing knowledge base articles, create new ones, or document solutions for tricky problems.
  • Other team members will refer to your documentation to solve similar issues. Your manager won't have to chase you for updates after you've fixed something complex. It's about making sure the next person (or future you!) can understand what happened.
Collaboration & Peer Support
How effectively you work with the wider IT team, including the service desk, and how you help colleagues out.
  • You'll be known for jumping in to help a colleague when they're stuck, sharing your knowledge, and communicating clearly with the service desk about ticket handovers. People will say you're easy to work with and a good source of practical advice.
Learning & Development Application
How you take on new challenges, learn new systems, and apply that knowledge to improve your work.
  • You'll be asking for opportunities to learn new modules or tools, showing initiative in self-study, and demonstrating that you're applying what you've learned to solve problems more efficiently or take on more complex tasks. You're not just 'doing the job'
  • you're growing in it.

5Would you like it

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

What people enjoy
Solving Puzzles

You get a real buzz from taking a tangled, unclear system problem and methodically working through it until you find the solution. It's like a daily logic puzzle, and you love the 'aha!' moment when it all clicks into place.

A user can't log into an application, and the logs are showing a generic error. You'll spend an hour tracing their account through Okta, Azure AD, and the application's own user directory until you pinpoint a misconfigured group membership. That's your kind of win.

Making a Tangible Difference

You enjoy seeing the direct impact of your work. When you fix an issue, you know you've immediately made someone's day easier or enabled a business process to continue. It's not abstract; it's concrete and immediate.

You resolve a critical issue with the ERP system that was preventing Finance from closing month-end. Knowing that your fix directly allowed the company to meet its reporting deadlines is genuinely satisfying.

Continuous Learning & Mastery

You're never satisfied with just knowing 'enough'. You want to understand the deeper workings of the systems, learn new features, and become a true expert in the applications you support. The idea of constantly expanding your technical toolkit excites you.

You'll spend some of your own time (or company-provided learning time) digging into new features of ServiceNow or exploring advanced configurations in Workday, just because you want to know more and be better at your job.

What frustrates people
  • Dealing with users who haven't tried basic troubleshooting steps before raising a ticket (e.g., 'Have you tried turning it off and on again?').
  • Working on legacy systems that are clunky, poorly documented, and prone to unexpected failures.
  • Trying to troubleshoot an issue where multiple systems are involved, and it's unclear where the actual problem lies (the 'integration tax' is real).
  • Having to say 'no' to a user's request because it violates security policy or system architecture, even though you want to help.
  • The constant tension between fixing urgent issues and finding time for proactive improvements or learning.
What this role does not give you
  • A purely strategic, hands-off role; you'll be doing a lot of actual system work.
  • A predictable, 9-to-5 schedule every single day; urgent issues can pop up.
  • A role where you get to build brand-new, cutting-edge software from scratch; it's more about configuring and maintaining existing enterprise systems.
  • A role with direct reports or team leadership responsibilities at this level.

6Who you work with

Your work ensures that our critical business applications are available, performant, and correctly configured. If you do your job well, our teams can process orders, manage employees, and communicate effectively without system hiccups. If you don't, well, things grind to a halt pretty quickly, impacting productivity and potentially even customer satisfaction.

Inside the business
  • End-users across all departments (Sales, Marketing, Finance, HR)
  • IT Service Desk team (for L1 escalations)
  • Senior Systems Analysts and Architects
  • Business Process Owners (e.g., Head of Finance for ERP issues)
Outside the business
  • Software vendors' support teams (e.g., ServiceNow, Okta)

7What 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 an IT support, systems administration, or application specialist role, dealing with enterprise-level software.
  • Proven ability to troubleshoot complex technical issues methodically and communicate solutions clearly.
  • Experience with at least two of the core platforms mentioned (e.g., ServiceNow, Okta, Workday, NetSuite) at an administration or L2 support level.
  • A solid understanding of basic networking concepts (e.g., DNS, TCP/IP) and how they relate to application connectivity.
  • Demonstrable experience in creating and maintaining technical documentation.

8What to practise next

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

Basic Scripting & Automation (PowerShell/Python)

Many routine system tasks can (and should) be automated. Knowing how to write simple scripts will dramatically increase your efficiency and reduce manual errors.

Variables & Data Types · Conditional Logic (If/Else) · Loops (For/While) · API Interaction Basics

  • This week: Find a free online course on Python or PowerShell basics (e.g., Codecademy, Microsoft Learn).
  • This month: Write a simple script to automate a task you do at least once a week (e.g., pulling a user list, checking a service status).
  • Month 2: Learn how to use a system's API (if available) to pull data or make a simple change via script.
  • Month 3: Share your automation ideas with your manager and senior colleagues; see where you can contribute to larger automation efforts.

Quick win: Write a basic script to generate a report of inactive user accounts in Azure AD. It's a small win, but it builds confidence.

Cloud Service Fundamentals (IaaS, PaaS, SaaS)

More and more of our systems are cloud-based, or integrate with cloud services. A deeper understanding of cloud concepts will help you troubleshoot integration issues and understand system architecture better.

Infrastructure as a Service (IaaS) · Platform as a Service (PaaS) · Software as a Service (SaaS) · Cloud Security Basics

  • This week: Read up on the differences between IaaS, PaaS, and SaaS.
  • This month: Complete a free 'Cloud Fundamentals' course from AWS, Azure, or GCP.
  • Month 2: Research how one of our core SaaS applications (e.g., Workday) integrates with other cloud services.
  • Month 3: Start thinking about how cloud concepts apply to our own internal infrastructure and suggest improvements.

Quick win: Identify one of our existing systems that relies heavily on cloud infrastructure and learn the basic services it uses (e.g., Azure SQL Database for a particular app).

9Staying current once you are in

What people here do to keep up
  • Actively participate in online forums and communities related to the systems we use (e.g., ServiceNow Community, Workday Community) to learn from peers and stay updated.
  • Dedicate time each week to exploring new features or modules within our existing systems in a sandbox environment.
  • Attend relevant webinars or virtual conferences to keep abreast of industry trends and best practices in systems management.
  • Seek out opportunities to shadow senior colleagues on complex projects or incident resolutions to learn advanced troubleshooting techniques.
  • Take advantage of any internal training programmes or lunch-and-learns we offer on new tools or processes.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Prompt Engineering for Systems Support

AI assistants are getting smarter, and knowing how to ask them the right questions is becoming a superpower. You'll be able to get faster, more accurate answers for troubleshooting or configuration queries.

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

Your PlanIllustration

Built for Systems Analyst

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

  1. Provide technical support for computer application software and equipment for learning activitiesETC Awards Limited · covers 1 of 2 standardsLevel 3
  2. Providing technical sales and marketing support for engineering activitiesExcellence, Achievement & Learning Limited · covers 1 of 2 standardsLevel 3
  3. Technical Support for Computerised Medical DevicesPearson Education Ltd · covers 1 of 2 standardsLevel 4
  4. Systems Analysis and DesignNCFE · covers 1 of 2 standardsLevel 3
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering for Systems Support

AI assistants are getting smarter, and knowing how to ask them the right questions is becoming a superpower. You'll be able to get faster, more accurate answers for troubleshooting or configuration queries.

  • Clear & Concise Prompting
  • Contextual Information
  • Iterative Prompting
  • Output Validation

What you’ll use

Skills this role draws on

Technical

  • ITIL Framework (Foundational)
  • Business Process Understanding
  • Data Governance Basics
  • Systems Development Life Cycle (SDLC) / Agile Concepts

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 Systems Analyst

    1-2 years

    Skills to master

    • L1 incident resolution, basic system navigation, following runbooks, user account basics, clear documentation.

    You're ready to move on when

    • Consistently resolves L1 tickets accurately and efficiently.
    • Can independently perform basic system tasks (e.g., password resets, simple data entry).
    • Demonstrates a keen interest in learning how systems work and asking insightful questions.
    • Proactively updates documentation after resolving an issue.
  2. 2

    IT Support Specialist (L2)

    2-3 years

    Skills to master

    • Advanced troubleshooting, L2 incident management, understanding of business processes, basic system configuration, effective user communication.

    You're ready to move on when

    • Consistently resolves complex L2 issues without escalation.
    • Can identify patterns in recurring problems and propose preventative measures.
    • Is seen as a go-to person for specific application support by users and peers.
    • Takes initiative to learn new system modules or features.
  3. 3

    Junior Application Administrator

    2-3 years

    Skills to master

    • Deep knowledge of a specific application (e.g., Salesforce, Workday), module configuration, basic reporting, user training.

    You're ready to move on when

    • Becomes the subject matter expert for a particular business application.
    • Can configure new features or modules within that application with minimal guidance.
    • Successfully delivers small application enhancement projects.
    • Proactively identifies ways to optimise the application for users.

11Where this role leads

The long view:Your career path here isn't a rigid ladder; it's more like a tree with many branches. We're committed to helping you find the path that best suits your strengths and ambitions, whether that's becoming a technical guru, a team leader, or something else entirely. It all starts with doing great work as a Systems Analyst.

Pay & demand

The figure is the median for full-time employees in the ONS occupation this job title codes to (IT business analysts, architects and systems designers), 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 Systems Analyst 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.

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

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:

Provide technical support for computer application software and equipment for learning activitiesLevel 3

Applied to your work in Systems Analyst

This unit aims to equip learners with the skills and knowledge to provide effective technical support for computer application software and equipment used in learning activities. Learners will be able to troubleshoot common issues, provide guidance to users, and understand the processes involved in delivering technical support.

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 Systems Analyst

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.

  • Ticket Resolution Time (L2)The average time it takes you to resolve escalated L2 support tickets from when they land in your queue.If you close 10 tickets in a week, and the total time spent resolving them was 60 hours, your average resolution time is 6 hours. We're looking for consistent improvement here.Average resolution under 8 hours
  • User Satisfaction (CSAT)Feedback from users on the quality and helpfulness of your support after a ticket is closed.If 95 out of 100 users rate your support as 'good' or 'excellent' after you've helped them, you're hitting the mark. It's about being helpful, not just fast.Maintain 90%+ positive feedback
  • Configuration AccuracyHow often system configurations or data entries you make are correct the first time, without needing rework or causing downstream issues.You set up 50 new user accounts and configure 20 application modules in a quarter. If only one of those configurations needs to be corrected later because of an error you made, that's a 1.4% error rate – spot on.Less than 2% error rate on configurations
  • System Uptime ContributionYour direct impact on preventing and resolving incidents that affect system availability for specific applications you support.You proactively spot a potential issue in Datadog, escalate it, and help resolve it before it becomes a major outage. That's a direct contribution to uptime.Contribute to 99.9% uptime for assigned Tier 2 applications
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 Systems Analyst to Senior Systems Analyst, and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Systems Analyst→ your design
Where this takes you

Your career path here isn't a rigid ladder; it's more like a tree with many branches. We're committed to helping you find the path that best suits your strengths and ambitions, whether that's becoming a technical guru, a team leader, or something else entirely. It all starts with doing great work as a Systems Analyst.

See Your Progress GrowIllustration
Systems Analyst
  • ITIL Framework (Foundational)
  • Business Process Understanding
  • Data Governance Basics
  • Systems Development Life Cycle (SDLC) / Agile Concepts
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

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

  1. Senior Systems Analyst

    3-5 years from this role

    Level 3 (Senior Professional)

    • Advanced Configuration & Customisation: Designing and implementing complex system configurations, writing basic scripts for automation.
    • Requirements Gathering: Translating complex business needs into detailed technical requirements.
    • Vendor Management: Managing relationships with key software vendors and holding them accountable.
    • System Integration Basics: Understanding how different systems connect and data flows between them.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, a lot of system administration can be a bit repetitive. But what if you could offload some of that to AI? We're already exploring how AI can make your day-to-day work smoother, faster, and frankly, more interesting, by taking away some of the tedious bits.

In Technical_roles, AI isn't here to replace you; it's here to make you a superhero. Imagine spending less time on basic troubleshooting and more time on the really juicy problems. We're building out our AI productivity hub, and you'll be at the forefront of using these tools to transform how we manage our systems.

Automated Ticket Triage & Resolution

Our ITSM tools (like ServiceNow's Virtual Agent) can use AI to read incoming tickets, figure out what they're about, and even resolve common requests like password resets or basic access issues. This means fewer simple tickets landing in your queue, freeing you up for the trickier stuff.

Proactive Anomaly Detection

Imagine a tool like Datadog using AI to sift through millions of system logs and spot tiny, unusual patterns that humans would miss. This helps us catch potential problems before they become full-blown outages, shifting you from reactive firefighting to proactive prevention. You'll be alerted to 'weird' behaviour, not just 'broken' behaviour.

Instant Change Management Comms

Need to tell the Sales team about an upcoming Salesforce maintenance window? Instead of spending ages drafting the perfect email, you'll use an LLM to generate a clear, audience-appropriate draft in seconds. Just give it a few bullet points, and it'll do the rest, saving you loads of time on communications.

Accelerated Troubleshooting & Research

Stuck on a tricky error message? You can feed error logs or system behaviour descriptions into an AI assistant. It'll quickly search documentation, forums, and even vendor knowledge bases to suggest potential causes and solutions, giving you a head start on your detective work. Think of it as a super-smart research assistant.

Common questions

Common questions

How do you become a Systems Analyst?

Common routes in include Associate Systems Analyst (1-2 years), IT Support Specialist (L2) (2-3 years) and Junior Application Administrator (2-3 years). Times vary with prior experience.

Where can a Systems Analyst progress to?

This role can lead on to Senior Systems Analyst (3-5 years from this role), depending on the skills you build.

What level is a Systems Analyst 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 Systems Analyst?

Increasingly, Prompt Engineering for Systems Support. 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 Systems Analyst, works on the job you actually do, and keeps going at your pace rather than a timetable's.

  • Searching and planning stay free. You only pay when you start learning.
  • Your credits are yours. Regulated, and they don't vanish when a subscription ends.
  • Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 2 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming a Systems Analyst: 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 build here – understanding enterprise systems, ITIL processes, cloud fundamentals, and effective troubleshooting – are highly transferable. You could easily move into IT consulting, specialise in a particular software vendor's ecosystem (e.g., a Workday Consultant), or transition into a broader IT Operations role in almost any industry.

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.