UK

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

Cloud Migration Assistant

As a Cloud Migration Specialist, you orchestrate the seamless transition of systems into the cloud, ensuring they thrive in their new digital home.

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.

See how AI is changing this job, and get the full read by email.

Start my free AI Fluency module

As a Cloud Migration Assistant, a good place to start on Prompt Engineering for Technical Tasks is Using and Checking AI Tools in Daily Work, a free Future Fluency module at Level 3. You'd practise using everyday AI tools on real tasks from your own week, and checking what they produce before you use it.

Free to start, no card.

Keep this job description

Where should we send it?

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

Your employer, or 'self-employed'

Leading a team? Try this with up to five of them for 14 days, free.

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

Also advertised as Cloud Migration Specialist · Mid-Level Cloud Engineer · Migration Delivery Engineer

Built on 43,079 real UK job descriptions we analysed · grounded in what real qualifications cover

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 5 of 11 standards
Cambridge OCR Level 3 Cambridge Technical Certificate in IT Cambridge OCR · Level 3 · covers 3 of 11 standards
Cambridge OCR Level 3 Cambridge Technical Introductory Diploma in IT Cambridge OCR · Level 3 · covers 3 of 11 standards
Cambridge OCR Level 3 Cambridge Technical Extended Diploma in IT Cambridge OCR · Level 3 · covers 2 of 11 standards
Cambridge OCR Level 3 Cambridge Technical Subsidiary Diploma in IT Cambridge OCR · Level 3 · covers 2 of 11 standards
Pearson BTEC Level 5 Higher National Diploma in Cloud Computing Pearson Education Ltd · Level 5 · covers 8 of 11 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 5 Higher National Diploma in Cloud Computing
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
Your Plan Illustration

Built for Cloud Migration Assistant

2 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 8 of 11 standards Level 5
  2. Cloud computing in business Cambridge OCR · covers 3 of 11 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 Migration Assistant?

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

How the AI economy is changing work like this

A broad read on this kind of work, not an analysis of this job on its own. Roles that share a pattern get the same answer here.

Fading: AI does more of this

AI is taking over the repetitive aspects of pre-migration checks and basic troubleshooting, freeing you to focus on more complex challenges.

→
Rising: worth more because of AI

Your ability to design and implement modular IaC templates becomes more valuable, as AI handles routine tasks, allowing you to focus on strategic improvements.

The new skill this role is being asked for

  • Prompt Engineering for Technical Tasks
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 Migration Assistant plan as you set up, starting with the free AI Fluency module. No card.

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

Ready to pay? Subscribe for £70 a month

Keep this read. One email with what AI is changing in this job, the new skills it asks for and where to start free. Nothing else follows unless you confirm your address.

3What this role really is

We see you

You sometimes wonder if AI will outpace your technical skills, yet you know the human touch in problem-solving and strategic thinking is irreplaceable. The thrill of overcoming complex migration challenges keeps you motivated.

A Cloud Migration Assistant moves applications and data from on-premises systems into the cloud. The work involves moving specific servers and services, and making sure they land safely and work as expected. It is a hands-on technical role that follows established processes, with room to work out the best way to handle routine problems. It involves fitting individual pieces of a larger migration into place.

4A day in the life

Not a job advert. A real day, built from what this role actually holds.

08:45
You start your day with a quick check-in with the Senior Engineer to discuss the day's migration tasks and any potential roadblocks.
11:00
You're deep into executing a pre-migration assessment, meticulously checking dependencies and preparing for the cutover.
14:30
A migration cutover is underway, and you troubleshoot a network configuration issue that pops up, coordinating with the network engineer to resolve it swiftly.
16:15
You update the migration runbook with new insights from today's tasks, ensuring future migrations benefit from what you've learned.

5What you'd actually use

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

AWS Management Console / Azure Portal / GCP Console Intermediate

Launching instances from templates, configuring basic network settings (VPCs, subnets, security groups), monitoring resource health, checking logs for migrated workloads.

Migration & Discovery Tools (e.g., AWS MGN, Azure Migrate, Zerto) Intermediate

Deploying discovery agents, configuring replication jobs, monitoring migration progress, initiating cutovers for individual servers, troubleshooting replication issues.

