The difference between a cloud engineer CV and a cloud architect CV is not seniority — it is the type of evidence on the page. An engineer CV shows execution: infrastructure built, pipelines deployed, costs reduced. An architect CV shows design authority: hard problems framed, architectural decisions made and justified, outcomes delivered at programme scale. Most cloud architect applications fail because they read as senior engineer CVs — impressive execution, no design narrative. The second common failure is certification level: associate-level certifications (AWS SAA-C03, Azure AZ-900) on an architect application signal mid-level, not strategic. Professional-level certifications (AWS Solutions Architect Professional, Azure Solutions Architect Expert, Google Professional Cloud Architect) are what hiring managers expect to see before the interview shortlist is set. This guide covers the ATS keywords, CV structure, and bullet patterns that position a cloud architect CV at the right level.

What Cloud Architect Job Descriptions Require in 2026

Cloud architect JDs are more varied than engineer JDs, but the requirements that appear consistently across AWS, Azure, and GCP roles in 2026 are:

  • Professional-level cloud certification — AWS Solutions Architect Professional (SAP-C02), Azure Solutions Architect Expert (AZ-305), or Google Professional Cloud Architect. These are the minimum expected credentials for architect-level roles at most mid-size and enterprise companies. Associate-level certifications are insufficient as a primary credential; they can be listed as supporting qualifications.
  • Migration and transformation experience — the majority of cloud architect roles exist because organisations are migrating workloads or modernising existing cloud infrastructure. JDs consistently list "cloud migration" or "cloud transformation" as a requirement. Candidates without documented migration experience are at a disadvantage in most architect hiring pipelines.
  • Enterprise governance — AWS Organizations with SCPs, Azure Management Groups with Policy, or GCP resource hierarchy with org-level constraints. Architect roles own the governance layer, not just individual workloads. JDs for senior architect roles explicitly list "landing zone design" and "multi-account strategy."
  • Architecture documentation — architecture decision records (ADRs), reference architectures, and technical roadmaps. The ability to produce artefacts that guide engineering teams is a core deliverable of the architect role.
  • Executive communication — translating architecture trade-offs into business language for CTO, CFO, and board audiences. Senior architect JDs list "stakeholder management" or "executive communication" as a requirement, not a soft skill.

Cloud architect salaries in 2026: £80K–£140K UK; $150K–$220K US. Principal and Distinguished Architect roles at hyperscaler-adjacent companies exceed $280K total compensation.

ATS Keywords for a Cloud Architect CV

Cloud architect ATS filtering starts with provider and certification. Recruiters search for the professional certification name explicitly — "AWS Solutions Architect Professional" or "Azure Solutions Architect Expert" — not just the provider name alone.

Essential ATS terms for a cloud architect CV:

  • Title variants: Cloud Architect, Solutions Architect, Enterprise Architect, Cloud Solutions Architect, Principal Cloud Architect, Technical Architect
  • Providers: AWS, Microsoft Azure, Google Cloud Platform, GCP, multi-cloud, hybrid cloud
  • Certifications: AWS Solutions Architect Professional, SAP-C02, Azure Solutions Architect Expert, AZ-305, Google Professional Cloud Architect, CKA, TOGAF
  • Governance: Well-Architected Framework, landing zone, AWS Control Tower, AWS Organizations, Azure Policy, Azure Management Groups, cloud governance, FinOps, TCO
  • Architecture patterns: microservices, event-driven architecture, serverless, API Gateway, service mesh, CQRS, event sourcing
  • Migration: cloud migration, 7Rs, lift-and-shift, re-platforming, re-architecture, application modernisation, on-premise to cloud
  • Security: Zero Trust, CSPM, cloud security architecture, threat modelling, data classification, secrets management
  • IaC: Terraform, CloudFormation, Pulumi, CDK, Infrastructure as Code
  • Long-tail phrases: cloud architect resume examples, how to write a cloud architect resume, solutions architect cv template, AWS architect resume, Azure architect cv

