Skip to main content
RoleCloud

Cloud Architect

Whiteboards, design reviews, cost models, less keyboard time than you think.

The verdict

A real seat at large orgs, a vanity title at small ones. Take it only when you've already shipped multiple production designs end-to-end.

Pick this if
  • You've owned at least two non-trivial cloud builds from blank slate to live
  • You enjoy stakeholder conversations as much as diagrams
  • You can write a decision record that someone will still understand in two years
  • You're patient with org politics, half of architecture is internal sales
Skip this if
  • You want to keep your hands deep in the console every day
  • You've never carried an outage that came from your own design choices
  • You think frameworks like TOGAF will do the thinking for you
What "doing well" looks like in the seat
  • Engineering teams ask for your reviews before procurement does
  • Your designs survive contact with the security and finance teams
  • You can pick the boring option and defend it without flinching
  • You're the one whose ADRs the next architect actually reads
The bit you're probably underestimating

Most cloud architect seats below FTSE-250 scale are slide decks and Visio diagrams with very little authority. You'll spend two years drawing target states nobody implements, then realise your hands have gone rusty. The good seats expect you to still write Terraform, still join incident calls and still own an outcome, not just a diagram. Ask in the interview when they last shipped one of the architect's designs to production. If they pause, walk.

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

Very high. Principal / distinguished architect is a real ladder.

Who actually gets in
  • +Senior cloud engineer
  • +Solutions architect
  • +Pre-sales SE
Common misconceptions
  • That it's a cert-driven role. Design intuition from real projects is the moat.
  • Enterprise Architect
  • Staff Platform
  • Pre-sales

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

Where this fits

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

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.

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.