UK

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

Network 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 toSenior Network Support Analyst
  • UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Network Support Technician · Junior Network Engineer · IT Network Specialist

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 Network 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 isn't just about fixing things; it's about keeping our digital world running smoothly. You'll be the person tackling network issues head-on, making sure our people can actually do their jobs without a hitch. Think of it as being the engine mechanic for our company's digital highways. You're not just following instructions anymore; you're figuring out the best way to get the job done for routine problems, and you'll know when to ask for help on the really tricky stuff.

2What you'd actually use

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

SolarWinds NPM / Nagios / Zabbix (Network Monitoring)Intermediate

Reading dashboards, acknowledging alerts, performing basic health checks, and investigating initial alert triggers. You'll be spotting 'flapping ports' before they become outages.

ServiceNow / Jira Service Management (ITSM & Ticketing)Intermediate

Managing your personal ticket queue, updating ticket status, following existing knowledge base articles to resolve issues, and creating new 'CRs' for changes.

Wireshark (Packet Analysis)Basic

Capturing traffic on a specific interface, applying basic display filters (e.g., by IP address or protocol) to confirm connectivity or identify basic application issues.

PuTTY / SecureCRT / Windows Terminal (Remote Access & CLI)Intermediate

Using saved sessions to connect to network devices, executing pre-vetted `show` commands (e.g., `show ip interface brief`), and making basic configuration changes.

Confluence / NetBox (Documentation)Intermediate

Finding and following existing documentation (e.g., network diagrams, runbooks), and creating/updating network diagrams (using tools like Visio/Draw.io) and runbooks for common procedures. You'll keep NetBox up to date with IPAM data.

Splunk / Graylog (Log Management)Basic

Performing basic searches on an IP address or hostname to find related events (e.g., firewall denies, switch port status changes) to aid in troubleshooting.

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 Approach for IncidentsFollows documented runbooks and escalates if the issue isn't covered or if unsure.Chooses appropriate troubleshooting methodology (e.g., top-down, bottom-up) for routine problems; escalates novel or complex issues after initial investigation.Defines troubleshooting methodologies for new technologies; leads complex incident resolution; makes real-time decisions during major outages.
Network Configuration ChangesExecutes pre-approved, simple changes under direct supervision (e.g., adding a port to a specific VLAN).Proposes and implements routine configuration changes (e.g., new switch port, basic firewall rule) with peer review and formal 'CR' approval.Designs and implements significant network changes (e.g., new routing protocols, VPN tunnels); approves changes for junior staff; accountable for change success.
Documentation UpdatesFinds and follows existing documentation; updates minor details under guidance.Creates new knowledge base articles for recurring issues; updates network diagrams (using Visio/Draw.io) and runbooks for common procedures.Establishes documentation standards; reviews and approves documentation from junior staff; ensures documentation supports audit requirements.

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.

Mean Time to Resolution (MTTR) for P3 Tickets
How long it takes you, on average, to resolve a standard priority 3 network incident from the moment it hits your queue.
Target · < 4 hours

You pick up a 'printer not connecting' ticket at 10:00, diagnose a misconfigured switch port, fix it, and close the ticket by 11:30. That's 1.5 hours, contributing positively to your MTTR.

First Contact Resolution (FCR) Rate
The percentage of network issues you resolve on your first interaction with the user or without needing to escalate to a more senior engineer.
Target · > 75% for common issues

A user reports 'no network access'. You guide them through basic troubleshooting, identify a faulty network cable, and they're back online without you needing to pass it up the chain. That counts as an FCR.

SLA Compliance for Assigned Tickets
The percentage of your assigned network incident and service request tickets that you resolve within their agreed-upon service level agreement.
Target · 95% of tickets resolved within SLA

If a P2 ticket has a 24-hour resolution SLA, you need to have it fixed and closed before that 24-hour mark hits. Consistently hitting this shows you're managing your workload well.

Knowledge Base Contribution
The number of new or updated knowledge base articles you create or improve based on recurring issues you've resolved.
Target · 2 new or updated articles per month

