UK

United Kingdom · Technology and data · Mid-Level (2-5 years)

Cloud Engineer

Here is the whole job, in plain words. What it is, 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.

Start my Cloud Engineer plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

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

Also advertised as Mid-Level Cloud Infrastructure Engineer · AWS/Azure/GCP Platform Engineer · DevOps Engineer (Cloud Focus)

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

Pearson BTEC Level 4 Higher National Certificate in Cloud Computing Pearson Education Ltd · Level 4 · covers 6 of 12 standards
City & Guilds Level 3 Diploma in ICT Systems and Principles for IT Professionals City & Guilds Limited · Level 3 · covers 3 of 12 standards
City & Guilds Level 3 Certificate in ICT Systems and Principles City & Guilds Limited · Level 3 · covers 3 of 12 standards
City & Guilds Level 3 Diploma in ICT Systems Support City & Guilds Limited · Level 3 · covers 2 of 12 standards
Cambridge OCR Level 3 Cambridge Technical Certificate in IT Cambridge OCR · Level 3 · covers 2 of 12 standards
Cambridge OCR Level 3 Cambridge Technical Introductory Diploma in IT Cambridge OCR · Level 3 · covers 2 of 12 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Deploying and Operating in the Cloud Project (Pearson set) Pearson BTEC Level 4 Higher National Certificate in Cloud Computing
Implementing and maintaining Cloud technologies and infrastructure City & Guilds Level 3 Diploma in ICT Systems and Principles for IT Professionals
Cloud computing in business Cambridge OCR Level 3 Cambridge Technical Certificate in IT

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
Automation Fluency building AI into how work runs
Sustainability Fluency building care for people and planet into the work
Systems Fluency seeing the whole picture
Start my Cloud Engineer plan, free
Your Plan Illustration

Built for Cloud Engineer

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

  1. Deploying and Operating in the Cloud Project (Pearson set) Pearson Education Ltd · covers 6 of 12 standards Level 4
  2. Implementing and maintaining Cloud technologies and infrastructure City & Guilds Limited · covers 3 of 12 standards Level 3
  3. Cloud computing in business Cambridge OCR · covers 2 of 12 standards Level 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.

2AI and this work

Will AI change your work as a Cloud Engineer?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • Prompt Engineering for Cloud Operations
  • Advanced Observability & AIOps
Why each one is rising

The future skills this job leans on

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

What happens when you start

Next, a free account. We build your Cloud Engineer plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Cloud Engineer plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A Cloud Engineer builds and maintains the cloud infrastructure that keeps applications running. This work takes architectural designs and turns them into working systems, mostly using code. It means making sure everything is stable, secure and performs well, and owning projects from start to finish.

4What you'd actually use

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

AWS (EC2, S3, IAM, VPC, RDS, Lambda, EKS) Intermediate

You'll be deploying and managing virtual machines, storage, user permissions, networking, databases, serverless functions, and Kubernetes clusters in AWS.

Azure (VMs, Blob Storage, Azure AD, VNet, Azure SQL, AKS) Intermediate

You'll be managing virtual machines, object storage, identity and access, virtual networks, managed databases, and Kubernetes clusters in Azure.

GCP (Compute Engine, Cloud Storage, IAM, VPC, Cloud SQL, GKE) Intermediate

You'll be working with virtual machines, object storage, identity and access, virtual networks, managed databases, and Kubernetes clusters in GCP.

Terraform (HCL) Advanced

This is your primary tool for defining, provisioning, and managing all our cloud infrastructure across all providers. You'll be writing, reviewing, and applying Terraform code daily.

Docker & Kubernetes (kubectl, Helm) Intermediate

You'll be containerising applications, building Docker images, deploying applications to Kubernetes clusters, writing Helm charts, and troubleshooting containerised workloads.

GitLab CI / GitHub Actions Advanced

You'll be designing, building, and maintaining our automated CI/CD pipelines for both infrastructure and application deployments. This means writing YAML configurations for workflows.

Datadog / Prometheus (Monitoring & Alerting) Intermediate

You'll be setting up custom dashboards, configuring alerts, performing log queries, and using APM to monitor the health and performance of our cloud services and applications.

Bash / Python (Scripting) Intermediate

You'll be writing automation scripts for repetitive tasks, interacting with cloud SDKs (Boto3, Azure SDK), and potentially building small CLI tools for other engineers.

