How to become a cloud engineer

A cloud engineer builds and runs the environments everything else sits on. The work splits between provisioning — networks, identity, compute, storage, all as code — and answering for cost, because cloud spend rises quietly and someone has to explain it. It overlaps DevOps heavily; the distinction, where one exists, is that the cloud engineer owns the platform and DevOps owns the path onto it.

Written by the JobStraight team · pay and hiring figures measured 2026-08-22 · page updated 2026-09-01

The realistic ways in

Which people each route suits, and what it honestly costs.

From system administration or IT infrastructure

The most common route. Networking, identity and storage all transfer; what is new is that infrastructure is now written and reviewed like code.

From software engineering

You can code and automate. The gap is networking and identity, which are the two areas that produce the most expensive mistakes.

From support or NOC work

Viable and slower. You have seen how things fail, which is genuinely valuable, and you build the platform knowledge deliberately.

The title you get hired into first

The titles this role is actually hired under:

  • Cloud Engineer
  • Cloud Support Engineer
  • Infrastructure Engineer
  • DevOps Engineer
  • Platform Engineer
  • Systems Engineer

102 live cloud engineer openings are on the site right now, refreshed on every build and linking to the employer's own posting.

What to learn, in order

Ordered by dependency, not by interest. Durations assume eight to ten hours a week and are an estimate, not a measurement.

  1. Networking and identity 6–8 weeks

    VPCs, subnets, routing, security groups, IAM. Nearly every serious cloud incident traces back to one of these two.

  2. One provider, properly 8–10 weeks

    Depth in AWS, Azure or GCP. Depth in one beats a certificate in each, and a certification here genuinely helps at the entry level.

  3. Infrastructure as code 6 weeks

    Terraform, and the discipline that the console is for looking rather than for changing.

  4. Cost and monitoring 4 weeks

    Tagging, budgets, alerts, right-sizing. The bill is a shared responsibility and being the person who reduced it is a career accelerant.

The one piece of work that changes the conversation

An environment defined entirely in code — network, identity, compute, storage — that someone else can stand up from your repository without asking you anything. Add the monthly cost estimate. Cost awareness is rare in junior candidates and it is the thing that makes a hiring manager remember an application.

What it pays, measured

From salary figures on live cloud engineer postings, not a survey. Half sit between the outer two columns.

Salary figures on cloud engineer postings, by market
MarketLower quarter belowMidpointUpper quarter abovePostings with a figure
India ₹9.1L ₹15L ₹23L 363
the UK £52k at least £70k at least £70k 768
the US $131k at least $140k at least $140k 3,925

How much of this the source estimated rather than read off a posting: India 0%, the UK 29%, the US 70%. The full note, and what it means for each market, is on the salary page below.

The full distribution for each market, the twelve-month movement and the employers posting most of these roles are on the cloud engineer salary page.

What the role is screened on

Our skill study covers six role groups and cloud engineer is not one of them. So this list is editorial — what the interviews test — not a count of postings.

    Who is hiring, right now

    Ranked by how often each appears in cloud engineer advertisements, measured 2026-08-22. Advertisement frequency, not vacancy count — which is why there is an order here and no number.

    • India: Oracle, H & R Johnson, GENPACT, HP Textile Mill, Sikka Infrastructure Private
    • the UK: Amazon, Google, JPMorgan Chase, IBM, Capgemini
    • the US: Oracle, Deloitte, Accenture, Amazon, Google

    Appearing high can mean growth, turnover, an agency posting for a client, or a bulk feed repeating one advertisement. Research, not a recommendation.

    What gets people rejected

    Not being able to explain a bill. Cloud interviews increasingly include a cost scenario, and an engineer with no view on what their design spends is a liability the finance team has already met before.

    Whatever you write, make sure the resume that gets you the interview can survive the questions it invites — everything on it is fair game, and the numbers attract the most scrutiny. Check it against a real posting before you send it.

    How long it really takes

    Nine to eighteen months from IT or system administration. Faster with a certification plus a real environment you built, slower from a non-technical start.

    Who finds this harder than expected. People who dislike being on call. The platform failing is everyone's problem and you are the one who gets paged for it.

    Common questions

    How long does it take to become a cloud engineer?

    Nine to eighteen months from IT or system administration. Faster with a certification plus a real environment you built, slower from a non-technical start.

    Do you need a degree to become a cloud engineer?

    Not usually a specific one — From system administration or IT infrastructure; From software engineering; From support or NOC work are all routes people take here. Where a degree matters it is a filter at large employers rather than something the work needs.

    What should be in a cloud engineer portfolio?

    An environment defined entirely in code — network, identity, compute, storage — that someone else can stand up from your repository without asking you anything. Add the monthly cost estimate. Cost awareness is rare in junior candidates and it is the thing that makes a hiring manager remember an application.

    What gets people rejected for cloud engineer roles?

    Not being able to explain a bill. Cloud interviews increasingly include a cost scenario, and an engineer with no view on what their design spends is a liability the finance team has already met before.

    Which job title should you apply to first?

    Not cloud engineer necessarily — Cloud Engineer, Cloud Support Engineer, Infrastructure Engineer, DevOps Engineer are where people are actually hired in.

    Is cloud engineer the right role for you?

    It is harder than the internet implies for one group in particular: people who dislike being on call. The platform failing is everyone's problem and you are the one who gets paged for it.

    Where to go next

    Keep reading

    How to find a remote job in 2026 (without wasting months)
    A practical guide to landing a remote role: where the genuine listings are, how to spot hybrid-in-disguise…
    How to write a resume with no experience (that isn't padded)
    How to build a credible first resume: what counts as experience, the section order that works, and turning…
    How to become a data engineer
    How to become a data engineer: the realistic ways in, what to learn in order, and what the role pays from…
    How to become a devops engineer
    How to become a devops engineer: the realistic ways in, what to learn in order, and what the role pays from…