Terraform (HCL) / CloudFormation Basic

Reading existing templates to understand infrastructure definitions, making minor modifications (e.g., changing an instance type or tag) under guidance, identifying resources defined in code.

Ansible Playbooks / PowerShell Scripts Intermediate

Executing pre-written playbooks or scripts for post-migration configuration, validation checks, and software installations. Debugging basic script failures.

Jira / Confluence Intermediate

Updating migration status in Jira tickets, creating and managing your own tasks, following and updating detailed runbooks in Confluence, contributing to post-mortem documents.

6What 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
Migration Approach for a Single Server Follows pre-defined 'Lift and Shift' or 'Replatform' instructions from a senior engineer. Escalates any deviation. Can independently choose between 'Lift and Shift' or a simple 'Replatform' for a non-complex server, based on application requirements and existing patterns. Consults manager for anything unusual. Designs the migration strategy (including Rehost, Replatform, Refactor) for entire multi-tier applications, considering business drivers and technical complexity.
Troubleshooting a Replication Failure Collects logs and escalates immediately to a senior engineer, providing all gathered information. Independently diagnoses common replication issues (e.g., network connectivity, agent status) using logs and standard tools. Proposes a fix to manager before implementing if it impacts production. Resolves complex, intermittent replication failures, potentially involving cloud provider support. Defines new troubleshooting runbooks for the team.
Updating Migration Runbooks Makes minor edits to existing runbooks under direct supervision, following templates. Proactively updates sections of existing runbooks based on lessons learned from migrations, ensuring clarity and accuracy. Shares updates with the team for review. Authors entire new runbooks for complex application migrations. Establishes standards and templates for runbook creation across the team.
Cloud Resource Sizing Deploys instances based on pre-defined specifications from a senior engineer. Proposes initial 'right-sizing' adjustments for migrated VMs based on observed usage patterns. Seeks approval from manager before implementing changes that affect performance or cost significantly. Defines the right-sizing methodology and tools for entire application portfolios. Works with application owners to forecast future resource needs.

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

Server Migration Throughput
The number of individual servers or virtual machines you successfully migrate from on-premises to the cloud each month.
Target · 15-20 servers per month (for non-complex moves)

In April, you successfully moved 18 non-critical application servers, all within their allocated cutover windows.

Runbook Execution Error Rate
The percentage of times you encounter an error or deviation when following a pre-defined migration runbook.
Target · <1% error rate on checklist tasks

Out of 50 runbook steps executed during a recent migration, only one required a manual override or correction, resulting in a 0.5% error rate.

Issue Resolution Time (L1/L2)
How quickly you diagnose and resolve routine technical issues that crop up during or immediately after a migration.
Target · Resolve L1/L2 validation issues within 4 hours

A user reported a connectivity issue to a newly migrated application; you identified a missing security group rule and fixed it within 3 hours, restoring service.

Post-Migration Cost Optimisation
Identifying and implementing initial right-sizing opportunities for migrated instances, ensuring we're not overspending.
Target · Identify and implement 5-10% cost reduction on initial migrated workloads within 2 weeks post-cutover.

After migrating a development server, you noticed it was provisioned with 8 vCPUs but only using 2. You proposed and implemented a resize, saving £50/month.

Runbook Quality & Updates
How well you update and improve existing migration runbooks based on your experiences, making them clearer and more robust for future use.
  • Your manager and peers regularly use your updated runbook sections. You proactively suggest improvements to existing processes. Your updates are clear, concise, and prevent others from making the same mistakes you encountered.
Proactive Issue Identification
Your ability to spot potential problems before they become major incidents, especially during discovery or pre-migration checks.
  • You flag a potential network bottleneck during a discovery scan that wasn't immediately obvious. You notice an application dependency that wasn't documented and bring it to the team's attention before cutover.
Clear Communication During Incidents
How effectively you communicate status, findings, and next steps when a migration encounters an unexpected problem.
  • During a failed replication, you provide concise, factual updates to your manager and the application owner, explaining what happened and what you're doing about it, without panicking. Your emails are easy to understand, even for non-technical people.
