UK

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

Security Analyst / Engineer

Here is the whole job, in plain words. What it is, a real day, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Security Engineer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Cyber Security Analyst · Information Security Engineer · SOC Analyst

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 Security Analyst / Engineer

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

This role is all about being on the front lines, getting your hands dirty with the tools, and making sure our systems are actually safe. You're not just monitoring; you're actively investigating, fixing, and learning. Think of yourself as a digital detective, always looking for the bad guys and patching up our defences. It's a busy job, but incredibly rewarding when you stop something nasty in its tracks.

2What you'd actually use

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

Splunk Enterprise Security / Microsoft Sentinel (SIEM)Intermediate

Monitoring dashboards, investigating pre-defined alerts, writing basic search queries to hunt for anomalies, understanding data ingestion.

CrowdStrike Falcon / SentinelOne (EDR)Intermediate

Responding to endpoint detection and response alerts, isolating infected machines, reviewing endpoint activity logs, remediating threats on devices.

Tenable.io / Qualys (Vulnerability Management)Intermediate

Running vulnerability scans, validating scan findings, assigning remediation tickets to IT teams, tracking remediation progress.

ServiceNow GRC / Jira (GRC & Ticketing)Basic

Inputting data for risk assessments, uploading evidence for audit controls, managing and updating security incident and remediation tickets.

Confluence / Slack (Collaboration)Intermediate

Documenting incident timelines, contributing to runbooks, communicating incident updates with the team, sharing threat intelligence.

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
Incident Triage & PrioritisationEscalate all but the most basic, pre-defined alerts to a Senior Analyst.Independently triage and prioritise routine alerts. Escalate critical or novel incidents to a Senior Security Engineer for review and guidance.Lead triage for complex incidents, making initial containment decisions and delegating tasks to junior analysts. Consult with manager on major incident declarations.
Vulnerability RemediationExecute remediation steps as instructed by a Senior Analyst, documenting progress.Take ownership of assigned vulnerabilities, determining the best remediation approach (patch, configuration change) and coordinating with IT Ops. Escalate if remediation is blocked or requires significant resources.Prioritise vulnerabilities across multiple systems, design complex remediation plans, and negotiate timelines with system owners. Approve compensating controls if direct remediation isn't feasible.
Security Tool ConfigurationPerform basic configuration changes under direct supervision (e.g., add an IP to a blocklist).Independently configure and fine-tune existing security tools (e.g., EDR policies, SIEM detection rules) within established parameters. Propose improvements to existing configurations.Design and implement new security tool configurations, architecting detection rules and automation playbooks. Make recommendations for tool enhancements or replacements.

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 Acknowledge (MTTA) Critical Alerts
How quickly you spot and acknowledge a high-priority security alert.
Target · <15 minutes

If a critical alert comes in at 10:00, you should have it acknowledged and be starting your investigation by 10:14 at the latest. We track this automatically in our SIEM.

Remediation SLA Adherence
The percentage of assigned security tickets (vulnerabilities, incident follow-ups) that you close within the agreed service level agreement.
Target · 95% of assigned tickets

If you're assigned 20 tickets this month, you'd need to close 19 of them on time. This includes patching requests, configuration changes, or incident clean-up tasks.

Phishing Simulation Click Rate Reduction
Helping to reduce the number of times users in your assigned business units click on simulated phishing emails.
Target · Reduce click rate by 50% over 12 months (e.g., from 10% to 5%)

You might help identify repeat clickers, suggest targeted training, or work with the awareness team to improve messaging. If your business unit started at 10% click rate, we'd want to see it around 7.5% after 6 months.

False Positive Reduction for Custom Rules
For any detection rules you help create or fine-tune, ensuring they're actually catching real threats, not just generating noise.
Target · <10% false positive rate for rules you've worked on

If you build a new SIEM correlation rule, and 10 alerts fire, we'd expect 9 of them to be genuine security events, not just benign activity. High false positives mean wasted time for the whole team.

