Skip to main content
POST ATLAS
RoleCloud

Cloud Engineer

Provision, glue services, fight IAM, own one cloud account end-to-end.

The verdict

The single best risk-adjusted move from sysadmin or networking right now, provided you've already shipped something in a real AWS or Azure account.

Pick this if
  • You've got two-plus years of Linux or networking and want a salary jump
  • 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
  • You want the title without the on-call, mid-sized orgs almost always pair them
  • You think AWS SAA on its own opens the door, in 2026 it doesn't
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

The interview market has hardened. Two years ago a SAA plus a half-decent CV got you a phone screen. Now you're competing with people who've migrated production workloads, owned a P1 outage in cloud, and can talk through a landing zone from memory. If your only cloud time is in your own sandbox account, you'll plateau at interview stage for six months before you work out what's missing. Build something that mattered to someone other than you.

Tradeoffs at a glance

Hover any chip for the calibrated meaning. Ratings are directional, not absolute.

Promotion ceiling

Strong. Senior cloud / staff platform is one of the best-paid IC tracks.

Who actually gets in
  • +Sysadmin
  • +Network engineer
  • +Backend dev
Common misconceptions
  • −That AWS SAA gets you the job, projects with real IaC do.

Where this leads

  • DevOps / Platform
  • Cloud Security
  • Solutions Architect

Certifications people pair with this

Listed because the graph connects them to this role, not because you need all of them. Most practitioners pick one or two.

Pathways that pass through here

Where this fits

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

Pathways that touch this
Roles to consider
Certifications in scope
Perspectives that bear on this

The serious next step

You've read about the role. The harder question is whether it's the right one for you.

A Career Verdict is the written, practitioner-authored call on your specific route into and out of this role. Six primitives, same format every time.

Plateau zone
The flat year nobody warns you about, named and timed.
Reality vs Fantasy
Your actual five-year curve against the one you've been sold.
What to sit and what to skip
Each cert on your list: useful, optional, or skip, with reasons.
The call
A single written judgment on whether your plan holds up.
Tradeoff spectrum
What you're giving up for what you're choosing, plotted.
Decisive factors
The two or three things that will actually make or break this.
See what a Career Verdict looks like£25 · one verdict, yours to keep

Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. Framework is human-authored; the verdict applies it to your inputs.

All roles