5What 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 in Where you are nowThe step above
Infrastructure Deployment (Routine) Executes `terraform apply` under direct supervision, all changes pre-approved. Independently deploys routine infrastructure changes (e.g., new EC2 instance, S3 bucket) using approved IaC modules. Consults senior engineer for complex changes. Approves and deploys complex infrastructure changes, including new architectural patterns. Defines deployment best practices for the team.
Troubleshooting & Incident Response Follows runbooks to diagnose and resolve L1 issues. Escalates anything beyond basic steps. Independently diagnoses and resolves L2 incidents using monitoring tools and logs. Proposes solutions for novel issues, consulting senior engineers. Leads incident response for critical issues. Defines root cause analysis processes and implements preventative measures.
Tool/Technology Selection Uses existing tools as directed. No input on new tool selection. Can propose new tools or services for specific problems, but requires approval from senior engineers or manager. Focuses on existing tech stack. Evaluates and recommends new core technologies or services for adoption by the team. Leads proof-of-concept efforts.
Budgetary Spend (Project-level) No direct budgetary authority. All resource provisioning approved by supervisor. Aware of project costs and seeks cost-effective solutions. Can provision resources within established cost guardrails (e.g., up to £500 per month for a specific project) with manager awareness. Escalates anything above this. Manages project budgets up to £5K-£10K. Makes recommendations for larger cost optimisations or investments.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Deployment Success Rate
The percentage of your infrastructure deployments (e.g., Terraform `apply` operations) that complete without manual intervention or rollback.
Target · >98% success rate for routine deployments

You deployed 50 Terraform changes last month; 49 went through perfectly, one needed a quick fix post-deployment. That's a 98% success rate.

Ticket Resolution Time (SLA Adherence)
How quickly you resolve assigned infrastructure-related tickets from development teams or internal monitoring alerts, staying within agreed Service Level Agreements.
Target · Resolve 80% of assigned tickets within SLA

You had 20 tickets this week, 16 were closed within their 4-hour SLA, 4 took a bit longer due to complexity. You're hitting 80%.

Cloud Cost Optimisation Contributions
Identifying and implementing specific changes that reduce our cloud spend without negatively impacting performance or reliability.
Target · Identify and implement 1-2 cost-saving recommendations per quarter, saving roughly £1K-£5K annually.

You spotted an idle EC2 instance in a dev environment and terminated it, saving £100/month. Or you reconfigured a storage tier, saving £200/month.

Infrastructure as Code (IaC) Coverage
The proportion of new infrastructure you deploy that is fully defined and managed through IaC (e.g., Terraform) from day one.
Target · 100% for all new infrastructure deployments

Every new database, load balancer, or server you set up this quarter was done via Terraform, no 'Click-Ops' involved.

Documentation Quality & Completeness
How well you document the infrastructure you build, including runbooks, architecture diagrams, and configuration details, making it easy for others to understand and support.
  • Other engineers can follow your runbooks to resolve issues. New team members can quickly understand your project's setup. Your documentation is regularly updated and accurate.
Proactive Issue Identification
Spotting potential problems in the infrastructure before they become critical incidents, like an upcoming certificate expiry or a resource nearing its capacity limit.
  • You flag potential issues in stand-ups. You raise JIRA tickets for preventative maintenance. You're often the first to notice a trend in monitoring data that suggests a future problem.
Collaboration & Knowledge Sharing
How effectively you work with development teams and other engineers, sharing your cloud knowledge and helping them understand infrastructure constraints and best practices.
  • Developers regularly ask you for advice. You contribute to team knowledge base articles. You actively participate in code reviews, offering constructive feedback.
Security Best Practice Adherence
Consistently applying security best practices in your infrastructure designs and configurations, like least privilege IAM policies or secure network configurations.
  • Security reviews of your work pass with minimal findings. Your configurations rarely get flagged by automated security scanning tools. You can explain the security rationale behind your choices.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Building Robust Systems

You get a real kick out of seeing your Terraform code successfully deploy a complex, resilient system. You enjoy the process of designing, building, and then watching it run smoothly.

Successfully deploying a new Kubernetes cluster with automated scaling and self-healing capabilities, then seeing it handle peak traffic without a hitch.

Solving Technical Puzzles

You love digging into a tricky problem, whether it's a mysterious application error or an obscure networking issue, and systematically working through it until you find the solution.