You keep seeing the same VPN connectivity issue. You write a clear, step-by-step guide for users or IT Service Desk staff to follow, reducing future tickets on that topic.

Quality of Troubleshooting & Documentation
How thoroughly you investigate issues, the clarity of your thought process in tickets, and the completeness of your documentation.
  • Your tickets consistently show a logical troubleshooting path (e.g., 'Checked Layer 1, then Layer 2, then Layer 3'). Colleagues can easily understand your notes and follow your steps. Your manager rarely needs to ask for more detail on a closed ticket.
Proactive Issue Identification
Your ability to spot patterns in recurring issues or monitoring alerts that might point to a bigger problem, even if it's not explicitly assigned to you.
  • You flag up that 'flapping port' alert that's been happening every Tuesday for the last month. You notice a cluster of 'can't get a DHCP lease' tickets from a specific office and suggest investigating the local DHCP server, rather than just restarting user machines.
Team Collaboration & Support
How well you work with the rest of the IT team, especially the Service Desk, and your willingness to help out junior colleagues.
  • The Service Desk team often praises your clear communication. You're happy to walk a new joiner through a common troubleshooting scenario. You offer to help a colleague who's swamped with tickets without being asked.

5Would you like it

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

What people enjoy
Solving Puzzles

You get a kick out of taking a vague problem ('the Wi-Fi is rubbish') and breaking it down into smaller pieces until you find the exact culprit. The satisfaction of a tricky diagnosis and a successful fix is what gets you going.

You spend an hour methodically tracing a 'flapping port' issue back to a faulty patch cable in a dusty comms cabinet, and you feel a real sense of accomplishment.

Keeping Things Running Smoothly

You genuinely care about uptime and reliability. You're motivated by the idea that your work directly contributes to everyone else being able to do their job without interruption. You're the unsung hero of the office.

You proactively spot a potential 'broadcast storm' building up from monitoring alerts and fix it before anyone even notices a slowdown, feeling good that you've averted disaster.

Continuous Learning & Mastery

You're always looking to deepen your understanding of network technologies. You'll spend your lunch break reading up on a new routing protocol or trying to understand *why* 'it's always DNS'.

After resolving an issue, you'll spend extra time researching the underlying technology, not just the quick fix, to make sure you truly understand it for next time.

What frustrates people
  • The 'Network is Slow' Fallacy: Spending hours proving that 99% network uptime and low latency mean the problem is actually the under-resourced application server, yet still being seen as the bottleneck.
  • Vague Tickets: Receiving tickets with the subject 'No internet' from a user in a 10,000-person company with no additional details (no username, no asset tag, no location).
  • Documentation Debt: Trying to troubleshoot a critical outage using a network diagram that was last updated three years and two office moves ago, or having to do 'cable management archaeology' in a rat's nest.
  • On-Call Nightmares: Being woken up at 3 AM for an automated alert that turns out to be a non-production server being rebooted by another team that didn't inform anyone.
  • The 'Quick Fix' Mentality: Being pressured to implement a quick, unvetted change that you know will cause problems down the line, rather than following proper 'Change Management Discipline'.
What this role does not give you
  • A predictable, 9-to-5 schedule every single day. Outages don't care about your plans.
  • A role where you only work on exciting, cutting-edge projects. There's a lot of routine maintenance and troubleshooting.
  • A quiet, isolated environment. You'll be talking to people constantly, often under stress.
  • The ability to completely ignore process. We have processes for a reason, and you'll be expected to follow them, even when they feel clunky.

6Who you work with

This role directly impacts our company's day-to-day operational efficiency. If the network isn't working, neither are our people. You're keeping the lights on, digitally speaking, and making sure our core business functions can run without interruption. You're also building up our knowledge base, which helps everyone resolve issues faster in the future.

Inside the business
  • Your Manager (Senior Network Support Analyst)
  • IT Service Desk Team
  • Server Operations Team
  • Internal Business Users (your 'customers')