Team Collaboration & Support
Your willingness to help out other team members, share knowledge, and contribute positively to the team's overall working environment.
  • You offer to help a junior engineer with a tricky script. You share a useful troubleshooting tip you discovered in the team's chat. You're generally seen as a helpful and approachable colleague.

8Would you like it

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

What people enjoy
Seeing Tangible Progress

You get a real kick out of seeing a server successfully shut down on-premises and then boot up perfectly in the cloud. You like ticking off tasks on a checklist and seeing the migration dashboard numbers go up.

Successfully migrating a tricky database server over a weekend, then seeing the application owners confirm everything is working Monday morning.

Solving Technical Puzzles

When a migration tool throws a cryptic error, you see it as a challenge to be conquered, not a reason to give up. You enjoy digging into logs, researching solutions, and figuring out why something isn't working.

Spending an hour debugging a network connectivity issue between the old data centre and the cloud, finally pinpointing the exact firewall rule that needed changing.

Contributing to a Bigger Picture

You understand that your individual server migrations contribute to the company's larger goal of moving to the cloud, saving money, and enabling new digital services. You feel like you're part of something important.

Knowing that the 20 servers you migrated this month directly helped us hit our target for decommissioning an entire rack of old hardware.

What frustrates people
  • Inaccurate Discovery Data: Spending days trying to reconcile why the 'authoritative' CMDB lists a server that was decommissioned two years ago, or has completely wrong dependency information.
  • The 'Pocket Veto' from App Owners: Dealing with application owners who are resistant to change and 'forget' to provide critical information or sign-offs until the last possible second, jeopardising the wave schedule.
  • Last-Minute Change Freezes: Having a meticulously planned weekend cutover for a 50-server application cancelled on Friday afternoon because of an unrelated production issue in another department.
  • Performance Complaint Witch-Hunts: Proving that the 'slowness' a user is reporting is due to WAN latency or a poorly written application query, not the cloud infrastructure you just migrated them to.
  • Hard-Coded Everything: Discovering during final testing that a critical legacy application has IP addresses hard-coded into its source code, turning a simple migration into a major refactoring project.
What this role does not give you
  • A completely predictable, routine day-to-day. Expect curveballs.
  • Full autonomy on strategic decisions – you'll be executing the strategy, not defining it.
  • A quiet, uninterrupted environment. You'll be interacting with lots of people and troubleshooting issues.
  • The chance to build brand-new, greenfield cloud architectures from scratch (mostly brownfield migrations here).

9Who you work with

Your reliable delivery of migration tasks directly contributes to our overall cloud adoption goals. Get it right, and we hit our targets for decommissioning old hardware and reducing operational costs. Get it wrong, and we face project delays, budget overruns, and potentially serious business disruption. You're a vital cog in the machine, making sure the wheels keep turning smoothly as we shift to the cloud.

