Tech & Software

Cloud Architect Career Roadmap

Cloud architecture is systems thinking at planetary scale — designing infrastructure that must absorb load spikes, survive regional outages, comply with data regulations across jurisdictions, and cost less than it costs to maintain by hand. The prevailing orthodoxy says cloud is just rented servers. Cloud architects know better: done well, it's the difference between a startup that can serve ten million users on day two and one that can't survive its first viral moment.

Cloud Architect roadmap: the learning path in 5 steps, Cloud Fundamentals & Core Services, then Networking & Security Architecture, then Infrastructure as Code with Terraform, then Serverless, Containers & Microservices, then Architecture Patterns, Cost Optimisation & Certifications
The Cloud Architect roadmap at a glance: 5 steps, from Cloud Fundamentals & Core Services to Architecture Patterns, Cost Optimisation & Certifications.

Is this the right path for you?

Cloud architects come from senior engineering or DevOps/infrastructure roles — this is not an entry-level path. The typical trajectory runs through 5+ years of building and operating systems before the architect title makes sense. Solution architects at AWS and GCP are also a common pipeline, as are infrastructure leads who've built production systems at scale.

If you design for failure before you design for success — if your first instinct when reviewing a system diagram is 'what happens when this component goes down' rather than 'does this meet the requirements' — you're already thinking like an architect. The role rewards systems-level paranoia and the ability to translate that paranoia into design decisions.

Cloud architect is a senior role, and most job postings with 'entry-level cloud architect' in the title are really cloud engineers or solutions engineers. The architect title implies you've been accountable for production systems that broke in interesting ways and you've had to explain why. Most paths run 5–8 years before that credibility is real. Calibrate expectations accordingly.

Time to entry:3–5 years
Median wage (BLS):$130,390
Updated:
Steps:5 stages
BLS 2024–2034
↑ +11.9% job growth
Openings/yr:~11,200
Nearest BLS occupation:Computer network architects
Source: BLS ↗
Share:XLinkedInReddit

Career Progression

Where does this role lead?

Click any role to explore timeline, key skills and, where the Department of Labor publishes it, pay.

Entry

Cloud Engineer

~1–2 yrs

$78,416 (Level I)

You're provisioning infrastructure and learning why certain design choices exist. Understanding the cost and failure modes of each cloud primitive is the key early investment.

Key skills

AWS / GCP / Azure basicsTerraformLinuxNetworking fundamentalsDocker
Main trackOptional branchYour current level

Pay shown is the U.S. Department of Labor prevailing wage for Level I (entry), Level III (mid) and Level IV (senior) in the nearest BLS occupation, base wage for the typical metro, wage year 2025, shown for the main track only. It is a benchmark, not an offer; branches and lead, staff and executive stages have no official figure.

Visual roadmap

Cloud Architect learning path