Spending an afternoon debugging why a particular service can't talk to a database, only to discover a subtle misconfiguration in a security group. The 'aha!' moment is your reward.

Continuous Learning & Mastery

The constant evolution of cloud technology excites you. You're always keen to learn a new service, master a new IaC pattern, or understand a different cloud provider's approach.

Taking the initiative to learn a new feature in AWS Lambda or Azure Functions, then proposing a way to use it to simplify an existing process.

What frustrates people
  • The 'Click-Ops' Inheritance: Inheriting a production environment that was built manually in the console, forcing you to spend months reverse-engineering it into Terraform just to achieve a stable baseline.
  • Developer Secret Sprawl: Constantly chasing down development teams who hardcode API keys, passwords, and tokens directly in their code or config files instead of using proper secret management.
  • The 3 AM Page for a Cloud Provider Outage: Being woken up by alerts for a major service outage (like S3 or Azure AD) that you have no control over, but still have to manage communication for.
  • The Cost Optimization Battle: Proving to management that a more expensive, managed service (like RDS or EKS) is actually cheaper in the long run due to lower operational overhead.
  • Security vs. Velocity: Navigating the constant tension between the security team wanting to lock everything down and developers needing access to external packages and APIs.
What this role does not give you
  • A perfectly clean, greenfield environment—you'll deal with legacy systems.
  • Complete autonomy from day one—you'll be working within established patterns and designs.
  • A purely strategic role—this is very hands-on, building and maintaining.
  • Immunity from 'toil'—you'll still have some repetitive operational tasks, though we aim to automate them.

8Who you work with

This role directly impacts the reliability, scalability, and security of our core applications. A well-executed cloud engineering function means our products are always available to customers and our development teams can innovate quickly without infrastructure getting in the way. You're essentially building the stable ground our entire digital business stands on.

Inside the business
  • Software Development Teams (your primary 'customers')
  • Senior Cloud Engineers and Architects (for guidance and design input)
  • Security Team (to ensure compliance and best practices)
  • Product Managers (to understand application requirements and priorities)
  • Technical Operations Team (for handovers and incident response)
Outside the business
  • Cloud Providers (AWS, Azure, GCP support)
  • Key Software Vendors (e.g., Datadog, GitLab)

9What 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 dedicated Cloud Engineer, DevOps Engineer, or Infrastructure Engineer role.
  • Demonstrable experience building and managing infrastructure in at least one major cloud provider (AWS, Azure, or GCP).
  • Solid experience with Infrastructure as Code (IaC) tools, primarily Terraform, including writing modules and managing state.
  • Proven ability to write automation scripts in Bash or Python.
  • Experience with containerisation technologies like Docker and orchestrators like Kubernetes (or managed services like EKS/AKS/GKE).
  • A good grasp of CI/CD pipeline concepts and practical experience with tools like GitLab CI or GitHub Actions.
  • Strong understanding of networking fundamentals (TCP/IP, DNS, VPCs/VNets) and cloud security best practices.

10What to practise next

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

Multi-Cloud & Hybrid Cloud Patterns

While we might primarily use one cloud, understanding how to operate across multiple providers (or even on-premise) is becoming crucial for resilience, cost optimisation, and avoiding vendor lock-in. You'll need to think beyond a single cloud's ecosystem.

Cloud Agnostic IaC (e.g., Crossplane) · Network Interconnectivity (Direct Connect, ExpressRoute, Cloud Interconnect) · Data Replication & Synchronisation across Clouds · Identity Federation (SSO across clouds)

  • This week: Read up on the networking options for connecting AWS, Azure, and GCP. How do they differ?
  • This month: Experiment with a tool like Crossplane or Pulumi to deploy a simple resource to two different clouds.
  • Month 2: Research common multi-cloud deployment patterns (e.g., active-passive, active-active, disaster recovery).
  • Month 3: Present a short overview to the team on the pros and cons of a specific multi-cloud strategy.

Quick win: Set up a free tier account in a cloud provider you're less familiar with and deploy a basic VM using Terraform. Just get comfortable with the console and core services.

Advanced Kubernetes & Service Mesh

Kubernetes is becoming the de facto standard for container orchestration, but simply deploying pods isn't enough. You'll need to understand how to build truly resilient, observable, and secure microservice platforms, which means diving into advanced Kubernetes features and service mesh technologies.