Outside the business
  • Internet Service Providers (ISPs)
  • Network Hardware Vendors (e.g., Cisco, Juniper support)

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 a network support or IT support role with a strong network focus.
  • Proven ability to troubleshoot common network issues (e.g., connectivity, Wi-Fi, basic routing) independently.
  • Demonstrable understanding of the OSI model and TCP/IP stack.
  • Experience working with an ITSM ticketing system (e.g., ServiceNow, Jira Service Management).
  • A solid grasp of IP subnetting (IPv4 is a must, IPv6 is a bonus).
  • Experience using command-line interfaces (CLI) for network device configuration and troubleshooting.

8What to practise next

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

Advanced Troubleshooting & Problem Management

As networks become more complex, the easy problems get automated away. You'll be left with the really tricky, intermittent issues that require deeper analysis and a more structured approach to 'Problem Management'—finding and fixing the root cause, not just the symptom.

Root Cause Analysis (RCA) techniques · Performance baselining · Intermittent fault diagnosis · Packet flow analysis (deep dive with Wireshark)

  • This week: Focus on writing detailed, logical troubleshooting steps in every ticket, even for simple issues.
  • This month: Pick one recurring network problem and try to perform a full RCA, even if it's just for your own learning.
  • Month 2: Get comfortable with advanced Wireshark filters and start analysing packet captures for real-world issues.
  • Month 3: Shadow a Senior Analyst during a complex incident or problem management meeting to see how they approach it.

Quick win: Whenever you fix a problem, ask yourself 'Why did this happen?' at least three times. It's a simple habit that builds a problem-solving mindset.

Cloud Networking Fundamentals (Azure/AWS/GCP)

More and more of our infrastructure, and our customers' infrastructure, is moving to the cloud. You won't just be supporting on-premise networks; you'll need to understand how virtual networks, firewalls, and VPNs work in cloud environments. It's a different beast, but the core networking principles still apply.

Virtual Private Clouds (VPCs) / Virtual Networks (VNets) · Cloud routing tables & security groups · Site-to-site VPNs / ExpressRoute / Direct Connect · Cloud-native load balancers & DNS

  • This week: Sign up for a free tier account on Azure or AWS and deploy a basic virtual network.
  • This month: Complete an introductory course on cloud networking fundamentals (e.g., Azure AZ-900 or AWS Cloud Practitioner).
  • Month 2: Try to configure a simple site-to-site VPN between your virtual network and a simulated on-premise network.
  • Month 3: Read up on common cloud network troubleshooting scenarios and best practices.

Quick win: Familiarise yourself with the basic terminology of one cloud provider (e.g., AWS EC2, S3, VPC). Just knowing the names helps you understand conversations.

9Staying current once you are in