Placement: Professional certification name in full in your CV headline or certifications section. "AWS Solutions Architect Professional" must appear as the complete string — not just "AWS certified." Your Skills section should lead with architecture patterns and governance frameworks, then tools — the design layer comes before the execution layer on an architect CV.

Cloud Architect CV Structure and Bullets That Show Design Authority

Section order:

  1. Headline — "Cloud Architect | AWS Solutions Architect Professional · Terraform · Multi-Account · FinOps"
  2. Certifications — dedicated section at the top. Professional-level first. Include: name in full, issuing body, year, expiry date.
  3. Skills — Architecture Patterns / Governance & Compliance / Cloud Providers / IaC / Languages
  4. Experience — 4–5 bullets per role; each bullet should show a design decision and its outcome, not just a service used
  5. Education — CS, engineering, or mathematics degree; bottom of page

Two pages is the standard; three is acceptable at principal or distinguished level with publications, conference talks, or board-level advisory work. Link to GitHub if you have public architecture decision records, reference architectures, or well-documented IaC repositories.

Architect bullets need to show the design reasoning, not just the result. Three examples:

  • Designed a 7R migration strategy for a 340-application estate from on-premise to AWS — built the landing zone using Control Tower across 12 accounts, defined networking via Transit Gateway and Direct Connect, and delivered the programme 6 weeks ahead of schedule with zero critical incidents at a £4.2M migration cost against a £5.8M budget
  • Architected an event-driven order processing platform on AWS using EventBridge, SQS, and Lambda handling 2.4M daily transactions, replacing a monolithic batch process responsible for 4 SLA breaches; p99 processing latency fell from 8 minutes to 340ms
  • Led cloud cost governance across a 22-account AWS organisation — implemented SCPs to restrict unapproved resource types, enforced tagging via Config Rules, and reduced untagged spend from 34% to under 2%; annual cloud spend reduced by £1.1M through committed use agreements and rightsizing

Cloud architect interviews are design-led: the canonical question is "design a globally distributed platform for this use case — walk me through your decisions." The CV's evidence of past design decisions sets the complexity level of the question you receive. Candidates with programme-scale migration evidence and governance work get harder, more interesting problems — which is also the signal that separates shortlisted candidates from the rest.

Three Cloud Architect CV Mistakes That Signal the Wrong Level

Architecture described as execution. "Built a microservices platform on AWS" is an execution statement. It says what was constructed, not what was designed. A cloud architect CV should show the decision: why microservices, what the trade-offs were against a modular monolith, how service boundaries were defined, what the failure modes are and how they're handled. "Designed the service decomposition strategy for a monolith-to-microservices migration across 18 bounded contexts, defining inter-service contracts, event schema standards, and circuit breaker patterns — reducing deployment coupling that had caused 11 coordinated release failures in the prior year" is an architecture statement. The reasoning and constraints are the signal.

Associate-level certifications as the primary credential. AWS Solutions Architect Associate, Azure AZ-900, and their equivalents are entry-level validations. They demonstrate foundational knowledge, not design authority. For cloud architect roles — where the expectation is that you can design enterprise-grade, multi-account, multi-region architectures — these certifications are table stakes at best and filters at worst when listed as the primary credential. If you hold the professional-level certification, lead with it. If you don't yet hold it, it is the single highest-return investment you can make before your next application: it directly changes which JDs you are shortlisted for.

No migration or transformation evidence. Most cloud architect roles are created to solve a specific problem: migrating a legacy estate, modernising existing cloud infrastructure, or designing a net-new platform. A CV with no migration evidence — no 7R assessment, no landing zone design, no on-premise-to-cloud programme — misses the core signal that architect hiring managers filter for. Even a single well-documented migration programme (what was migrated, what the strategy was, what the outcome was) is enough to establish the signal. If your architecture experience has been greenfield only, make that explicit and describe the governance and design work in detail.

If you are applying to cloud architect or solutions architect roles and want your CV rebuilt around the specific AWS, Azure, and migration requirements in a target job description, Resumegpt generates your cloud architect CV from your work history in under 60 seconds — professional certifications surfaced, design authority signalled, ATS-optimised, and exported as a PDF ready to submit.