Work down the line, one step at a time. Tick each skill as you can do it.

  1. 1

    Cloud Fundamentals & Core Services

    6–8 weeks

    Start with AWS (the dominant platform). Learn core services: EC2, S3, RDS, VPC, IAM, Lambda, and CloudFront. Understand shared responsibility model, regions, availability zones, and pricing. Get the Cloud Practitioner cert first.

    Skills to learn

    • AWS EC2, S3, RDS, VPC
    • AWS Lambda & API Gateway
    • CloudFront & Route 53
    • IAM (policies, roles, MFA)
    • S3 Storage Classes & Lifecycle
    • CloudWatch (metrics, logs, alarms)
    • AWS CLI & CloudShell
    • Shared Responsibility Model
    • Regions & Availability Zones
    • AWS Pricing & Cost Explorer

    Start with

  2. 2

    Networking & Security Architecture

    6–8 weeks

    Deep-dive into cloud networking: VPCs, subnets, route tables, NACLs, security groups, Transit Gateways, and Direct Connect. Master IAM policies, roles, and least-privilege design. Understand compliance frameworks (SOC 2, HIPAA, PCI DSS).

    Skills to learn

    • VPC Design (subnets, NACLs, SGs)
    • VPN Gateway & Direct Connect
    • Transit Gateway (multi-VPC)
    • AWS WAF & Shield
    • Zero Trust Architecture
    • IAM Identity Center (SSO)
    • KMS (encryption key management)
    • SOC 2 / HIPAA / PCI DSS controls
    • AWS Security Hub & GuardDuty

    Start with

  3. 3

    Infrastructure as Code with Terraform

    5–7 weeks

    Learn to provision and manage cloud infrastructure declaratively with Terraform. Study modules, state management, remote backends, and workspaces. Combine with GitHub Actions for GitOps CI/CD pipelines.

    Skills to learn

    • Terraform HCL (resources, modules)
    • Terraform Remote State (S3 + DynamoDB)
    • Terraform Workspaces
    • AWS CDK (TypeScript / Python)
    • AWS CloudFormation
    • Terragrunt (DRY Terraform)
    • Packer (machine images)
    • GitHub Actions for IaC Pipelines
    • Drift Detection & Policy as Code

    Start with

  4. 4

    Serverless, Containers & Microservices

    6–8 weeks

    Understand modern cloud-native architectures. Build with Lambda + API Gateway for serverless. Deploy containerised services with ECS or EKS. Design event-driven systems with SQS, SNS, and EventBridge.

    Skills to learn

    • AWS Lambda + API Gateway
    • ECS (Elastic Container Service) + Fargate
    • EKS (Elastic Kubernetes Service)
    • EventBridge & SQS & SNS
    • AWS Step Functions (workflows)
    • Service Mesh (App Mesh / Istio)
    • Serverless Framework / SAM
    • Microservices Patterns (strangler fig, saga)
    • API Gateway (REST, WebSocket, HTTP)

    Start with

  5. 5

    Architecture Patterns, Cost Optimisation & Certifications

    8–12 weeks

    Study the AWS Well-Architected Framework (5 pillars). Design for high availability, disaster recovery, and cost optimisation. Earn AWS Solutions Architect Professional and practise architecture whiteboards for interviews.

    Skills to learn

    • AWS Well-Architected Framework (6 pillars)
    • High Availability (multi-AZ, multi-region)
    • Disaster Recovery (RTO, RPO, strategies)
    • FinOps (Reserved Instances, Savings Plans)
    • Architecture Diagrams (draw.io, Lucidchart)
    • Architecture Decision Records (ADRs)
    • Cloud Migrations (6Rs framework)
    • Technical Leadership & Design Reviews
    • AWS Solutions Architect Professional

    Start with

jobroadmaps.com/roadmaps/cloud-architect · Pay, demand and employer data for this role are further down the page.

Job Market Insights for Cloud Architect

Data-backed

What do employers actually ask for?

Read from live job postings — how often each credential is named, from rare to almost always.

"Certification mentioned" is the most common credential named, yet it appears only occasionally in what we could read. Postings that state it are the minority, but these counts are a floor, so do not read this as "no one asks".

Some postings say outright that equivalent experience or a self-taught route is accepted. That wording is worth reading closely when you see it.

Our read: a portfolio that proves the skill, and a referral from someone inside the company, usually carry more weight than a credential match on paper. That is judgement, not something these counts measure.

Certification mentioned

Occasional

Bachelor's degree

Occasional
flexible

Equivalent experience accepted

Occasional

Computer Science background

Rare

Master's degree

Rare

Our read: how often a credential is named is not how strictly it is enforced. Equivalent experience, a standout portfolio, or a referral often counts for more than the credential listed.

Data-backed

Which skills appear most in job postings?

Read from live job postings, ranked from most to least often named.

Python is the most-named skill. Common, but not universal: many postings do not list it.

Past the fundamentals, 2 specialisation skills (Python included) start separating candidates who can do the job from candidates who have done it. The 14 niche skills are named rarely enough that knowing them is upside, not prerequisite.

SpecialisationPython
Common
SpecialisationSQL
Common
NicheAWS
Occasional
NicheAzure
Occasional
Niche

compliance

Rare
Niche

solution design

Rare
Rare
Niche

networking

Rare
Niche

proof of concept

Rare
Niche

Infrastructure as Code

Rare
Niche

high availability

Rare
NicheDocker
Rare
Niche

domain expertise

Rare
Rare
Niche

customer discovery

Rare
NicheGo
Rare

Sorted by how often named · JobRoadmaps

Data-backed

Which tools and artifacts appear most in job postings?

Read from live job postings, ranked from most to least often named.

MongoDB is the most-named tool, but no tool is a universal requirement here.