Custom Resource Definitions (CRDs) & Operators · Network Policies & Ingress Controllers · Service Mesh (Istio, Linkerd) · GitOps with ArgoCD/Flux

  • This week: Read the Kubernetes documentation on Network Policies and Ingress Controllers.
  • This month: Deploy a simple application to Kubernetes and then implement a basic service mesh (e.g., Linkerd) to observe its traffic.
  • Month 2: Experiment with writing a custom Helm chart for a more complex application.
  • Month 3: Explore ArgoCD or Flux and try to set up a GitOps pipeline for a test application.

Quick win: If you're not already, start using `kubectl` daily. Try to debug a failing pod or service using its built-in commands. Deploy a simple Helm chart from a public repository.

11Staying current once you are in

What people here do to keep up
  • Actively participate in online cloud communities, forums, or local meetups to stay current and share knowledge.
  • Dedicate time each week to exploring new cloud services or features, perhaps through personal projects or sandbox environments.
  • Attend relevant webinars, workshops, or online courses to deepen your expertise in specific areas like Kubernetes security or FinOps.
  • Contribute to open-source projects, especially those related to cloud infrastructure or automation, to hone your coding and collaboration skills.
  • Seek out mentorship from senior engineers within our team or through external networks.

12The rising capability

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 Cloud Operations

AI assistants are getting smarter, fast. Competitors are already using tools like GitHub Copilot or specialised LLMs to generate boilerplate IaC, debug code, and even draft incident reports in minutes. Engineers who master this will be significantly more productive.

  • Context Windows & Token Limits
  • Temperature Settings
  • Output Validation & Hallucination Detection
  • Prompt Chaining

Advanced Observability & AIOps

As our cloud environments grow more complex, manually sifting through dashboards and logs becomes impossible. AIOps tools are becoming essential for automatically detecting anomalies, predicting issues, and even suggesting root causes before a human engineer even sees an alert. This shifts your role from reactive monitoring to proactive system health management.

  • Service Level Objectives (SLOs) & Indicators (SLIs)
  • Distributed Tracing
  • Log Aggregation & Analysis
  • Predictive Analytics for Infrastructure

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Infrastructure as Code (IaC) Principles
  • Cloud Security & Governance
  • High Availability & Disaster Recovery (HA/DR)
  • FinOps & Cloud Cost Management
  • CI/CD & GitOps Strategy

14The pathway

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 Cloud Engineer / Associate Cloud Engineer

    2-3 years

    Skills to master

    • Mastering the basics of one cloud provider, understanding core IaC concepts (reading/modifying Terraform), executing runbooks, basic scripting, and effective troubleshooting of L1 issues.

    You're ready to move on when

    • Can independently deploy simple resources using IaC.
    • Consistently resolves routine tickets within SLA.
    • Actively contributes to team documentation.
    • Demonstrates a strong desire to learn and take on more complex tasks.
  2. 2

    System Administrator / Infrastructure Engineer (Cloud Transition)

    3-4 years (with 1-2 years focused on cloud)

    Skills to master

    • Translating on-premise infrastructure knowledge to cloud equivalents, gaining hands-on experience with cloud-native services, learning IaC from scratch, and adapting to a DevOps/SRE mindset.

    You're ready to move on when

    • Has successfully migrated at least one on-premise application to the cloud.
    • Can demonstrate strong scripting skills and a basic understanding of CI/CD.
    • Understands the differences and advantages of cloud-native architectures.
    • Holds at least one associate-level cloud certification.
  3. 3

    Software Developer (with Infrastructure Interest)

    2-4 years (with 1-2 years focused on infrastructure)

    Skills to master

    • Deepening understanding of cloud infrastructure beyond application deployment, learning IaC, networking, and security best practices. Developing strong troubleshooting skills for distributed systems.

    You're ready to move on when

    • Has designed and deployed their own application infrastructure in the cloud.
    • Contributes to infrastructure-as-code in their current role.
    • Understands the operational challenges of running applications in production.
    • Demonstrates a passion for infrastructure and platform engineering.

15Where this role leads

The long view: This work can lead into Site Reliability Engineering, Cloud Architecture, Security Engineering or Developer Relations.

16Pay and demand

Pay & demand

Typical pay £60,288 a year Source: ONS Annual Survey of Hours and Earnings, 2025 (provisional), under the Open Government Licence v3.0

