Skip to main content
TechWaymark

Classroom mode. Nothing is saved to this machine and no personal detail is asked for.

Leave classroom mode
A cloud engineer at a standing desk reviews infrastructure code and a cloud console
Cloud Used in TechWaymark Education

Cloud Engineer

Builds and runs the infrastructure that now lives in someone else's data centre, and pays for it by the hour.

Could I move into this role? See a day in the role

Role at a glance

The shape of the job

Typical UK pay£36–45k entry · £58–72k senior
ExperienceEarly to mid career
Work patternHybrid or remote is common
Technical depthDeep in one provider, broad across services
People contactModerate, mostly with engineers
HoursOffice hours, some on-call

Pay bands are TechWaymark practitioner estimates for UK roles, reviewed 2026-09, not survey data. They vary by region, sector and employer.

What the Cloud Engineer role involves

  • You build networks, servers, storage and permissions in AWS, Azure or Google Cloud, usually as code rather than by hand.
  • You keep things running: patching, scaling, backups, and working out why a service is slow or unreachable.
  • You spend more time on identity and networking than people expect. Most cloud problems are one of the two.
  • You watch cost. A forgotten test environment can quietly spend more than your salary.
Read TechWaymark's full role verdict and reasoning
TechWaymark verdict

A practical engineering route combining cloud deployment with access, reliability and cost decisions.

Domain
Cloud
Entry
£36–45k
Senior
£58–72k
Pick this if
  • You have systems or networking experience you want to apply to cloud workloads
  • You enjoy IAM puzzles and reading other people's Terraform without crying
  • You're happy working in tickets, PRs and reviews, less keyboard-on, more thinking
  • You'll keep building lab projects, not just collecting certifications
Skip this if
  • You haven't touched a console yet, do the rep work first or you'll bomb the interview
  • The advertised incident or on-call responsibilities do not suit you
  • You want examination success treated as proof of all the role's operating responsibilities

What "doing well" looks like in the seat

  • You can debug an IAM problem without resorting to wildcard policies
  • Your PRs get merged with minor feedback, not full rewrites
  • You're the one who notices the cost spike before finance does
  • You can explain your design choices to a stakeholder who doesn't care about the tech
The bit you're probably underestimating

Deploying a service is only part of the remit. Determine who owns incidents, spending, infrastructure changes and recovery, and how much of that ownership is supervised.

A laptop showing a terminal and code editor beside a notebook
Most changes start as code in a repository, not clicks in a console.

Illustrative

A day in the role

  1. Stand-up. A team needs a new environment for testing by Friday
  2. Write the Terraform for it, reusing the team's existing modules
  3. An app can't reach its database. Trace security groups, routes and DNS until you find it
  4. Review a colleague's pull request that widens a storage permission more than it needs to
  5. Cost report shows a spike. Find three oversized instances left over from a load test
  6. Update the runbook for restoring a database snapshot, and test it

An example day. Roles and organisations vary, and no two days match.

Day to day

What you'll work with

Systems

AWS, Azure or Google CloudVirtual networks and load balancersManaged databases and storageIdentity and access management

Tools

Terraform or BicepGit and pull requestsCI/CD pipelinesMonitoring (e.g. CloudWatch, Azure Monitor)

Concepts

Least privilegeAvailability zones and regionsInfrastructure as codeCost allocation

Hiring reality

What employers actually expect

Must understand

  • Solid networking: subnets, routing, DNS, firewalls
  • Comfortable in Linux and a scripting language
  • Can read and change infrastructure code safely
  • Treats permissions as something to justify, not grant

Commonly expected

  • Deep familiarity with one provider
  • Terraform or the provider's own tooling
  • Some container knowledge
  • An associate-level cert (AWS SAA, AZ-104)

Sets you apart

  • Prior on-premises infrastructure experience
  • Cost work you can quantify
  • A public repository of real infrastructure code
  • Having handled an outage and written it up

