UK

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

Global Systems Support Assistant

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 toGlobal Systems Support Manager
  • UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Systems Support Analyst · IT Support Specialist (Global) · Technical Support Engineer (Level 2)

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 Global Systems Support Assistant

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

This role is all about keeping our global teams up and running. You'll be the person our colleagues turn to when their systems aren't behaving, whether it's a tricky login issue or a problem with their work applications. It's a hands-on job where you'll independently solve problems, making sure everyone can get on with their work without a hitch. Honestly, you're the backbone of our digital operations, making sure the tech just… works.

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

You'll be living in our ITSM platform, resolving incidents, fulfilling service requests, and using the knowledge base. You'll also be building basic reports and dashboards to track your own performance.

Okta / Azure AD (Entra ID)Intermediate

You'll manage user provisioning/deprovisioning, handle password and MFA resets, and assign users to existing groups and applications. You'll also troubleshoot basic SSO failures.

Workday HCM / SAP S/4HANA (HRIS/ERP)Basic

You'll assist users with navigation, perform basic data entry corrections based on approved requests, and run standard reports related to user data for troubleshooting.

MS Teams / Confluence (Collaboration Suite)Intermediate

You'll answer user questions about collaboration tools, manage channel/space permissions, and create/update knowledge base articles from templates. You might even build simple workflows.

Microsoft Intune / Jamf (Endpoint Management)Intermediate

You'll enrol devices, deploy pre-packaged applications to user devices, and walk users through basic troubleshooting steps for their laptops and mobile devices. You'll also configure compliance policies.

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
Troubleshooting Steps & ResolutionFollows defined runbooks; escalates if runbook doesn't cover the issue or if unsure.Independently diagnoses and resolves issues using judgment and available tools; consults on novel problems.Defines troubleshooting methodologies; makes critical real-time decisions during P1 incidents; authorises workarounds.
System Configuration Changes (User Level)Performs changes (e.g., password reset, group add) strictly as per documented requests and procedures.Independently applies configuration changes for individual users (e.g., application access, device enrolment) within defined security policies.Approves and implements configuration changes impacting multiple users or system-wide settings; defines security policies for user access.
Escalation & CommunicationEscalates all non-routine issues to L2/supervisor; communicates status updates as instructed.Decides when to escalate to L3/engineering based on troubleshooting limits; communicates directly with users on complex issues and manages expectations.Manages P1 incident communication to wider business; decides on cross-functional escalation paths; represents support in critical incident calls.
Knowledge Base ContributionsUses existing KB articles to resolve issues; reports gaps or inaccuracies.Updates existing KB articles based on new solutions; drafts new articles for common L2 issues with review.Designs KB structure; reviews and approves L1/L2 KB contributions; leads KCS initiatives.

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.

First Contact Resolution (FCR)
The percentage of tickets you resolve on your first interaction with the user, without needing to escalate or follow up multiple times.
Target · > 70%

If you handle 100 tickets in a month and resolve 75 of them on the first go, that's a 75% FCR. Higher is always better, it means you're really getting to the root of things quickly.

Ticket CSAT Score
The average satisfaction rating from users after you've closed their ticket. They'll get a quick survey, and we're looking for honest feedback on your service.
Target · > 4.5/5.0

If 20 users rate your service, and the average comes out to 4.6, you're doing great. It's a direct measure of how happy people are with your help.

SLA Adherence (L2 Tickets)
The percentage of L2 tickets you resolve within the agreed-upon Service Level Agreement timeframe. This means getting things done before they 'breach'.
Target · > 98%

Out of 50 L2 tickets, if you resolve 49 within the SLA, that's 98%. Missing an SLA occasionally happens, but we want to make sure it's rare and for good reason.

Average Handle Time (AHT) for L2 Tickets
The average time you spend actively working on an L2 ticket, from opening to closing. We'll compare this against the team's baseline.
Target · Meet or beat team baseline (e.g., < 45 minutes)

If the team's average is 50 minutes, and your average is 45 minutes, you're being efficient. It's not about rushing, but about effective troubleshooting.