The figure is the median for full-time employees in the ONS occupation this job title codes to (IT business analysts, architects and systems designers), from the April 2025 survey, about six months old when published, as ASHE always is. It is that occupation's middle, not this role's. Half earn more.

The ten Future Fluencies

Zavmo analysis

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

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

The highlighted ones are the Fluencies your role leans on hardest, from how Cloud Engineer is actually changing.

Where it leads

Roles this leads to

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Deploying and Operating in the Cloud Project (Pearson set), worked against Cloud Engineer.

Deploying and Operating in the Cloud Project (Pearson set) Level 4

Applied to your work in Cloud Engineer

This unit aims to enable learners to discuss cloud architectural principles, develop a cloud-based prototype, and test it against business case requirements. Learners will gain practical experience in deploying and operating in the cloud, and will be able to discuss the value gained from developing a cloud-based solution to support sustainable organisational performance.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 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.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Cloud Engineer plan, free
See Your Progress Grow Illustration
Cloud Engineer
  • Infrastructure as Code (IaC) Principles
  • Cloud Security & Governance
  • High Availability & Disaster Recovery (HA/DR)
  • FinOps & Cloud Cost Management
  • CI/CD & GitOps Strategy
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.

17The 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

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

  1. Senior Cloud Engineer

    3-5 years in this role

    From L2 to L3

    • Designing components of large-scale, resilient cloud systems.
    • Deep expertise in a specific cloud domain (e.g., Kubernetes, serverless, networking).
    • Architecting advanced CI/CD pipelines and GitOps workflows.
    • Leading incident response and driving post-mortem improvements.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, cloud engineering can be a demanding job. There's endless documentation, repetitive code, and constant troubleshooting. But what if you could offload some of that 'toil' to AI? We're not talking about replacing you; we're talking about giving you a seriously powerful co-pilot.

Imagine spending less time on boilerplate code and more time on high-impact architecture and complex problem-solving. Our AI Productivity Hub is designed specifically for Cloud Engineers like you, integrating smart tools directly into your workflow to cut down on the grunt work. Here's how it'll actually help you day-to-day:

IaC Code Generation

Use AI assistants, like a beefed-up GitHub Copilot, to churn out boilerplate Terraform, CloudFormation, or ARM templates from simple English prompts. Need an S3 bucket with specific encryption and versioning? Just ask. This isn't just about speed; it's about reducing typos and ensuring consistent patterns.

Anomaly Detection & Root Cause Analysis

Our observability tools, powered by AI, don't just alert you to problems; they often suggest the likely culprit. Think Datadog's Watchdog, but smarter. This means less time sifting through logs in a panic during an outage and more time fixing the actual issue.

Cloud Service Research Assistant

Drowning in AWS, Azure, or GCP documentation? Use AI chatbots to summarise lengthy whitepapers, compare features between different cloud services, or generate specific code snippets for using an SDK. It's like having a hyper-efficient research assistant at your fingertips.

Incident Report & Runbook Authoring

After an incident, you can feed technical notes, Slack conversations, and metrics into an AI model. It'll then spit out a structured first draft of a post-mortem report or a step-by-step runbook for future mitigation. This saves hours of tedious writing when you'd rather be doing literally anything else.

Common questions

Common questions

How do you become a Cloud Engineer?

Common routes in include Junior Cloud Engineer / Associate Cloud Engineer (2-3 years), System Administrator / Infrastructure Engineer (Cloud Transition) (3-4 years (with 1-2 years focused on cloud)) and Software Developer (with Infrastructure Interest) (2-4 years (with 1-2 years focused on infrastructure)). Times vary with prior experience.

Where can a Cloud Engineer progress to?

This role can lead on to Senior Cloud Engineer (3-5 years in this role), depending on the skills you build.

What new skills matter most for a Cloud Engineer?

Increasingly, Prompt Engineering for Cloud Operations and Advanced Observability & AIOps. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

18Where 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.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills built as a Cloud Engineer transfer across sectors. You could move into Site Reliability Engineering. You could specialise in a cloud provider as a Cloud Architect. You could move into Security Engineering, or into Developer Relations helping other engineers build on cloud platforms. Demand for these skills spans almost every industry.

This role profile is © 2026 Growth 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. Start my Cloud Engineer plan, free What happens next: a free account, then we build your plan as you set up. 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.