Accuracy of Incident Triage & Initial Investigation
How well you assess an alert's severity, gather initial context, and determine the next steps (e.g., escalate, remediate, close).
  • Your manager rarely has to re-triage your incidents. Your initial investigation notes are clear and complete. The right incidents get escalated to the right people at the right time. You can explain your reasoning clearly during incident reviews.
Proactive Identification of Security Issues
Beyond just reacting to alerts, you're looking for potential weaknesses or areas for improvement in our security posture.
  • You flag misconfigurations you've spotted, suggest improvements to existing detection rules, or propose new monitoring. You might notice a trend in alerts that points to a systemic issue and bring it up in team meetings. This isn't about finding huge flaws, but small, consistent improvements.
Collaboration & Team Contribution
How effectively you work with your team and other departments, sharing knowledge and supporting collective goals.
  • You're responsive to requests from IT Ops or Dev teams. You actively participate in team discussions, offering ideas or asking clarifying questions. You're happy to jump in and help a colleague who's swamped with alerts. People genuinely enjoy working with you.
Documentation & Knowledge Sharing
Keeping our internal knowledge base up-to-date and contributing to runbooks and playbooks.
  • Your incident notes are detailed enough for someone else to pick up. You update existing playbooks with new findings. You contribute to our Confluence pages with how-to guides or explanations of common issues. This helps everyone, especially new joiners.

5Would you like it

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

What people enjoy
Solving Complex Puzzles

Every alert is a mini-mystery. You'll love digging through logs, correlating events, and piecing together clues to understand what happened. It's like being a detective, but for computers.

An alert flags suspicious activity on a server. You'll spend hours sifting through network traffic, process logs, and user activity to figure out if it's a real attack or a false alarm, and then explain your findings.

Protecting the Organisation

There's a genuine satisfaction in knowing your work directly contributes to keeping our data, systems, and customers safe. You're a guardian of our digital assets.

You successfully contain a phishing campaign before anyone clicks a malicious link, or you identify and block a piece of malware before it spreads. That feeling of 'I stopped that' is a big part of the reward.

Continuous Learning & Skill Development

The security landscape never stands still, so you'll always have new technologies, threats, and techniques to learn. If you love expanding your knowledge, you'll thrive here.

You'll be encouraged to take courses, attend webinars, and experiment with new tools. You might spend time researching a new ransomware variant to understand its indicators of compromise.

What frustrates people
  • Alert fatigue: Drowning in thousands of low-priority alerts and trying to find the one that actually matters.
  • Legacy systems: Having to secure old, clunky systems that are hard to patch or monitor effectively.
  • Lack of context: Getting an alert without enough information to properly investigate, leading to lots of back-and-forth.
  • User error: Dealing with the same basic security mistakes from users, despite training.
  • The 'we accept the risk' button: When you flag a risk, but a business unit decides to go ahead anyway, leaving you feeling exposed.
What this role does not give you
  • A predictable 9-to-5: Incidents don't care about your schedule, so occasional out-of-hours work is a reality.
  • Complete autonomy on strategy: You'll be executing, not setting the overall security direction.
  • A quiet, solitary job: You'll be collaborating constantly with various teams and people.
  • The ability to fix everything immediately: Sometimes, you'll identify a problem but won't have the authority or resources to fix it straight away.

6Who you work with

Your work directly impacts our ability to detect and respond to cyber threats. If you're on the ball, we catch things early, minimise damage, and maintain trust with our customers. If you miss something, the consequences could be significant, affecting our reputation, finances, and operational continuity. Essentially, you're a crucial part of keeping the lights on and the bad actors out.

Inside the business
  • Your immediate Security team (for collaboration and incident response)
  • IT Operations (to implement fixes and changes)
  • Development teams (to understand new features and potential vulnerabilities)
  • Helpdesk (for user-reported issues and phishing alerts)
  • Project Managers (when security input is needed for new initiatives)
Outside the business
  • Security vendors (for tool support and updates)
  • Threat intelligence providers (to stay on top of new threats)
  • External auditors (occasionally, for evidence gathering)