Problem Ownership & Resolution
You don't just fix the symptom; you dig into the 'why'. This means you're not just closing tickets, but you're also making sure the underlying issue is genuinely resolved, even if it involves other teams.
  • You'll see fewer recurring incidents for problems you've handled. You'll proactively follow up with other teams if a ticket is escalated, ensuring a full resolution. Your ticket notes will show a clear, methodical troubleshooting process, not just a quick fix.
Knowledge Base Contribution & Improvement
You're actively helping build our collective knowledge. This means not just using the existing runbooks, but also spotting gaps, suggesting improvements, or even drafting new articles for common issues you've solved.
  • You'll have a few new or updated KB articles published under your name each quarter. You'll be bringing ideas to team meetings about improving our documentation. Colleagues will refer to articles you've written.
Effective Communication & Expectation Management
You're great at talking to people, even when they're frustrated. You can explain complex technical issues in plain English and manage expectations about when something will be fixed.
  • Users will comment on your clear and helpful communication in CSAT surveys. You'll be able to de-escalate tricky situations. You'll proactively update users on ticket progress, even if there's no new news, just to keep them informed.
Process Adherence & Improvement Suggestions
You follow our established processes religiously, but you're also not afraid to point out when a process could be better. You're a guardian of operational excellence, making sure we do things the right way, and then finding ways to make that right way even better.
  • Your audit trails will show consistent adherence to procedures (e.g., for JML processes). You'll regularly bring forward ideas for runbook updates or workflow tweaks in team meetings. You'll spot inconsistencies and help us fix them.

5Would you like it

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

What people enjoy
Solving Puzzles

You get a real kick out of diagnosing a complex technical issue that no one else could figure out. That 'aha!' moment when you find the root cause is genuinely satisfying.

Spending an hour tracing a tricky network connectivity issue across multiple systems, finally identifying a misconfigured firewall rule, and getting everyone back online.

Helping People

You enjoy being the person who unblocks someone's day. Knowing that your technical skills directly enable someone else to do their job well is a big deal for you.

Getting a 'thank you' email from a colleague who was stuck for hours and you got them back up and running in minutes, allowing them to hit their deadline.

Mastering Systems

You love diving deep into how different systems work, understanding their quirks, and becoming the go-to expert for specific platforms like Okta or ServiceNow.

Spending your downtime exploring new features in our ITSM platform or figuring out a more efficient way to manage application access in Azure AD.

What frustrates people
  • The 'It's Broken' Ticket: Receiving tickets with zero useful information, requiring you to spend the first 15 minutes just trying to understand what the actual problem is.
  • Repetitive, Low-Value Tasks: The soul-crushing monotony of resetting the same user's password for the third time this month.
  • Users Who Don't Read: Carefully crafting a knowledge base article with screenshots and step-by-step instructions, only to have users ignore it and log a ticket anyway.
  • Blame without Context: Getting blamed for a system being 'slow' when the issue is with the network, another team's integration, or the user's home Wi-Fi.
  • After-Hours Escalations: The on-call pager going off at 2 AM because of an issue in a different time zone (though this is less frequent at L2, it can happen).
What this role does not give you
  • A quiet, uninterrupted work environment – you'll be interacting with people constantly.
  • Complete control over your task list – urgent issues will always pop up and reprioritise your day.
  • A role where you never have to repeat yourself – some issues just keep coming back.
  • A role where every problem has a clear, documented solution – you'll often be figuring things out for the first time.

6Who you work with

This role directly impacts the daily productivity of every employee across the organisation. If you're doing well, people are working efficiently, systems are reliable, and our business operations run smoothly. If you're not, well, things grind to a halt pretty quickly, leading to lost time, missed deadlines, and a lot of frustrated colleagues. You're essentially the oil in the machine, keeping everything moving.

Inside the business
  • All global employees (end-users)
  • IT Infrastructure Team
  • Application Owners (e.g., HR, Finance)
  • Security Operations Team
  • Other L1 Support Teams