DevOpsMongoDB
Occasional
DevOpsSnowflake
Rare
MonitoringDatadog
Rare
Toolchain

GitLab

Rare
Toolchain

Salesforce

Rare
Rare
Toolchain

GitHub

Rare
Rare

Sorted by how often named · JobRoadmaps

Industry overlay

Targeting a specific industry?

The core roadmap gets you through the door anywhere. The difference between "qualified" and "they hired someone else" often lives in industry-specific context — the norms, the compliance floors, the tools assumed fluent in that sector.

Must have

multi-tenancy architecture

SaaS platforms must isolate customer data and resources securely while sharing infrastructure efficiently.

Must have

horizontal scalability

SaaS businesses grow rapidly and unpredictably; architects design systems that scale without manual intervention.

Important

usage-based billing integration

SaaS companies monetize via consumption; architects integrate metering, quota enforcement, and billing systems.

Companies hiring:

AsanaCloudflareStripeDatabricksMongoDBGitLabSnowflake
Must have

legacy system integration

Enterprise customers have decades of systems. Architects design hybrid cloud strategies and data migration patterns.

Must have

compliance and governance

Regulated industries demand HIPAA, GDPR, SOC 2, FedRAMP. Architects design for audit trails and policy enforcement.

Important

change management

Enterprise transformation requires stakeholder alignment and phased rollouts. Architects guide organizational change.

Companies hiring:

RampWPPVeeva SystemsAppian

Industry premiums based on aggregated job posting data · Updated quarterly

Interactive

How ready are you right now?

Check the skills you already have to see your current job-market fit.

The most-named skill for this role is Python, so a gap there costs you the most. No single skill dominates, but each gap narrows which postings fit you. Check what you already have to see your biggest current gap.

Readiness Check

Check the skills you already have

0/5

base skills

Your biggest gap: Python, the most often named of the skills you have not ticked.

Start there, then work down the list.

Books worth reading as a Cloud Architect

Where to start, in order. The full list of 12, grouped by career stage, is on its own page.

Getting started

  • Cover of Amazon Web Services in Action

    Amazon Web Services in Action

    by Andreas Wittig, Michael Wittig · 2015

    ~500 pages~13 hrs to read

    A hands-on tour of core AWS services: compute, storage, networking, databases and automation. A solid way to learn one platform properly before designing across several.

    View book →
  • Cover of Fundamentals of Software Architecture

    Fundamentals of Software Architecture

    by Mark Richards, Neal Ford · 2020

    ~430 pages~11 hrs to read

    Surveys architecture styles, characteristics and the trade-offs between them, plus the architect's role. Read it early to get the vocabulary for explaining why one design fits and another does not.

    View book →

Doing the job

  • Cover of Designing Data-Intensive Applications

    Designing Data-Intensive Applications

    by Martin Kleppmann · 2017

    ~620 pages~16 hrs to read

    Explains how storage engines, replication, partitioning, transactions and stream processing work and where each breaks. The reference for judging database and messaging choices in a design.

    View book →
  • Cover of Software Architecture

    Software Architecture: The Hard Parts

    by Neal Ford, Mark Richards, Pramod Sadalage, Zhamak Dehghani · 2021

    ~450 pages~11 hrs to read

    Works through decomposing systems, data ownership and service granularity using trade-off analysis. Read it when you face real decisions about splitting a monolith.

    View book →

Senior and leading

  • Cover of The Software Architect Elevator

    The Software Architect Elevator

    by Gregor Hohpe · 2020

    ~370 pages~9 hrs to read

    Describes how architects move between the engine room and the executive level, connecting technical choices to business decisions. Read it when your work shifts from designing systems to persuading organizations.

    View book →
  • Cover of Cloud FinOps

    Cloud FinOps

    by J. R. Storment, Mike Fuller · 2020

    ~450 pages~11 hrs to read

    Explains how engineering, finance and product teams manage cloud spend together. Read it when cost becomes part of your design reviews.

    View book →

All 12 books for a Cloud Architect →Browse all books →

Some book links are affiliate links: we earn a small commission if you buy, at no cost to you. It does not affect what we list.

Prerequisites & Education

What credentials do employers look for?

These are the most common paths into this role — no single one is required.

Education Level

