Infrastructure Engineer to Cloud Engineer
Step-by-step guide to changing career from Infrastructure Engineer to Cloud Engineer — transferable skills, skill gaps, salary comparison, timeline, and practical advice for the UK market.
Can you go from Infrastructure Engineer to Cloud Engineer?
Moving from Infrastructure Engineer to Cloud Engineer is a realistic career change that many professionals make successfully. Both roles sit within technology, which means you already understand the sector's language, pace, and priorities — that contextual knowledge is genuinely valuable and shouldn't be underestimated.
The core of this transition rests on 1 skill that directly transfer (ci/cd pipeline design). Your experience with ci/cd pipeline design as a Infrastructure Engineer gives you a genuine head start over candidates entering Cloud Engineer roles from scratch. The gaps that do exist are fillable within 6-12 months, and most can be addressed through self-directed learning, short courses, or early-career projects in the new role.
This guide covers exactly what transfers, the specific gaps you'll need to close (AWS (EC2, S3, Lambda, RDS, networking), Terraform or CloudFormation, Kubernetes and Docker among them), the realistic salary impact, and a step-by-step plan for making the move from Infrastructure Engineer to Cloud Engineer in the UK market.
Why Infrastructure Engineers make this change
Infrastructure Engineers frequently reach a ceiling — whether that's salary, progression, variety, or day-to-day satisfaction — that makes them look seriously at what else their skills could unlock. Cloud Engineer work — which typically involves designing and deploying cloud infrastructure. cloud engineers spend significant time architecting systems in aws, azure, or gcp — deciding on compute (ec2, lambda), storage (s3, databases), networking, and security. decisions made here affect cost, performance, and reliability for the entire organisation. — offers a meaningfully different daily rhythm that appeals to Infrastructure Engineers looking for faster-paced, project-driven work with visible outputs. The transition isn't usually driven by a single factor — it's a combination of wanting more from your career and recognising that your Infrastructure Engineer skills open doors you hadn't previously considered.
Practically, Infrastructure Engineers are drawn to Cloud Engineer because the day-to-day work is meaningfully different while still drawing on strengths they've already developed. The mid-career earning potential for Cloud Engineers (£50,000–£75,000) compared to Infrastructure Engineer rates (£48,000–£70,000) is part of the equation — though salary shouldn't be the only reason to make a change. The strongest candidates are those genuinely interested in working with AWS (EC2, S3, Lambda, RDS, networking) and Terraform or CloudFormation and building expertise in technology.
How realistic is this career change?
This transition is realistic but requires deliberate effort. You won't walk into a Cloud Engineer role on the strength of your Infrastructure Engineer experience alone — there are specific skills and knowledge areas you'll need to build. That said, the 1 skill that transfers directly gives you a solid starting point. Expect the full transition to take 6-12 months, with the first few months focused on upskilling and the latter part on landing and settling into the new role.
The biggest risk isn't ability — it's patience. Career changers who treat this as a six-month sprint often get discouraged. Those who commit to a structured plan and accept that the first role might not be their dream position tend to succeed.
Skills that transfer directly
CI/CD pipeline design
As a Infrastructure Engineer
As a Infrastructure Engineer, you use CI/CD pipeline design in day-to-day development and problem-solving
As a Cloud Engineer
Cloud Engineers rely on CI/CD pipeline design for building and maintaining systems — your existing proficiency transfers directly
Analytical thinking
As a Infrastructure Engineer
Infrastructure Engineers develop strong analytical habits — breaking problems into components, evaluating evidence, and forming conclusions. This transfers directly to technical problem-solving
As a Cloud Engineer
Cloud Engineers apply analytical thinking to AWS (EC2, S3, Lambda, RDS, networking) and Terraform or CloudFormation, making your structured approach a genuine asset
Structured communication
As a Infrastructure Engineer
Explaining complex technology concepts to non-specialists is a skill you've practised repeatedly as a Infrastructure Engineer
As a Cloud Engineer
Cloud Engineers need to communicate technical decisions to business stakeholders, product teams, and clients — your clarity translates well
Project coordination
As a Infrastructure Engineer
Whether formally or informally, Infrastructure Engineers manage timelines, dependencies, and deliverables — that's project management in practice
As a Cloud Engineer
Most Cloud Engineer roles involve coordinating work across multiple stakeholders, so your organisational skills transfer well
Skills you'll need to build
AWS (EC2, S3, Lambda, RDS, networking)
Cloud Engineers need AWS (EC2, S3, Lambda, RDS, networking) for core aspects of the role. This isn't something you can bluff in interviews — you'll need demonstrable competence, even at a foundational level.
Terraform or CloudFormation
Cloud Engineers need Terraform or CloudFormation for core aspects of the role. This isn't something you can bluff in interviews — you'll need demonstrable competence, even at a foundational level.
Kubernetes and Docker
Cloud Engineers need Kubernetes and Docker for core aspects of the role. This isn't something you can bluff in interviews — you'll need demonstrable competence, even at a foundational level.
Infrastructure-as-Code practices
Cloud Engineers need Infrastructure-as-Code practices for core aspects of the role. This isn't something you can bluff in interviews — you'll need demonstrable competence, even at a foundational level.
Networking (VPCs, subnets, routing)
Cloud Engineers need Networking (VPCs, subnets, routing) for core aspects of the role. This isn't something you can bluff in interviews — you'll need demonstrable competence, even at a foundational level.
Salary comparison
Infrastructure Engineer
Cloud Engineer
When transitioning from a mid-career Infrastructure Engineer position (£48,000–£70,000) to an entry-level Cloud Engineer role (£32,000–£44,000), expect a short-term pay adjustment. This is normal for career changes — you're trading seniority in one field for growth potential in another. The gap is typically most noticeable in the first 12-18 months.
The long-term picture is more encouraging. Experienced Cloud Engineers earn £80,000–£130,000+, and career changers who commit to the new path typically reach mid-career rates (£50,000–£75,000) within 2-4 years. Your Infrastructure Engineer background can actually accelerate this — employers value the broader perspective and professional maturity that career changers bring.
Day-to-day comparison
Your current day as a Infrastructure Engineer
As a Infrastructure Engineer, your typical day involves writing and reviewing infrastructure code. modern infrastructure engineers code in terraform, cloudformation, or ansible, treating infrastructure like software. this includes peer review, testing, and version control just like application code., and designing systems for scale and reliability. infrastructure engineers design cloud architectures that handle traffic spikes, recover from failures gracefully, and cost efficiently. this involves understanding trade-offs between consistency, availability, and cost.. The rhythm is shaped by technology priorities — sprint cycles, standups, and iterative delivery.
Your future day as a Cloud Engineer
As a Cloud Engineer, the day looks different: designing and deploying cloud infrastructure. cloud engineers spend significant time architecting systems in aws, azure, or gcp — deciding on compute (ec2, lambda), storage (s3, databases), networking, and security. decisions made here affect cost, performance, and reliability for the entire organisation., and infrastructure-as-code work with terraform or cloudformation. rather than manually clicking through cloud consoles, cloud engineers write code that defines infrastructure. this enables reproducibility, version control, and rapid scaling. most of the day involves writing, testing, and reviewing iac code.. The emphasis shifts to technical delivery, code reviews, and system reliability.
How to frame your background in interviews
The interview is where career changers either win or lose. You'll face two recurring questions: "Why are you leaving Infrastructure Engineer?" and "Why Cloud Engineer?". Frame your answer around what you're moving toward, not what you're escaping. "I discovered that the aspects of my Infrastructure Engineer work I enjoy most — AWS (EC2, S3, Lambda, RDS, networking), Terraform or CloudFormation, Kubernetes and Docker — are exactly what Cloud Engineers do full-time" is stronger than "I was bored" or "I wanted better pay". Cloud Engineer interviewers specifically look for systems thinking at scale and cost awareness, so build your narrative around demonstrating these.
Prepare 4-5 examples from your Infrastructure Engineer career that directly demonstrate Cloud Engineer competencies. Your shared experience with ci/cd pipeline design gives you concrete examples — use them. The best career-changer examples show transferable impact: "In my Infrastructure Engineer role, I [did something] which resulted in [measurable outcome] — and this is directly comparable to how Cloud Engineers approach [similar challenge]." Don't apologise for your background or oversell it. Be matter-of-fact about what you bring and honest about what you're still building.
Frequently asked questions
Can I realistically move from Infrastructure Engineer to Cloud Engineer?
Yes — this is a moderate transition that is achievable with focused preparation. The key is identifying which of your Infrastructure Engineer skills transfer directly and addressing the specific gaps. Expect the transition to take 6-12 months from starting preparation to landing a role.
Will I need to take a pay cut to change from Infrastructure Engineer to Cloud Engineer?
In most cases, yes — at least initially. You're entering a new field where your seniority doesn't directly transfer, so your starting salary will likely be below what you currently earn as a Infrastructure Engineer. However, career changers typically reach market rate within 2-4 years, and many find the long-term earning trajectory in Cloud Engineer roles (reaching £80,000–£130,000+ at senior level) compensates for the short-term dip.
What qualifications do I need to become a Cloud Engineer?
Formal qualifications aren't always essential for Cloud Engineer roles, especially for career changers who can demonstrate relevant skills through other means. The most effective approach is targeted upskilling: identify the 2-3 most critical gaps from job descriptions and address those first. Practical evidence (projects, portfolios, voluntary work) often carries more weight than certificates alone.
How do I explain my career change in interviews?
Frame it as a deliberate, positive move — not an escape. "I discovered that the parts of my Infrastructure Engineer work I'm best at and most energised by are exactly what Cloud Engineers do full-time" is a strong opening. Back this up with 3-4 specific examples showing how your Infrastructure Engineer achievements demonstrate Cloud Engineer competencies. Be direct about your motivations and honest about what you're still learning.
Should I retrain full-time or transition while working as a Infrastructure Engineer?
For most people, transitioning while employed is more sustainable — it maintains your income, avoids a CV gap, and lets you build skills gradually. Evening courses, weekend projects, and online learning can all be done alongside your current role. If you can, negotiate reduced hours or a four-day week in your Infrastructure Engineer role to create dedicated transition time.
How long does it take to go from Infrastructure Engineer to Cloud Engineer?
The typical timeline is 6-12 months from starting active preparation to landing a Cloud Engineer role. This includes skills development, CV repositioning, networking, and the application process. Some people move faster (especially for straightforward transitions), while others — particularly those requiring formal qualifications — may take longer. Don't optimise for speed; optimise for landing the right role.
What are the biggest challenges when moving from Infrastructure Engineer to Cloud Engineer?
The main challenges are bridging specific technical skill gaps, managing a potential short-term salary dip, and building credibility in a new field where you don't yet have a track record. The career changers who struggle most are those who underestimate the preparation needed or try to skip the skill-building phase. Those who succeed treat it as a structured project with clear milestones.
Are there companies that specifically hire Infrastructure Engineers for Cloud Engineer roles?
Some employers actively value career changers for Cloud Engineer positions — particularly those who appreciate the diverse perspective and professional maturity that Infrastructure Engineers bring. Since you're staying within technology, many employers in the sector will recognise the relevance of your background immediately. Recruitment agencies specialising in technology can also help identify employers who are open to career changers.
Other career changes from Infrastructure Engineer
Other routes into Cloud Engineer
Explore both roles
Ready to prepare for your Cloud Engineer interview?
Practise Cloud Engineer interview questions with instant feedback. Free to start, no card required.
Sign up free · No card needed · Free trial on all plans