Inside the business
  • Your direct manager (Senior Cloud Migration Engineer)
  • Other Cloud Migration Specialists (your peers)
  • Application Owners (the people who actually use the apps you're moving)
  • Infrastructure Operations Teams (who manage the old and new environments)
  • Network Engineers (for connectivity between old and new)
  • Security Teams (to make sure everything's locked down)
Outside the business
  • Cloud Platform Support (AWS, Azure, GCP)
  • Migration Tool Vendors (if we're using third-party software)

10What you need before you start

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

  • 2-5 years of experience in an IT operations, infrastructure support, or junior cloud engineering role.
  • Demonstrable experience with at least one major cloud platform (AWS, Azure, or GCP), even if it's just basic console usage.
  • Hands-on experience with virtualisation technologies like VMware or Hyper-V.
  • A good understanding of networking concepts (TCP/IP, DNS, firewalls).
  • Experience with basic scripting (PowerShell, Bash, or Python) for automation tasks.

11What to practise next

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

Advanced Cloud Cost Optimisation Techniques

Simply 'right-sizing' isn't enough anymore. You'll need to understand more nuanced cost-saving strategies like reserved instances, spot instances, and serverless cost models to truly optimise migrated workloads.

Reserved Instances & Savings Plans · Serverless Cost Models · Cost Explorer & Billing Reports · Tagging & Cost Allocation

  • This week: Read up on the basics of Reserved Instances for your primary cloud platform.
  • This month: Use your cloud provider's cost explorer to identify the top 3 biggest spenders in your migrated workloads.
  • Month 2: Propose a cost-saving change (e.g., resizing, changing instance family) for one of those workloads, with a clear ROI.
  • Month 3: Get familiar with tagging best practices and start applying them to new resources you migrate.

Quick win: Look at any development or test environments you've migrated – are they running 24/7? Could they be shut down overnight or on weekends to save money? Propose that change.

Expanded IaC (Infrastructure as Code) Proficiency

As we move more to the cloud, everything needs to be defined in code. You'll move beyond just reading and making minor edits to actually writing more complex modules and integrating them into CI/CD pipelines.

Terraform Modules · State Management · CI/CD for IaC · Policy as Code (e.g., Sentinel, OPA)

  • This week: Take an online course on advanced Terraform concepts, focusing on modules.
  • This month: Try to write a simple Terraform module for a common resource (e.g., a security group or a storage bucket).
  • Month 2: Work with a senior engineer to understand how our IaC is integrated into our CI/CD pipeline.
  • Month 3: Propose a way to automate a manual cloud setup task using Terraform.

Quick win: Find a small, repeatable manual task you do in the cloud console (like creating a specific type of user or a simple network resource) and try to write a basic Terraform script to automate it.

12Staying current once you are in

What people here do to keep up
  • Regularly engage with cloud provider documentation (AWS Docs, Azure Docs, GCP Docs) – it's your bible for new services and troubleshooting.
  • Follow key cloud migration blogs and industry experts on LinkedIn or Twitter to stay current with best practices.
  • Participate in online forums or communities (e.g., Stack Overflow, Reddit's r/cloud) to learn from others' challenges and share your own insights.
  • Attend virtual webinars or local meetups focused on cloud migration or specific cloud platforms.
  • Dedicate a few hours each week to hands-on experimentation in a personal cloud account, trying out new services or migration patterns.

13The 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 Technical Tasks

AI is already changing how we write code, troubleshoot, and document. Analysts who can effectively 'talk' to large language models (LLMs) to generate accurate scripts, debug assistance, or even draft runbook sections will be significantly more productive.

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

14What you’ll use

What you’ll use

Skills this role draws on

Technical

  • The 6 R's of Migration Strategy
  • Application Dependency Mapping (Basic)
  • Cutover Planning & Execution (Following Runbooks)
  • Cloud Adoption Framework (CAF) Principles
  • Basic Cloud Cost Awareness

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

    IT Support Engineer / Helpdesk Specialist

    2-3 years

    Skills to master

    • Troubleshooting, customer service, basic networking, understanding of IT systems, ticket management.

    You're ready to move on when

    • You're consistently resolving complex L1/L2 issues without escalation.
    • You've started automating repetitive tasks with scripts.
    • You're actively learning about cloud technologies in your spare time.
  2. 2

    Junior Systems Administrator / Infrastructure Engineer

    2-4 years

    Skills to master

    • Server administration (Linux/Windows), virtualisation (VMware/Hyper-V), scripting, basic network configuration, patch management.

    You're ready to move on when

    • You're managing a small fleet of servers independently.
    • You've deployed or managed applications in a virtualised environment.
    • You're comfortable with command-line interfaces and basic automation.
  3. 3

    Junior Cloud Engineer / Cloud Operations Analyst

    1-2 years

    Skills to master

    • Basic cloud service provisioning, cloud monitoring, managing cloud resources, cloud security fundamentals.

    You're ready to move on when

    • You've provisioned resources (VMs, storage) in a major cloud platform.
    • You understand basic cloud networking and IAM concepts.
    • You're familiar with cloud provider consoles and APIs.

16How people get here · where they go next

Came from
IT Infrastructure Engineer / Systems Administrator
2-4 years
You mastered the intricacies of on-premise infrastructure, equipping yourself with the skills to tackle cloud migrations.
You are here
Cloud Migration Assistant
Mid-Level (2-5 years)
A Cloud Migration Assistant moves applications and data from on-premises systems into the cloud. The work involves moving specific servers and services, and making sure they land safely and work as expected. It is a hands-on technical role that follows established processes, with room to work out the best way to handle routine problems. It involves fitting individual pieces of a larger migration into place.
Goes to
Senior Cloud Migration Specialist (L3)
3-5 years
This role involves leading 'waves' of migrations, mentoring others, and tackling complex technical challenges.

The long view: This work can lead to Lead Cloud Migration Architect, designing migration strategy for whole waves of applications, or Principal Cloud Strategist, managing dependencies and business cases across a wider programme.

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 Migration Assistant 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 Migration Assistant.

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

Applied to your work in Cloud Migration Assistant

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.

The Coach Last time, we talked about refining your pre-migration assessments. How did your latest assessment go?

You It went well, but I encountered some unexpected dependencies.

The Coach Great learning opportunity! Let's explore how you can document these dependencies to improve the accuracy of future assessments.

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.

A year from now

A year from now, you confidently lead migration projects, leveraging AI-enhanced tools to refine strategies and mentor emerging specialists.

See Your Progress Grow Illustration
Cloud Migration Assistant
  • The 6 R's of Migration Strategy
  • Application Dependency Mapping (Basic)
  • Cutover Planning & Execution (Following Runbooks)
  • Cloud Adoption Framework (CAF) Principles
  • Basic Cloud Cost Awareness
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 Migration Assistant is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior Cloud Migration Engineer (L3)

    2-3 years from this role

    You'll move from owning individual servers to owning entire multi-tier applications. You'll write runbooks from scratch, develop automation, and mentor junior team members.

    • End-to-end Application Migration Design Architecting the migration strategy (including Replatforming and Refactoring) for complex applications.
    • Advanced Automation Scripting Writing robust Ansible playbooks or Python scripts for pre/post-migration tasks and validation.
    • Database Migration Expertise Handling database migrations using tools like AWS DMS or Azure DMS.
    • Cloud Security Best Practices Implementing advanced security controls for migrated applications.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, cloud migration can be a repetitive beast. Imagine having a smart assistant that handles the grunt work, leaving you to focus on the interesting technical challenges. That's exactly what AI can do for you in this role.

We're not talking about AI doing your job for you, but rather giving you superpowers. You'll use AI tools to automate the tedious bits, speed up analysis, and even draft communications, making your day-to-day work much more efficient and less frustrating. Think of it as having an extra pair of hands, but with a super-fast brain.

Runbook & Script Generation

Use AI assistants to whip up boilerplate runbook sections or generate PowerShell/Bash scripts for common pre/post-migration checks. Need a script to check service status or validate disk space? AI can give you a solid first draft in seconds, saving you from starting from scratch every time.

Dependency Analysis Accelerator

Feed the raw outputs from your discovery tools (like network traffic logs or inventory reports) into an AI model. It can then help you identify and visualise potential application dependencies, suggesting logical 'move groups' and flagging high-risk connections much faster than doing it manually.

Obscure Error Code Solver

Ever stared at a cryptic error code from a migration tool or a cloud provider API, wondering what on earth it means? Just paste it into an AI chat interface. It can instantly search forums, documentation, and knowledge bases to give you known issues and potential solutions, cutting down your troubleshooting time significantly.

Stakeholder Comms Assistant

Drafting those 'migration complete' emails or status updates for project managers can be a chore. Give AI the key data points, and it can generate clear, concise first drafts of stakeholder communications, freeing you up to focus on the technical details.

Common questions

Common questions

How do you become a Cloud Migration Assistant?

Common routes in include IT Support Engineer / Helpdesk Specialist (2-3 years), Junior Systems Administrator / Infrastructure Engineer (2-4 years) and Junior Cloud Engineer / Cloud Operations Analyst (1-2 years). Times vary with prior experience.

Where can a Cloud Migration Assistant progress to?

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

What new skills matter most for a Cloud Migration Assistant?

Increasingly, Prompt Engineering for Technical Tasks. 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 involved apply across industries, since most organisations are moving to the cloud. This includes financial services, retail, healthcare, public sector and tech. It can lead into broader Cloud Engineering, DevOps, or Cloud Security roles.

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 free AI Fluency module 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.