View list — coming soon
  • Bachelor's in Computer Science, Computer Engineering, or Information Systems
  • Bachelor's in IT or Networking — common path via sysadmin and infrastructure roles
  • Bachelor's in any technical discipline with strong cloud infrastructure experience
  • No degree — cloud architecture is one of the most cert-receptive senior tech roles

Cloud Architect is typically a senior role reached after 5–8 years in engineering or infrastructure. Certs and demonstrated architecture experience matter far more than the degree at this level.

Certifications

View list — coming soon
  • AWS Certified Solutions Architect – Professional — the most recognised cloud architecture cert
  • Google Cloud Professional Cloud Architect — strong signal for GCP-heavy organisations
  • Microsoft Azure Solutions Architect Expert (AZ-305) — near-required for Azure shops; requires AZ-104 first ($165 per exam)
  • Microsoft Azure Administrator Associate (AZ-104) — prerequisite for AZ-305; validates core Azure infrastructure management
  • Microsoft Azure Fundamentals (AZ-900) — entry-level baseline; good starting point before AZ-104 ($165)
  • Google Cloud Professional Cloud Network Engineer — validates designing, implementing, and managing GCP network infrastructure; valued for multi-cloud and hybrid architecture roles ($200)
  • CKA (Certified Kubernetes Administrator) — $395, hands-on exam; expected for cloud-native architecture roles; validates cluster administration, troubleshooting, and workload management
  • CKS (Certified Kubernetes Security Specialist) — $395, requires active CKA; covers cluster hardening, network policies, and supply chain security; differentiates senior architects from mid-level
  • CKAD (Certified Kubernetes Application Developer) — $395, covers application deployment patterns; useful complement to CKA for architects who also own developer experience

AWS SAP and GCP Professional Cloud Architect are the two most cited in Cloud Architect job postings. The Azure path (AZ-900 → AZ-104 → AZ-305) is a clear progression and near-required at Azure-first enterprises. For cloud-native architects, CKA is increasingly expected alongside cloud provider certs.

Bootcamps & Training

View list — coming soon
  • A Cloud Guru / Pluralsight — structured cloud certification prep with hands-on labs
  • Linux Foundation Kubernetes and cloud-native training — authoritative, vendor-neutral
  • AWS Skill Builder — official AWS training with practice exams and labs
  • HashiCorp Terraform training — essential for infrastructure-as-code in architecture roles

Architecture skills are best developed through real infrastructure work. Training programs are most valuable as certification prep — not as a substitute for hands-on cloud experience.

Portfolio & Other

View list — coming soon
  • Architecture diagrams (AWS, GCP, or Azure) with documented design decisions — publish in a blog or GitHub
  • Terraform or Pulumi modules publicly available on GitHub or the Terraform Registry
  • Cloudformation or Bicep templates demonstrating multi-region or multi-account design
  • Public post-mortem or incident retrospective showing systems thinking under failure
  • Speaking at cloud or infrastructure meetups — AWS User Groups, KubeCon talks

Architecture diagrams that document real trade-offs (cost vs latency, availability vs consistency) are far more compelling than cert lists. Most Cloud Architect candidates lack a public portfolio entirely.

Your Roadmap

5 steps
1

Cloud Fundamentals & Core Services

6–8 weeks

Start with AWS (the dominant platform). Learn core services: EC2, S3, RDS, VPC, IAM, Lambda, and CloudFront. Understand shared responsibility model, regions, availability zones, and pricing. Get the Cloud Practitioner cert first.

Skills to learn

AWS EC2, S3, RDS, VPCAWS Lambda & API GatewayCloudFront & Route 53IAM (policies, roles, MFA)S3 Storage Classes & LifecycleCloudWatch (metrics, logs, alarms)AWS CLI & CloudShellShared Responsibility ModelRegions & Availability ZonesAWS Pricing & Cost Explorer
2

Networking & Security Architecture

6–8 weeks

Deep-dive into cloud networking: VPCs, subnets, route tables, NACLs, security groups, Transit Gateways, and Direct Connect. Master IAM policies, roles, and least-privilege design. Understand compliance frameworks (SOC 2, HIPAA, PCI DSS).

Skills to learn

