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

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

Also advertised as IT Support Engineer (Infrastructure) · Technical Operations Analyst · Systems Support Specialist · Cloud Operations Assistant

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

You'll be the person keeping our systems ticking over, making sure everything from our servers to our cloud platforms is running smoothly. This isn't just about fixing things when they break; it's about making sure they don't break in the first place, or at least, that we catch it quickly. You'll be a key part of the team that ensures our colleagues and customers can actually get their work done without a hitch.

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

Logging, categorising, escalating, and resolving tickets based on established runbooks. You'll be creating basic reports on your personal ticket volume and managing your queue efficiently.

Datadog / Nagios / ZabbixIntermediate

Acknowledging alerts, performing Level 1 checks (e.g., disk space, CPU usage), and escalating based on documented procedures. You'll also be creating new monitoring dashboards for specific services.

AWS (EC2, S3, IAM) / Azure (VMs, Storage, Entra ID)Intermediate

Performing basic console operations like rebooting instances, checking permissions, mounting storage volumes. You'll also be using CLI/SDKs to automate routine tasks and troubleshoot IAM/Entra ID policy conflicts.

Bash / PowerShellIntermediate

Executing pre-written scripts to perform routine tasks (e.g., backups, log rotation) and making minor modifications to existing scripts. You'll also be writing new, simple scripts from scratch for automation.

Confluence / NotionIntermediate

Using existing runbooks and knowledge base articles to resolve issues. You'll also be authoring new, detailed runbooks and post-mortem documents, actively improving our documentation.

Terraform / AnsibleBasic

Reading and understanding existing Terraform HCL or Ansible playbooks. You'll execute `terraform apply` or `ansible-playbook` on pre-approved code and assist in troubleshooting deployment failures.

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 choice	Coming in	Where you are now	The step above
Incident Resolution (P2/P3)	Follows runbook, escalates if not covered or if unsure. All steps reviewed.	Independently diagnoses and resolves using runbooks, adapts standard approaches. Escalates novel issues.	Leads resolution of complex, non-routine incidents. Designs new runbooks/processes.
System Configuration Changes	Executes pre-approved changes under direct supervision. No independent changes.	Proposes and implements routine, low-risk changes after manager approval. Consults on higher-risk changes.	Designs and implements significant configuration changes. Approves changes for junior team members.
Tool Selection & Usage	Uses assigned tools as instructed.	Chooses appropriate tools from approved list for specific tasks. Proposes new tools for evaluation.	Recommends and evaluates new tools for team adoption. Defines best practices for tool usage.
Documentation Updates	Updates existing documentation with minor changes, follows templates.	Authors new runbooks and knowledge base articles, actively refactors existing docs.	Establishes documentation standards and reviews team's contributions.

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)

The average time it takes you to resolve a high-priority (P1/P2) incident from when it's reported.

Target · Under 4 hours for P2 incidents

If a P2 incident comes in at 10:00 and you resolve it by 13:30, that's 3.5 hours. We're tracking this across all your tickets.

First Contact Resolution Rate

The percentage of service requests or incidents you resolve on your first interaction with the user, without needing to escalate or follow up multiple times.

Target · Over 70% for common service requests

A user asks for a new software installation, and you complete it immediately without needing more info or passing it on. That counts.

SLA Adherence

How consistently you meet the agreed-upon Service Level Agreements for responding to and resolving tickets.

Target · Meet >98% of ticket response and resolution SLAs

If a P3 ticket needs a response within 2 hours and resolution within 2 days, you'll need to hit those targets almost every time.

Ticket Volume Closed

The number of incidents and service requests you successfully close each week.

Target · Consistently close 15-25 tickets per week

You're expected to manage your queue and steadily work through tickets, ensuring no backlog builds up.

Problem Identification & Prevention

Moving beyond just fixing symptoms to identifying and addressing the root cause of recurring issues, preventing future outages.

