Cloud Architect
Decides how systems should be built in the cloud, and owns the consequences for cost, resilience and security.
Role at a glance
The shape of the job
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 Architect role involves
- You design how applications and infrastructure should be built in the cloud: networks, identity, data, resilience.
- You make and document decisions, such as managed service or self-run, one region or two, and explain the tradeoffs.
- You review what engineering teams propose and steer them away from designs that will hurt later.
- You translate between engineers and leadership on cost, risk and timelines.
Read TechWaymark's full role verdict and reasoning
Architecture work that connects cloud choices to business constraints and delivery evidence.
- Domain
- Cloud
- Entry
- Not mapped
- Senior
- Not mapped
- 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
Design authority varies. Check who funds the implementation, who accepts residual risk and how architects learn whether their designs work in operation.
Illustrative
A day in the role
- Architecture review: a team wants a second region. Ask what failure they're actually protecting against
- Write a decision record choosing a managed database over running one on VMs
- Cost forecast for next year with the finance lead
- Workshop with security on identity design for a new partner integration
- Review a migration plan and flag three dependencies nobody has mapped
- Update the landing zone standards after a service change from the provider
An example day. Roles and organisations vary, and no two days match.
Day to day
What you'll work with
Systems
Tools
Concepts
Hiring reality
What employers actually expect
Must understand
- Hands-on cloud engineering experience
- Can explain a tradeoff to non-technical people
- Writes clear decision records
- Understands cost, security and resilience together
Commonly expected
- Years in cloud or infrastructure engineering
- A professional-level cert (AWS SAP, AZ-305)
- Migration experience
- Some networking and identity depth
Sets you apart
- A migration you designed with measurable results
- Cost savings you drove with numbers
- Decisions you'd now reverse and why
- Consulting or client-facing experience
What this role isn't
It isn't drawing diagrams, and it isn't a promotion you earn just by being the best engineer. It's accountability for decisions you often won't implement yourself.
How the role changes with seniority
Designs within a team or project, supported by senior architects, still hands-on.
Owns designs for a domain or programme, reviews teams' proposals, advises leadership.
Sets cloud strategy and standards across the organisation, owns major platform decisions.
Nobody puts this in the advert
The hard parts
Influence without authority
You rarely manage the teams building your designs. You have to persuade them.
Losing hands-on time
Skills fade when you stop building. Staying credible takes deliberate effort.
Owning the bill
Design choices show up in the cost report for years, long after you've moved on.
Few entry points
There's no junior version. You arrive after years of engineering.
More than one way in
How people actually get into it
From cloud engineering
The standard route, typically after several years owning designs within a team.
From infrastructure
Senior infrastructure engineers who build strong cloud experience.
From consulting
Cloud consultants who have designed across many clients.
From solutions architecture
Moving from pre-sales or project design into owning an organisation's cloud estate.
Evidence employers value
"Designed cloud solutions"
A decision record: the options, why you chose one, and what you'd revisit
"Cost optimisation"
A saving with numbers and the tradeoff you accepted to get it
"Stakeholder management"
A design you changed after challenge from another team, and what you learned
Projects that prove it
Small pieces of work you can do on your own, and what each one shows an employer.
Write three decision records
2-3 eveningsFor a fictional small business moving to cloud, write short records for three choices: database, region strategy and identity. Include what would make you change each.
What it demonstrates
Design a landing zone
2-3 eveningsSketch account or subscription structure, networking, identity and logging for that business. Explain it in one page a director could follow.
What it demonstrates
Cost two designs
1-2 eveningsUse the provider's pricing calculator to cost a single-region and a two-region version of the same app. Write what the extra money buys and whether it's worth it.
What it demonstrates
Your next hops
Where Cloud Architect can take you
Other common branches
There is no single ladder. See the routes on the Atlas.
Worth the effort?
Certifications that complement it
Interview reality
Questions you may be asked
Loading questions…
Practise with model answers in My WaymarkFor educators
Used in TechWaymark Education
These modules use this page as investigation material in the classroom.
- 1Technology is not one career
An example of senior work that mainly designs how systems are built
Where this fits
Roles connect to pathways, certs and other roles. Use one to test the next.
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.
Last reviewed 2026-09. Photographs are illustrative.