VPC Design (subnets, NACLs, SGs)VPN Gateway & Direct ConnectTransit Gateway (multi-VPC)AWS WAF & ShieldZero Trust ArchitectureIAM Identity Center (SSO)KMS (encryption key management)SOC 2 / HIPAA / PCI DSS controlsAWS Security Hub & GuardDuty
3

Infrastructure as Code with Terraform

5–7 weeks

Learn to provision and manage cloud infrastructure declaratively with Terraform. Study modules, state management, remote backends, and workspaces. Combine with GitHub Actions for GitOps CI/CD pipelines.

Skills to learn

Terraform HCL (resources, modules)Terraform Remote State (S3 + DynamoDB)Terraform WorkspacesAWS CDK (TypeScript / Python)AWS CloudFormationTerragrunt (DRY Terraform)Packer (machine images)GitHub Actions for IaC PipelinesDrift Detection & Policy as Code
4

Serverless, Containers & Microservices

6–8 weeks

Understand modern cloud-native architectures. Build with Lambda + API Gateway for serverless. Deploy containerised services with ECS or EKS. Design event-driven systems with SQS, SNS, and EventBridge.

Skills to learn

AWS Lambda + API GatewayECS (Elastic Container Service) + FargateEKS (Elastic Kubernetes Service)EventBridge & SQS & SNSAWS Step Functions (workflows)Service Mesh (App Mesh / Istio)Serverless Framework / SAMMicroservices Patterns (strangler fig, saga)API Gateway (REST, WebSocket, HTTP)
5

Architecture Patterns, Cost Optimisation & Certifications

8–12 weeks

Study the AWS Well-Architected Framework (5 pillars). Design for high availability, disaster recovery, and cost optimisation. Earn AWS Solutions Architect Professional and practise architecture whiteboards for interviews.

Skills to learn

AWS Well-Architected Framework (6 pillars)High Availability (multi-AZ, multi-region)Disaster Recovery (RTO, RPO, strategies)FinOps (Reserved Instances, Savings Plans)Architecture Diagrams (draw.io, Lucidchart)Architecture Decision Records (ADRs)Cloud Migrations (6Rs framework)Technical Leadership & Design ReviewsAWS Solutions Architect Professional

Start here this week

This week: take the AWS or GCP free tier and design a three-tier architecture — web tier, application tier, database tier. Write down every failure mode you can identify. What happens when the database goes down? When the load balancer is saturated? When a network partition separates the app tier from the database? That exercise is the interview.

For structured entry, the AWS Solutions Architect Associate certification is the industry-standard credential for this path. It's meaningful because the exam tests actual architectural reasoning, not just memorization. Study with Adrian Cantrill's course rather than the official materials — it's more thorough. After Associate, the Professional certification is worth pursuing for senior roles.

Pay

U.S. Department of Labor data for the nearest BLS occupation, Computer network architects. BLS has no occupation for this exact title, so treat these as a benchmark.

Median wage, all levels$130,390
Entry Level (Level I)$78,416
Cloud Engineer / Junior Solutions Architect
Mid Level (Level III)$118,082
Cloud Architect / Solutions Architect
Senior Level (Level IV)$137,925
Principal Cloud Architect / Chief Architect

Median: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics (median wage, May 2024) and Employment Projections (2024–34). Levels: U.S. Department of Labor Office of Foreign Labor Certification prevailing wage levels (wage year 2025, typical metro), a base-wage benchmark for the metro in the middle of 331 areas, not an offer. See every metro.

Job Titles at Each Level

Entry

Cloud Engineer / Junior Solutions Architect

Mid

Cloud Architect / Solutions Architect

Senior

Principal Cloud Architect / Chief Architect

Steps Overview

  1. 1

    Cloud Fundamentals & Core Services

    6–8 weeks

  2. 2

    Networking & Security Architecture

    6–8 weeks

  3. 3

    Infrastructure as Code with Terraform

    5–7 weeks

  4. 4

    Serverless, Containers & Microservices

    6–8 weeks

  5. 5

    Architecture Patterns, Cost Optimisation & Certifications

    8–12 weeks

Explore more roadmaps

Not sure this is the right path? Browse all tech career roadmaps.

View Similar Roadmaps

Built a project while following this roadmap?

Turn it into a hiring-ready case study in 10 seconds — free.

Generate Case Study

Ready to explore more?

Browse all career roadmaps across tech, business, and creative fields.