What people here do to keep up
  • Regularly engage with industry blogs and forums (e.g., Packet Pushers, Reddit's r/networking) to stay current on new technologies and troubleshooting tips.
  • Attend webinars or virtual conferences from vendors like Cisco, Juniper, or Fortinet to learn about their latest offerings.
  • Participate in online labs or build a home lab to experiment with new network configurations without impacting production.
  • Contribute to open-source networking projects or community discussions if you're feeling adventurous.
  • Take on more complex troubleshooting tasks and proactively seek feedback from senior colleagues.

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: Network Automation Fundamentals

Manual configuration is slow, error-prone, and doesn't scale. Our competitors are already automating routine tasks like VLAN changes, port activations, and even basic troubleshooting steps. This isn't just for engineers anymore; support staff will need to understand and use automation.

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

Your PlanIllustration

Built for Network Support Assistant

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

  1. Networked Systems SecurityNCFE · covers 2 of 10 standardsLevel 3
  2. Managing NetworksPearson Education Ltd · covers 2 of 10 standardsLevel 3
  3. Cisco CCNP TroubleshootingPearson Education Ltd · covers 1 of 10 standardsLevel 2
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.

Network Automation Fundamentals

Manual configuration is slow, error-prone, and doesn't scale. Our competitors are already automating routine tasks like VLAN changes, port activations, and even basic troubleshooting steps. This isn't just for engineers anymore; support staff will need to understand and use automation.

  • Infrastructure as Code (IaC) principles
  • Basic Scripting (Python, Ansible)
  • REST APIs for Network Devices
  • Idempotence

What you’ll use

Skills this role draws on

Technical

  • OSI Model & TCP/IP Stack
  • ITIL Framework (Incident & Change Management)
  • IP Subnetting (IPv4 & IPv6)
  • Network Topologies & Flow
  • Basic Routing & Switching 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

    IT Service Desk Analyst (Level 1/2)

    2-3 years

    Skills to master

    • First-line troubleshooting, incident logging, basic network connectivity checks, excellent customer service, understanding of ITIL processes.

    You're ready to move on when

    • Consistently resolving network-related tickets at the Service Desk level without escalation.
    • Demonstrating a keen interest in network technologies beyond basic user support.
    • Proactively learning about network infrastructure and asking insightful questions.
  2. 2

    Junior Network Support Technician

    1-2 years

    Skills to master

    • Basic network configuration (VLANs, port security), monitoring tool usage, documentation, CLI proficiency for `show` commands.

    You're ready to move on when

    • Independently performing routine network maintenance tasks.
    • Successfully troubleshooting common network issues with minimal supervision.
    • Contributing accurate and useful updates to network documentation.
  3. 3

    Apprenticeship / Graduate Programme (Network Focus)

    2-4 years

    Skills to master

    • Structured learning of network fundamentals, practical application of theory, exposure to enterprise-grade equipment, mentorship.

    You're ready to move on when

    • Successful completion of all programme modules and practical assessments.
    • Demonstrating a strong grasp of network theory and its application.
    • Positive feedback from mentors and project leads on technical aptitude and problem-solving.

11Where this role leads

The long view:Your journey here as a Network Support Assistant is just the beginning. We're committed to helping you build a long, rewarding career in networking, whatever path you choose. The opportunities are vast, and it all starts with mastering the fundamentals and showing that 'insatiably curious' drive to learn.

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

Also named as a next step, with no page in the catalogue yet:

  • Senior Network Support Analyst

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:

Networked Systems SecurityLevel 3

Applied to your work in Network Support Assistant

This unit aims to provide learners with a comprehensive understanding of networked systems security. Learners will gain knowledge of network attacks, their sources, security hardware and software, and organisational aspects of network security, and be able to apply system security measures such as access controls and data encryption.

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

  • Mean Time to Resolution (MTTR) for P3 TicketsHow long it takes you, on average, to resolve a standard priority 3 network incident from the moment it hits your queue.You pick up a 'printer not connecting' ticket at 10:00, diagnose a misconfigured switch port, fix it, and close the ticket by 11:30. That's 1.5 hours, contributing positively to your MTTR.< 4 hours
  • First Contact Resolution (FCR) RateThe percentage of network issues you resolve on your first interaction with the user or without needing to escalate to a more senior engineer.A user reports 'no network access'. You guide them through basic troubleshooting, identify a faulty network cable, and they're back online without you needing to pass it up the chain. That counts as an FCR.> 75% for common issues
  • SLA Compliance for Assigned TicketsThe percentage of your assigned network incident and service request tickets that you resolve within their agreed-upon service level agreement.If a P2 ticket has a 24-hour resolution SLA, you need to have it fixed and closed before that 24-hour mark hits. Consistently hitting this shows you're managing your workload well.95% of tickets resolved within SLA
  • Knowledge Base ContributionThe number of new or updated knowledge base articles you create or improve based on recurring issues you've resolved.You keep seeing the same VPN connectivity issue. You write a clear, step-by-step guide for users or IT Service Desk staff to follow, reducing future tickets on that topic.2 new or updated articles per month
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 Network Support Assistant to Senior Network Support Analyst, and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Senior Network Support Analyst→ your design
Where this takes you

Your journey here as a Network Support Assistant is just the beginning. We're committed to helping you build a long, rewarding career in networking, whatever path you choose. The opportunities are vast, and it all starts with mastering the fundamentals and showing that 'insatiably curious' drive to learn.

See Your Progress GrowIllustration
Network Support Assistant
  • OSI Model & TCP/IP Stack
  • ITIL Framework (Incident & Change Management)
  • IP Subnetting (IPv4 & IPv6)
  • Network Topologies & Flow
  • Basic Routing & Switching 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

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

  1. Senior Network Support Analyst

    3-5 years from current role

    Level 3 (Senior Professional)

    • Leading troubleshooting for complex, undocumented, and intermittent issues.
    • Contributing to 'Problem Management' by identifying recurring issues and proposing solutions.
    • Designing and implementing more significant network changes with less supervision.
    • Deeper expertise in specific network domains (e.g., security, wireless, data centre).

  2. Network Engineer

    4-6 years from current role

    Level 3/4 (Senior/Lead Professional)

    • Designing and implementing new network solutions (e.g., new office build-outs, WiFi refreshes).
    • Developing and implementing network automation scripts (Python, Ansible).
    • Advanced routing protocols (BGP, OSPF) and firewall configuration.
    • Capacity planning and performance optimisation.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, network support can be a grind. The same old tickets, the endless log searches, the 'it's always DNS' jokes that aren't funny anymore. But what if you could ditch the drudgery and focus on the really interesting stuff? Our AI Productivity Hub is here to help you do just that.

For a Network Support Assistant, AI isn't about replacing you; it's about making you a superhero. Imagine having an intelligent assistant that helps you spot problems before they happen, diagnoses issues faster than ever, and even drafts your incident reports. That's the power we're putting in your hands, letting you reclaim hours every week.

Proactive Fault Detection

Use an AI-powered log analyser (like Splunk's ITSI or Datadog) to constantly analyse telemetry from routers, switches, and firewalls. It can identify subtle patterns that precede an outage (e.g., rising CRC errors, unusual latency spikes) and create a predictive ticket *before* users are impacted. You'll be fixing problems before anyone even notices them.

Root Cause Analysis Accelerator

During a major incident, feed alerts and logs from multiple systems (monitoring, syslog, application performance) into an AIOps platform. The AI correlates the events and suggests the most likely root cause, pointing you directly to the faulty device instead of having to check 10 different systems manually. This means less time on 'war room' calls and faster fixes.

Instant Command & Config Syntax

Use a specialised AI assistant (like a fine-tuned LLM) as a 'co-pilot'. Ask it questions like, 'What's the correct command syntax to configure a BGP peer on a Juniper MX204 running Junos 21.4?' or 'Generate a standard ACL to block traffic from this subnet.' It provides instant, accurate answers, eliminating time spent searching through vendor documentation. No more 'it's always DNS' searches for command syntax.

Automated Incident Communication

After resolving an incident, use an AI tool to draft the initial post-mortem or user-facing communication. It can summarise the ticket timeline, translate technical jargon ('asymmetric routing issue') into plain English ('a configuration mismatch caused data to be misdirected'), and structure the report, leaving you to simply review and refine the details. Less admin, more actual network work.

Common questions

Common questions

How do you become a Network Support Assistant?

Common routes in include IT Service Desk Analyst (Level 1/2) (2-3 years), Junior Network Support Technician (1-2 years) and Apprenticeship / Graduate Programme (Network Focus) (2-4 years). Times vary with prior experience.

Where can a Network Support Assistant progress to?

This role can lead on to Senior Network Support Analyst (3-5 years from current role) and Network Engineer (4-6 years from current role), depending on the skills you build.

What level is a Network 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 Network Support Assistant?

Increasingly, Network Automation Fundamentals. 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 Network 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 Network 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 are highly transferable across almost any industry. Every company needs a network, whether it's finance, healthcare, e-commerce, or manufacturing. You could move into a vendor role (e.g., Solutions Architect for Cisco), a consulting role, or specialise in a niche like cloud networking or cybersecurity.

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.