Outside the business
  • Software vendors (e.g., ServiceNow, Okta support)

7What you need before you start

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

  • At least 2-3 years of hands-on experience in a technical support role, ideally in a global or multi-site environment.
  • Proven ability to independently troubleshoot and resolve a wide range of L2 technical issues, not just follow a script.
  • Demonstrable experience with an ITSM platform (like ServiceNow or Jira Service Management) for ticket management.
  • Solid understanding of Identity & Access Management concepts and experience with tools like Okta or Azure AD.
  • Experience supporting Windows and macOS operating systems, including basic command-line troubleshooting.
  • A genuine desire to help people and a calm, methodical approach to problem-solving, even when things are hectic.

8What to practise next

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

Advanced Scripting & Automation (e.g., PowerShell, Python)

As we grow, manual tasks become unsustainable. The ability to write scripts to automate repetitive tasks, manage configurations, or perform bulk operations will be essential for efficiency and consistency.

PowerShell for Windows Administration · Python for API Interactions · Version Control (Git) Basics · Error Handling & Logging

  • This quarter: Pick one repetitive task you do daily and try to automate a small part of it with a simple PowerShell script.
  • Next quarter: Find an online tutorial for Python basics focused on system administration or API interaction.
  • Within 6 months: Contribute a small, reviewed script to our internal automation repository.
  • Within 9 months: Work on a project to automate a common L2 request workflow from start to finish.

Quick win: Start by learning basic PowerShell commands for system information gathering. It's incredibly useful for troubleshooting and you can apply it immediately.

Cloud Infrastructure Fundamentals (Azure/AWS)

More and more of our systems are moving to the cloud. Understanding the basics of cloud services will be critical for troubleshooting cloud-hosted applications and collaborating with our cloud engineering teams.

IaaS, PaaS, SaaS Overview · Virtual Machines & Networking in Cloud · Identity & Access Management in Cloud · Cloud Monitoring & Logging

  • This quarter: Complete a free introductory course on Azure Fundamentals (AZ-900) or AWS Cloud Practitioner (CLF-C01).
  • Next quarter: Shadow a cloud engineer during a troubleshooting session to see how they approach cloud-specific issues.
  • Within 6 months: Identify one of our cloud-hosted applications and familiarise yourself with its basic architecture and monitoring.
  • Within 9 months: Work on a project that involves configuring basic cloud resources for a test environment.

Quick win: Familiarise yourself with the Azure or AWS console. Just poking around and understanding the layout can be a huge first step.

9Staying current once you are in