You'll be able to point to instances where you turned a recurring incident into a permanent fix. This might mean updating a runbook, automating a manual check, or proposing a system change. Your Senior Analyst will notice when the same P3 ticket stops appearing in the queue.

Documentation Quality

How well you contribute to and improve our internal knowledge base and runbooks, making it easier for everyone to resolve issues.

You'll be actively updating existing runbooks, adding new articles for common issues, and making sure your ticket notes are clear enough for someone else to pick up. We'll see this in Confluence activity and feedback from other team members.

User Satisfaction & Communication

How effectively you communicate with users during incidents and how satisfied they are with the support you provide.

We'll be looking for positive feedback from users (sometimes informal, sometimes via surveys). Clear, timely updates during an outage, even if it's just to say 'we're still looking', make a huge difference. You're keeping them in the loop, not leaving them wondering.

Collaboration & Teamwork

How well you work with other teams (Dev, Network, Security) and share knowledge within the Infrastructure team.

You'll be seen as someone who knows when to ask for help and when to offer it. You're not afraid to jump on a call with the Dev team to troubleshoot an application issue, and you're happy to share what you've learned with junior colleagues or during team huddles.

5Would you like it

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

What people enjoy

Solving Tricky Puzzles

You get a real buzz from taking a vague problem ('the system's slow') and methodically diagnosing it down to the exact misconfiguration or resource bottleneck. It's like being a detective for IT issues.

Successfully tracking down a sporadic application crash to a specific memory leak in a background process, then implementing a fix.

Keeping Things Running Smoothly

You genuinely enjoy the feeling of knowing that because of your work, people can do theirs. You're motivated by the stability and reliability of the systems you support, and you take pride in preventing outages.

Proactively identifying a disk nearing capacity and expanding it before an outage occurs, then documenting the process.

Learning and Growing Technically

You're eager to get your hands on new tools, understand new cloud services, and improve your scripting skills. Every incident is a learning opportunity, and you're always looking for ways to deepen your technical knowledge.

Taking the initiative to learn a new PowerShell module to automate a task you previously did manually.

What frustrates people

Vague Tickets: Spending the first 30 minutes of every investigation just trying to extract basic information from a user who submitted a ticket saying, 'The system is slow.'
Alert Fatigue: Being inundated with hundreds of low-priority, non-actionable alerts from poorly configured monitoring, making it easy to miss the one that actually matters.
On-Call Burnout: The pager going off at 2 AM for a non-production server that could have waited until morning, ruining your sleep for no good reason.
Documentation Debt: Trying to fix a critical legacy system using a runbook that was last updated six years ago and references servers that no longer exist.
The Blame Game: The inevitable finger-pointing between the network, database, application, and infrastructure teams during a complex outage.

What this role does not give you

A perfectly predictable 9-to-5 schedule (on-call rotation is part of the deal).
The chance to always build shiny new things (a lot of the job is maintaining and improving existing systems).
Complete control over all technical decisions (you'll work within established architectures and processes).

6Who you work with

This role is absolutely critical for day-to-day operations. If our infrastructure isn't stable, our teams can't do their jobs, and our customers can't use our products. You're essentially the first line of defence against outages and slow systems, directly impacting employee productivity and customer satisfaction. Get it right, and we save money and keep everyone happy. Get it wrong, and we're looking at lost revenue and frustrated users.

Inside the business

Internal users (Sales, Marketing, Finance)
Software Development Team
Network Operations Team
Information Security Team

Outside the business

Cloud Service Providers (AWS, Azure)
Software Vendors (ServiceNow, Datadog)

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 infrastructure role.
Demonstrable experience with both Linux and Windows server operating systems.
Proven ability to troubleshoot network connectivity issues and understand basic networking concepts.
Familiarity with at least one major cloud platform (AWS or Azure) and its core services.
Experience with an ITSM platform like ServiceNow or Jira Service Management for ticket management.
Basic scripting skills in Bash or PowerShell (you can read and modify existing scripts, and write simple new ones).
A genuine curiosity for how systems work and a drive to solve problems permanently.

8What to practise next

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

Infrastructure as Code (IaC) Mastery

Manual infrastructure provisioning is slow, error-prone, and hard to audit. IaC is the standard for building and managing infrastructure reliably and repeatedly. You'll need to move beyond just running existing code to actually writing and maintaining it.

Terraform HCL syntax and module development · Ansible playbook and role creation · State management and drift detection · CI/CD pipelines for infrastructure deployments · Policy-as-code (e.g., Sentinel, OPA) basics

This month: Complete an online course on Terraform or Ansible fundamentals.
Next quarter: Write a simple Terraform module to deploy a single EC2 instance or Azure VM.
Month 4-6: Work with a Senior Engineer to contribute to an existing IaC project, focusing on adding new features or fixing bugs.
Month 7-9: Learn how to manage Terraform state files and troubleshoot common IaC deployment failures.

Quick win: Set up a personal sandbox environment in AWS or Azure and practice deploying simple resources using Terraform. Break it, fix it, learn from it.

Container Orchestration (Kubernetes Basics)

Many of our new applications are being deployed in containers, managed by Kubernetes. Even if you're not a full-blown SRE, understanding the basics of how these platforms work is becoming essential for troubleshooting and supporting modern applications.

Docker fundamentals (images, containers, volumes) · Kubernetes architecture (nodes, pods, deployments, · Basic `kubectl` commands for inspecting cluster st · Understanding YAML manifests for Kubernetes resour · Troubleshooting containerised application issues

This month: Complete an online tutorial on Docker basics and run a few containers locally.
Next quarter: Take an introductory course on Kubernetes (e.g., 'Kubernetes for Absolute Beginners').
Month 4-6: Deploy a simple application to a minikube or kind cluster on your local machine.
Month 7-9: Shadow a Senior Engineer during a Kubernetes-related incident or deployment to see it in action.

Quick win: Install Docker Desktop and run a simple web server in a container. Just getting comfortable with the command line is a great start.

9Staying current once you are in

What people here do to keep up

Regularly participate in online courses or tutorials from platforms like Udemy, Coursera, or Pluralsight to keep your skills sharp.
Attend industry webinars or virtual conferences to stay up-to-date on emerging technologies and trends in infrastructure.
Actively contribute to our internal knowledge base and runbooks, sharing your learnings with the team.
Seek out mentorship opportunities from senior engineers within the team to accelerate your growth.
Set up a personal cloud sandbox environment (e.g., AWS Free Tier, Azure Free Account) to experiment with new services and practice IaC.

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: Advanced Automation & Orchestration

Manual tasks are becoming a thing of the past. If you're still clicking through GUIs for routine work, you'll be left behind. Automation is key to efficiency, reliability, and freeing up time for more interesting problems.

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

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.

Advanced Automation & Orchestration

Manual tasks are becoming a thing of the past. If you're still clicking through GUIs for routine work, you'll be left behind. Automation is key to efficiency, reliability, and freeing up time for more interesting problems.

API integration for system interaction
Orchestration tools (e.g., Ansible, Azure Automati
Event-driven automation (e.g., serverless function
Error handling and idempotency in scripts
Version control for automation scripts (Git)

Cloud Cost Optimisation Fundamentals

Cloud spend can quickly get out of control if not managed properly. Every infrastructure professional needs to understand the financial impact of their decisions and how to identify opportunities to save money without compromising performance.

Understanding cloud billing models (on-demand, res
Identifying idle or underutilised resources
Rightsizing instances based on actual usage
Cost allocation tags and reporting
Storage tiering strategies (e.g., S3 Intelligent-T

What you’ll use

Skills this role draws on

Technical

ITIL Framework
Network Troubleshooting (OSI Model)
System Administration Fundamentals
Root Cause Analysis (RCA)
Security Hardening & Patch Management

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
Junior IT Support Technician / Helpdesk Analyst
2-3 years
Skills to master
- Strong troubleshooting fundamentals, excellent user communication, basic understanding of network and server concepts, ticket management best practices.
You're ready to move on when
- Consistently resolving complex helpdesk tickets without escalation.
- Demonstrating proactive problem-solving beyond just 'fixing' issues.
- Taking initiative to learn about underlying infrastructure components.
- Comfortable with basic command-line operations (Windows PowerShell or Linux Bash).
2
Systems Administrator (Junior/Mid-level)
1-2 years
Skills to master
- Hands-on experience with server OS (Linux/Windows), Active Directory, virtualisation, basic scripting, monitoring tools, understanding of system security.
You're ready to move on when
- Independently managing server patching and updates.
- Troubleshooting performance issues on servers.
- Implementing basic security hardening measures.
- Comfortable with routine system administration tasks in a production environment.
3
Cloud Operations Associate
1-2 years
Skills to master
- Familiarity with core cloud services (EC2, S3, VMs, Storage), cloud networking basics, IAM concepts, cloud monitoring, basic cloud scripting.
You're ready to move on when
- Managing cloud resources via console and CLI.
- Troubleshooting basic cloud service connectivity.
- Understanding cloud cost implications for different services.
- Following cloud security best practices.

11Where this role leads

The long view:Your journey starts here, but where it goes is really up to you. We're committed to providing the opportunities and support for you to build a truly impactful and rewarding career, whether that's leading teams or becoming the go-to technical guru.

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

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:

Cloud Based Systems and SecurityLevel 3

Applied to your work in Infrastructure Support Assistant

The objective of this unit is to enable learners to assess and understand cloud-based systems and their security requirements, configure systems for efficient data management, and investigate potential security threats and legal issues. Learners will be able to recommend improvements to data management practices and mitigate security risks.

How the thinking builds

Remember
Understand
Apply
Analyse
Evaluate
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.

Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
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.
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.
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.
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 Infrastructure 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)The average time it takes you to resolve a high-priority (P1/P2) incident from when it's reported.If a P2 incident comes in at 10:00 and you resolve it by 13:30, that's 3.5 hours. We're tracking this across all your tickets.Under 4 hours for P2 incidents
First Contact Resolution RateThe percentage of service requests or incidents you resolve on your first interaction with the user, without needing to escalate or follow up multiple times.A user asks for a new software installation, and you complete it immediately without needing more info or passing it on. That counts.Over 70% for common service requests
SLA AdherenceHow consistently you meet the agreed-upon Service Level Agreements for responding to and resolving tickets.If a P3 ticket needs a response within 2 hours and resolution within 2 days, you'll need to hit those targets almost every time.Meet >98% of ticket response and resolution SLAs
Ticket Volume ClosedThe number of incidents and service requests you successfully close each week.You're expected to manage your queue and steadily work through tickets, ensuring no backlog builds up.Consistently close 15-25 tickets per week

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 Infrastructure Support Assistant to Senior Infrastructure Analyst/Engineer (L3), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Senior Infrastructure Analyst/Engineer (L3)→ your design

Where this takes you

Your journey starts here, but where it goes is really up to you. We're committed to providing the opportunities and support for you to build a truly impactful and rewarding career, whether that's leading teams or becoming the go-to technical guru.

See Your Progress GrowIllustration

Infrastructure Support Assistant

ITIL Framework
Network Troubleshooting (OSI Model)
System Administration Fundamentals
Root Cause Analysis (RCA)
Security Hardening & Patch Management

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

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

Senior Infrastructure Analyst/Engineer (L3)
3-5 years in current role
From L2 to L3
- Advanced Scripting (Python, Go): Writing complex automation scripts, integrating with APIs.
- Infrastructure as Code (IaC) Development: Designing and writing new Terraform modules or Ansible roles.
- Cloud Architecture Principles: Understanding high availability, disaster recovery, and cost-optimised designs in the cloud.
- Container Orchestration (Kubernetes): Basic administration and troubleshooting of Kubernetes clusters.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, infrastructure support can be a bit of a grind sometimes. The same alerts, the endless log files, the repetitive tasks. But what if you could offload a good chunk of that to AI? We're not talking about replacing you, but giving you a seriously powerful co-pilot.

Imagine having an assistant that can sift through mountains of logs in seconds, predict system failures before they happen, and even draft your incident reports. That's not science fiction anymore. Our AI Productivity Hub is designed to take the tedious out of your day, freeing you up for the interesting, complex problems that actually need your brainpower. Here's how it could look for you:

Automated Log Triage

Use an AI tool to analyse logs from a failing service. The AI can quickly identify the specific error message that started the cascade and suggest the most likely root cause, even pointing you to the relevant runbook. No more endless `grep` commands.

Predictive Health Scoring

An AI model analyses thousands of performance metrics (CPU, memory, disk I/O, network latency) to generate a single 'health score' for a system. It can predict a potential failure hours before traditional threshold-based alerts would trigger, giving you a head start to prevent outages.

Intelligent Runbook Search

Instead of manually searching through Confluence for the right document, use an AI-powered search that understands natural language. Ask 'How do I restart the production billing service?' and it returns the exact steps from the correct, up-to-date runbook, not 50 irrelevant pages. Instant answers, every time.

Draft Post-Mortem Reports

Feed the AI the incident timeline, chat logs from Slack/Teams, and key alerts. It generates a draft RCA document with a summary, timeline, and suggested action items, which you can then review and refine. Saves you hours of administrative work after every major incident.

Common questions

How do you become an Infrastructure Support Assistant?

Common routes in include Junior IT Support Technician / Helpdesk Analyst (2-3 years), Systems Administrator (Junior/Mid-level) (1-2 years) and Cloud Operations Associate (1-2 years). Times vary with prior experience.

Where can an Infrastructure Support Assistant progress to?

This role can lead on to Senior Infrastructure Analyst/Engineer (L3) (3-5 years in current role), depending on the skills you build.

What level is an Infrastructure 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 an Infrastructure Support Assistant?

Increasingly, Advanced Automation & Orchestration and Cloud Cost Optimisation 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 an Infrastructure 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 17 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 an Infrastructure 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 Zavmo curriculum screen: a three-month plan of nine units, ninety credits, each one an Ofqual-regulated unit the learner can tick or untick before starting. — 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 – cloud platforms, automation, system administration, and problem-solving – are highly transferable across almost any industry. Every company needs solid infrastructure. You could move into cloud engineering, DevOps, site reliability engineering, or even specialise in a particular area like network security or data centre operations.

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.

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.

Infrastructure Support Assistant

What's rising in its place

Advanced Automation & Orchestration

Cloud Cost Optimisation Fundamentals

Skills this role draws on

Technical

How you actually get there, here

Junior IT Support Technician / Helpdesk Analyst

Systems Administrator (Junior/Mid-level)

Cloud Operations Associate

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

Roles this leads to

No two people are taught the same way. This is one-to-one, not one-to-many.

A conversation, not a course

No two people run this the same way

This isn't a certificate you file away. It's a passport to the life you're designing.

Your journey starts here, but where it goes is really up to you. We're committed to providing the opportunities and support for you to build a truly impactful and rewarding career, whether that's leading teams or becoming the go-to technical guru.

Everything else the record holds

The career path, and where it branches

Senior Infrastructure Analyst/Engineer (L3)

Where AI is starting to help

Automated Log Triage

Predictive Health Scoring

Intelligent Runbook Search

Draft Post-Mortem Reports

Common questions

You’ve started things before

Less than one coaching session. Every month.

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