7What you need before you start

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

  • At least 2-5 years of hands-on experience in a security operations centre (SOC), incident response, or security engineering role.
  • Demonstrable experience with at least one major SIEM platform (e.g., Splunk, Sentinel) and one EDR solution (e.g., CrowdStrike, SentinelOne).
  • Solid understanding of common cyber attack techniques, vulnerabilities, and defence mechanisms.
  • Familiarity with scripting languages (e.g., Python, PowerShell) for automation or data analysis is a big plus, but not strictly essential.
  • A genuine passion for cybersecurity and a drive to continuously learn and improve.

8What to practise next

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

Advanced SIEM/SOAR Engineering

As our environment grows, our SIEM needs to be constantly optimised. You'll move from just using it to actively improving it, building more sophisticated detections and automating responses.

Custom Correlation Rule Development · SOAR Playbook Creation · Data Onboarding & Parsing Optimisation

  • This week: Review our existing SIEM rules and identify one that could be improved or made more efficient.
  • This month: Work with a Senior Engineer to develop a new, more advanced detection rule for a specific threat scenario.
  • Month 2: Start experimenting with our SOAR platform (e.g., Palo Alto Cortex XSOAR) to build a simple automated response playbook.
  • Month 3: Present your improved rule or playbook to the team, explaining the logic and benefits.

Quick win: Familiarise yourself with the query language of our SIEM (e.g., SPL for Splunk) and practice writing more complex searches to find specific events faster.

Proactive Threat Hunting

Waiting for alerts isn't enough anymore. We need to actively seek out threats that might have bypassed our automated defences. This requires a more offensive mindset.

Hypothesis-Driven Hunting · MITRE ATT&CK Framework Application · Endpoint & Network Forensics

  • This week: Read up on a recent high-profile attack and identify the TTPs used, thinking about how you'd detect them.
  • This month: Work with a Senior Engineer to conduct a small, focused threat hunt using our EDR data, looking for a specific TTP.
  • Month 2: Develop a simple threat hunting playbook for a common adversary technique relevant to our industry.
  • Month 3: Share your hunting methodology and any findings with the wider security team.

Quick win: Regularly review threat intelligence feeds (e.g., Mandiant Advantage) and try to map new TTPs to our existing detection capabilities – where are the gaps?

9Staying current once you are in

What people here do to keep up
  • Regularly engage with industry blogs, forums (e.g., SANS Internet Storm Centre, The Hacker News), and threat intelligence feeds to stay current on new threats and vulnerabilities.
  • Participate in local cybersecurity meetups or conferences (even virtual ones) to network and learn from peers.
  • Experiment with home labs or capture-the-flag (CTF) challenges to hone your practical skills in a safe environment.
  • Contribute to open-source security projects or write your own small scripts to automate repetitive tasks.

10How the AI economy is changing work like this

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

The new skill this role is being asked for: Prompt Engineering for Security Investigations

Generative AI models are getting better at summarising logs, drafting incident reports, and even suggesting investigation steps. Analysts who can 'talk' to these AIs effectively will be far more productive.

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

Your PlanIllustration

Built for Security Analyst / Engineer

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

  1. Incident Response, Investigations and ForensicsQualifi Ltd · covers 4 of 9 standardsLevel 4
  2. Investigations and Incident ResponseQualifi Ltd · covers 3 of 9 standardsLevel 3
  3. Carrying out Information Security Incident Management activitiesPearson Education Ltd · covers 2 of 9 standardsLevel 3
  4. Performing Computer System Security Assessments for Engineering SoftwareETC Awards Limited · covers 1 of 9 standardsLevel 3
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

The rising capability

Zavmo analysis

What's rising in its place

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

Prompt Engineering for Security Investigations

Generative AI models are getting better at summarising logs, drafting incident reports, and even suggesting investigation steps. Analysts who can 'talk' to these AIs effectively will be far more productive.

  • Context Windows & Token Limits
  • Effective Prompting Techniques
  • Output Validation & Hallucination Detection
  • Integrating AI into Workflows

Cloud Security Automation & Scripting

Everything's moving to the cloud, and manual security checks just don't scale. Knowing how to automate security tasks in cloud environments will be crucial for efficiency and consistency.

  • Infrastructure as Code (IaC) Security
  • Cloud Native Security Tools
  • Basic Cloud APIs & SDKs
  • Serverless Functions for Security