What people here do to keep up
  • Regularly engage with online technical communities (e.g., Reddit's r/sysadmin, relevant forums) to stay updated on new issues and solutions.
  • Attend webinars or virtual conferences on new technologies or support best practices (we'll cover the costs).
  • Take advantage of our internal training programmes on new system rollouts or advanced troubleshooting techniques.
  • Seek out opportunities to shadow L3 or engineering teams to understand how they tackle more complex 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: AI-Assisted Troubleshooting & Automation

AI isn't just for developers anymore. It's quickly becoming a crucial tool for support teams to speed up diagnosis, automate repetitive tasks, and even predict potential issues. Analysts who can effectively use AI will be significantly more productive.

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

Your PlanIllustration

Built for Global Systems Support Assistant

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

  1. Providing technical sales and marketing support for engineering activitiesExcellence, Achievement & Learning Limited · covers 4 of 10 standardsLevel 3
  2. Providing Operational Support for Computer Control ProgramsCity & Guilds Limited · covers 3 of 10 standardsLevel 3
  3. Provide technical support for computer application software and equipment for learning activitiesGQA Qualifications Limited · covers 3 of 10 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.

AI-Assisted Troubleshooting & Automation

AI isn't just for developers anymore. It's quickly becoming a crucial tool for support teams to speed up diagnosis, automate repetitive tasks, and even predict potential issues. Analysts who can effectively use AI will be significantly more productive.

  • Prompt Engineering for Support
  • AI-Powered Log Analysis
  • RPA (Robotic Process Automation) Basics
  • Ethical AI Use in Support

What you’ll use

Skills this role draws on

Technical

  • ITIL Framework (Incident, Problem, Change, Request Fulfilment)
  • Knowledge-Centered Service (KCS)
  • Root Cause Analysis (RCA)
  • SLA/OLA Management
  • Tiered Support Models (L1-L3)
  • Joiner-Mover-Leaver (JML) Process

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

    L1 Technical Support Analyst

    2-3 years

    Skills to master

    • Mastering first-contact resolution, understanding basic system diagnostics, excellent customer service, and strict adherence to runbooks. You'll need to show you can handle increasing complexity.

    You're ready to move on when

    • Consistently high CSAT scores and FCR rates in an L1 role.
    • Proactively identifying and escalating recurring issues to L2/Problem Management.
    • Demonstrating initiative by trying to solve L2-level problems before escalating.
    • Showing a keen interest in how systems work beyond the surface level.
  2. 2

    IT Helpdesk Technician (External)

    2-4 years

    Skills to master

    • Broad troubleshooting experience across various hardware and software, strong diagnostic skills, and the ability to work independently in a fast-paced environment. Experience with an ITSM platform is crucial.

    You're ready to move on when

    • Successfully managing a diverse ticket queue with minimal supervision.
    • Experience with user provisioning/deprovisioning in previous roles.
    • Ability to explain complex technical issues to non-technical users.
    • A track record of identifying and implementing small process improvements.
  3. 3

    Junior Systems Administrator

    1-2 years

    Skills to master

    • While more focused on infrastructure, this path provides strong system administration fundamentals, scripting skills, and a deeper understanding of network and server operations. You'd need to adapt to a more user-facing support role.

    You're ready to move on when

    • Experience managing user accounts and permissions in Active Directory or Azure AD.
    • Basic scripting skills (e.g., PowerShell) for automation.
    • Understanding of server and network troubleshooting.
    • A desire to apply system administration knowledge to direct user support.

11Where this role leads

The long view:Your journey here starts with solving problems for our colleagues, but it can lead to mastering entire systems, leading teams, or even shaping our overall IT strategy. We're committed to helping you build a career that's both challenging and rewarding. Where you go is really up to you and your ambition.

Pay & demand

Pay and demand for this role will appear here, each figure traced to a named authoritative source (e.g. the ONS Annual Survey of Hours and Earnings, under the Open Government Licence). We don’t show numbers we can’t attribute.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Global Systems Support Assistant 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:

Providing technical sales and marketing support for engineering activitiesLevel 3

Applied to your work in Global Systems Support Assistant

This unit aims to develop the skills and behaviours required to provide technical sales and marketing support for engineering activities. Learners will be able to use company information, produce compliant sales and marketing materials, and adhere to health and safety regulations. This will enable them to effectively contribute to the sales and marketing efforts of an engineering organisation.

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 Global Systems Support Assistant

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.

  • First Contact Resolution (FCR)The percentage of tickets you resolve on your first interaction with the user, without needing to escalate or follow up multiple times.If you handle 100 tickets in a month and resolve 75 of them on the first go, that's a 75% FCR. Higher is always better, it means you're really getting to the root of things quickly.> 70%
  • Ticket CSAT ScoreThe average satisfaction rating from users after you've closed their ticket. They'll get a quick survey, and we're looking for honest feedback on your service.If 20 users rate your service, and the average comes out to 4.6, you're doing great. It's a direct measure of how happy people are with your help.> 4.5/5.0
  • SLA Adherence (L2 Tickets)The percentage of L2 tickets you resolve within the agreed-upon Service Level Agreement timeframe. This means getting things done before they 'breach'.Out of 50 L2 tickets, if you resolve 49 within the SLA, that's 98%. Missing an SLA occasionally happens, but we want to make sure it's rare and for good reason.> 98%
  • Average Handle Time (AHT) for L2 TicketsThe average time you spend actively working on an L2 ticket, from opening to closing. We'll compare this against the team's baseline.If the team's average is 50 minutes, and your average is 45 minutes, you're being efficient. It's not about rushing, but about effective troubleshooting.Meet or beat team baseline (e.g., < 45 minutes)
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 Global Systems Support Assistant to Senior Global Systems Support Assistant, and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Senior Global Systems Support Assistant→ your design
Where this takes you

Your journey here starts with solving problems for our colleagues, but it can lead to mastering entire systems, leading teams, or even shaping our overall IT strategy. We're committed to helping you build a career that's both challenging and rewarding. Where you go is really up to you and your ambition.

See Your Progress GrowIllustration
Global Systems Support Assistant
  • ITIL Framework (Incident, Problem, Change, Request Fulfilment)
  • Knowledge-Centered Service (KCS)
  • Root Cause Analysis (RCA)
  • SLA/OLA Management
  • Tiered Support Models (L1-L3)
  • Joiner-Mover-Leaver (JML) Process
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

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

  1. Senior Global Systems Support Assistant

    3-5 years

    L3 (OFQUAL 6-7)

    • Advanced ITSM Configuration: Building and modifying service catalogue items, configuring complex automation rules within ServiceNow/Jira.
    • Identity & Access Management (IAM) Design: Configuring new application integrations (SAML/SCIM), designing group policies, and conducting access audits.
    • Endpoint Security & Compliance: Defining and implementing compliance policies, managing advanced application deployment packages, and reporting on endpoint security posture.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, a lot of systems support work can be repetitive, and frankly, a bit of a slog. But what if you could offload some of that mundane stuff to AI, freeing you up to tackle the really interesting, complex problems? That's exactly what we're doing here.

We're investing heavily in AI to make your job more rewarding and less about the grind. Imagine having an intelligent assistant that handles the basic stuff, helps you draft perfect responses, and even spots problems before they become P1 incidents. This isn't about replacing you; it's about making you a super-analyst.

L0 Support Automation

Our AI chatbot in MS Teams/Slack can handle the top 20% of repetitive L1 requests automatically (e.g., 'How do I reset my password?'). If it can't solve it, it'll create a perfectly formatted, detailed ServiceNow ticket for you, saving you the initial triage time.

Proactive Incident Detection

Use an AI tool to analyse incoming ticket streams and system logs in real-time. It can spot patterns – like a sudden spike in 'login failed' errors from a specific office – and flag a potential major incident to you before users even notice. You'll shift from reactive firefighting to proactive prevention.

Knowledge Base Generation

After you've resolved a complex ticket, feed your ticket notes and resolution steps into an AI assistant. It'll draft a well-structured, easy-to-read Confluence KB article for you. You just need to quickly review and publish it, turning your solutions into shared knowledge effortlessly.

Empathetic Response Crafting

When you're dealing with a frustrated user, especially on a tricky issue, use an AI assistant to draft a response. You can prompt it with something like, 'Write a clear, empathetic reply explaining that their request for admin rights is denied due to security policy X, and offer alternative solution Y.' It helps you maintain a professional, calm tone, even when you're feeling the pressure.

Common questions

Common questions

How do you become a Global Systems Support Assistant?

Common routes in include L1 Technical Support Analyst (2-3 years), IT Helpdesk Technician (External) (2-4 years) and Junior Systems Administrator (1-2 years). Times vary with prior experience.

Where can a Global Systems Support Assistant progress to?

This role can lead on to Senior Global Systems Support Assistant (3-5 years), depending on the skills you build.

What level is a Global Systems Support Assistant in the UK?

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

What new skills matter most for a Global Systems Support Assistant?

Increasingly, AI-Assisted Troubleshooting & Automation. 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 Global Systems Support Assistant, 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 10 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 Global Systems Support Assistant: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.
Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 2

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

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you'll gain here – problem-solving, system administration, ITIL, and customer focus – are highly transferable. You could move into roles in IT Operations, Cloud Engineering, Information Security, or even into a Product Owner role for an ITSM platform in other organisations. Your deep understanding of user needs and system functionality is valuable everywhere.

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.