What this role isn't

It isn't clicking through a console, and it isn't a shortcut past infrastructure basics. A cert without networking and Linux underneath tends to show in the first technical interview.

How the role changes with seniority

1Junior

Makes changes to existing code and environments with review. Handles tickets and routine operations.

2Experienced

Designs environments for a team, owns reliability for a set of services, reviews others' changes.

3Senior / lead

Sets standards and patterns across teams, makes cost and resilience calls, mentors.

An engineering team reviews a rising cost chart on a wall screen
Somebody always asks why the bill went up. Often it's you who has to answer.

Nobody puts this in the advert

The hard parts

The title means six jobs

Some roles are pure operations, some are nearly software engineering. Easy to land in the wrong one.

Invisible blast radius

One permission or route change can break things far from where you made it.

Constant change

Providers ship new services and deprecate old ones every month. Keeping up is part of the job.

The junior gap

Few true entry-level roles exist. Most people arrive from support, sysadmin or networking.

More than one way in

How people actually get into it

From sysadmin or infrastructure

The most natural route. You already know what the cloud is abstracting.

From IT support via a junior cloud role

Possible with a cert, a lab and visible infrastructure code.

Apprenticeship

Cloud and infrastructure apprenticeships exist, often at larger firms and consultancies.

From software development

Developers who drift into owning their own infrastructure often move across.

Evidence employers value

"AWS certified"

A repository where you built a small environment in Terraform, with a README explaining your choices

"Understands cloud security"

A before-and-after of a permission you narrowed and how you tested nothing broke

"Cost conscious"

A short note on a bill you reduced: what was running, what you changed, what it saved

Projects that prove it

Small pieces of work you can do on your own, and what each one shows an employer.

Build a small environment as code

2 weekends

Use Terraform to create a network, one virtual machine and a storage bucket in a free tier account. Destroy it and rebuild it from scratch to prove the code is the source of truth.

What it demonstrates

Infrastructure as codeCloud networking basicsRepeatable builds

Break it and fix it

1-2 evenings

Deliberately misconfigure a route or firewall rule so your server becomes unreachable. Diagnose it from logs and tools only, then write up how you found it.

What it demonstrates

Structured troubleshootingNetwork path reasoningClear write-ups

Set a budget and a cost alarm

1 evening

Add tagging, a monthly budget and an alert to your account. Leave something running, watch the alert fire, and note what you'd tell a manager.

What it demonstrates

Cost awarenessMonitoring and alertingExplaining spend

Your next hops

Where Cloud Engineer can take you

Junior Cloud EngineerCloud EngineerCloud Architect

Other common branches

DevOps EngineerPlatform EngineerCloud Security Engineer

There is no single ladder. See the routes on the Atlas.

See the pathway to Cloud Architect

Worth the effort?

Certifications that complement it

AWS CloudOps Associate

Relevant to the route into this role.

See certification verdict AWS SAA

The most commonly listed cloud cert on UK adverts. Broad coverage of how AWS services fit together.

See certification verdict AWS SysOps (superseded)

Relevant to the route into this role.

See certification verdict Azure Administrator (AZ-104)

The practical Azure administrator exam. Common where organisations are Microsoft-heavy, which many UK employers are.

See certification verdict Google Cloud Associate

The associate-level Google Cloud cert. Fewer UK roles, but less competition for them.

See certification verdict

Interview reality

Questions you may be asked

Loading questions…

Practise with model answers in My Waymark

For educators

Used in TechWaymark Education

These modules use this page as investigation material in the classroom.

  • 1
    Technology is not one career

    An example of work that mainly builds systems

Where this fits

Roles connect to pathways, certs and other roles. Use one to test the next.

Roles to consider

Could you realistically get here from where you are?

The Guided Route compares your background with this role and shows the honest route, hop by hop.

Try the free Guided Route About the Career Verdict

Last reviewed 2026-09. Photographs are illustrative.