What you’ll use

Skills this role draws on

Technical

  • Incident Response Lifecycle (PICERL)
  • Vulnerability Management Process
  • Network Security Fundamentals
  • Operating System Security (Windows/Linux)
  • Cloud Security Concepts (AWS/Azure/GCP)

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Junior Security Analyst

    1-2 years

    Skills to master

    • Basic alert monitoring, log review, understanding security fundamentals, following clear playbooks, documenting findings accurately.

    You're ready to move on when

    • Consistently handles routine alerts without supervision.
    • Demonstrates a solid grasp of basic security concepts.
    • Proactively seeks out learning opportunities.
    • Reliably completes assigned tasks and documentation.
  2. 2

    IT Support / Network Engineer with Security Focus

    2-3 years

    Skills to master

    • Deep understanding of network protocols, firewall rules, system administration, troubleshooting connectivity issues, and an interest in security principles.

    You're ready to move on when

    • Has taken on security-related tasks in their previous role (e.g., firewall rule reviews, access control management).
    • Holds a security-specific certification (e.g., CompTIA Security+).
    • Can articulate how IT infrastructure choices impact security.
    • Shows a clear drive to specialise in cybersecurity.
  3. 3

    Graduate Cyber Security Programme

    1-2 years (post-degree)

    Skills to master

    • Foundational security knowledge, exposure to various security domains (GRC, SOC, AppSec), project-based learning, structured mentorship.

    You're ready to move on when

    • Successfully completed all rotations or projects within a structured graduate programme.
    • Demonstrates a broad understanding of the cybersecurity landscape.
    • Has a clear interest in a hands-on technical security role.
    • Received positive feedback from mentors and project leads.

11Where this role leads

The long view:Your journey in cybersecurity is a continuous adventure. This role is a crucial step, giving you the hands-on experience and foundational knowledge to build a truly impactful career. We're excited to see where you'll take it.

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 Security Analyst / Engineer is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

Where it leads

Roles this leads to

The record names a next step, but the catalogue has no page for it yet:

  • Senior Security Engineer
  • Security Consultant (Internal or External)

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:

Incident Response, Investigations and ForensicsLevel 4

Applied to your work in Security Analyst / Engineer

This unit aims to equip learners with an understanding of incident response as a business function, including the operation of Computer Emergency Response Teams (CERTs) and aligned task forces for business continuity, disaster recovery, and crisis management. Learners will also understand how major computer incidents are formally investigated, including evidence gathering and analysis, and the relevant legal and ethical considerations.

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 Security Analyst / Engineer

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

  • Mean Time to Acknowledge (MTTA) Critical AlertsHow quickly you spot and acknowledge a high-priority security alert.If a critical alert comes in at 10:00, you should have it acknowledged and be starting your investigation by 10:14 at the latest. We track this automatically in our SIEM.<15 minutes
  • Remediation SLA AdherenceThe percentage of assigned security tickets (vulnerabilities, incident follow-ups) that you close within the agreed service level agreement.If you're assigned 20 tickets this month, you'd need to close 19 of them on time. This includes patching requests, configuration changes, or incident clean-up tasks.95% of assigned tickets
  • Phishing Simulation Click Rate ReductionHelping to reduce the number of times users in your assigned business units click on simulated phishing emails.You might help identify repeat clickers, suggest targeted training, or work with the awareness team to improve messaging. If your business unit started at 10% click rate, we'd want to see it around 7.5% after 6 months.Reduce click rate by 50% over 12 months (e.g., from 10% to 5%)
  • False Positive Reduction for Custom RulesFor any detection rules you help create or fine-tune, ensuring they're actually catching real threats, not just generating noise.If you build a new SIEM correlation rule, and 10 alerts fire, we'd expect 9 of them to be genuine security events, not just benign activity. High false positives mean wasted time for the whole team.<10% false positive rate for rules you've worked on
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 Security Analyst / Engineer to Senior Security Engineer, and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Security Engineer→ your design
Where this takes you

