Cloud Architect
Whiteboards, design reviews, cost models, less keyboard time than you think.
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.
- Domain
- Cloud
- Entry
- £42–62k
- Senior
- £105–145k
- 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
- 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
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.
Tradeoffs at a glance
Hover any chip for the calibrated meaning. Ratings are directional, not absolute.
Promotion ceiling
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.
Where this leads
- Enterprise Architect
- Staff Platform
- Pre-sales
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
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
- Cloud Security Engineer
Cloud-native IAM, workload security, policy-as-code. Entered from cloud, not from SOC.
What this is based on
Practitioner judgement. External evidence review pending.
Last reviewed: not yet reviewed · UK market
Where this fits
Roles connect to pathways, certs and other roles. Use one to test the next.
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- Cloud Security Engineer
Cloud-native IAM, workload security, policy-as-code. Entered from cloud, not from SOC.
- Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
The 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.
A route shows what is possible. A Career Verdict makes the call.
Career Verdict
Helpdesk → Security Architect
- 01The callA clear judgement on whether your route is realistic, and under what conditions.
- 02Where the route breaksThe most likely point to stall, and why it happens in practice.
- 03What to do nextSpecific priorities for the next 6–24 months, and what to drop.
Career Verdict
- The callA single written judgement on whether the route is realistic for you.
- Plateaus and failure modesThe flat years and the specific ways this route tends to stall.
- Where you standThe strongest and weakest parts of your current position, named.
- Salary realityWhat this route actually pays, set against what you've been told it pays.
Usually within minutes of payment. Kept 24 months, then deleted. Deletion on request at any time.
Built on POST's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.