Your journey in cybersecurity is a continuous adventure. This role is a crucial step, giving you the hands-on experience and foundational knowledge to build a truly impactful career. We're excited to see where you'll take it.

See Your Progress GrowIllustration
Security Analyst / Engineer
  • Incident Response Lifecycle (PICERL)
  • Vulnerability Management Process
  • Network Security Fundamentals
  • Operating System Security (Windows/Linux)
  • Cloud Security Concepts (AWS/Azure/GCP)
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

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

  1. Senior Security Engineer

    3-5 years in this role

    L3 (Senior)

    • Advanced SIEM/SOAR Engineering: Building custom correlation rules, developing SOAR playbooks.
    • Threat Hunting: Proactively searching for threats, not just reacting to alerts.
    • Security Architecture Principles: Designing security controls for new systems.

  2. Security Consultant (Internal or External)

    4-6 years in this role

    L3/L4 (Senior/Lead)

    • Risk Assessment Methodologies: Conducting formal risk assessments.
    • Security Audit & Compliance: Performing internal audits or preparing for external ones.
    • Security Solution Design: Proposing and designing security solutions for various business needs.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, security operations can be a bit of a grind. Too many alerts, too much manual digging. But what if you could cut through the noise, automate the tedious bits, and focus on the really interesting stuff? You can, with AI.

We're not talking about robots taking over your job. We're talking about smart tools that help you do your job better, faster, and with less burnout. For a Security Analyst / Engineer, this means turning thousands of alerts into a handful of actionable insights, freeing you up for proactive threat hunting and deeper investigations. Here's how AI is already making a difference:

Automated Alert Triage & Investigation

Imagine AI sifting through all your SIEM and EDR alerts, automatically enriching them with context from threat intel and internal asset data. It'll dismiss 80% of the false positives, leaving you with a much smaller, higher-fidelity queue of actual incidents. This means less time wasted on benign events and more time on real threats.

AI-Powered Risk Context

You'll use AI to quickly understand the business impact of a technical vulnerability. Instead of just seeing 'critical CVE', AI can help you understand 'This vulnerability affects a customer-facing system and could lead to a £500K loss if exploited.' This helps you prioritise your remediation efforts like a pro.

Automated Compliance Evidence Gathering

During an audit, the manual task of gathering evidence for ISO 27001 or SOC 2 controls is a nightmare. AI tools can continuously scan cloud configurations and system settings, automatically collecting and mapping evidence. This drastically cuts down on the soul-crushing admin work, letting you focus on actual security, not paperwork.

Generative AI for Incident Summaries

After an incident, you need to write a clear, concise summary. Feed your raw incident notes, timelines, and remediation steps into a secure, internal generative AI model. Ask it to 'Draft a summary for the IT Director focusing on impact and resolution.' You'll get a solid first draft in seconds, saving you valuable time.

Common questions

Common questions

How do you become a Security Analyst / Engineer?

Common routes in include Junior Security Analyst (1-2 years), IT Support / Network Engineer with Security Focus (2-3 years) and Graduate Cyber Security Programme (1-2 years (post-degree)). Times vary with prior experience.

Where can a Security Analyst / Engineer progress to?

This role can lead on to Senior Security Engineer (3-5 years in this role) and Security Consultant (Internal or External) (4-6 years in this role), depending on the skills you build.

What level is a Security Analyst / Engineer in the UK?

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

What new skills matter most for a Security Analyst / Engineer?

Increasingly, Prompt Engineering for Security Investigations and Cloud Security Automation & Scripting. 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 Security Analyst / Engineer, works on the job you actually do, and keeps going at your pace rather than a timetable's.

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

Your path, personalised

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

This route runs to 9 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 Security Analyst / Engineer: personal to you, and it still counts. The first steps are free.

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

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

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

15Where to go from here

Other roles at Level 3

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

Other roles in Technical roles

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

If you leave this industry

The skills you'll gain here are highly transferable across industries. Every company needs strong security, so you'll find opportunities in finance, tech, healthcare, government – pretty much anywhere. Your expertise will be in high demand.

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.