Path 9 of 10, by 2026 demand
Cloud Solutions Architect
Design customer or internal solutions on a cloud platform, from landing zone to workload architecture, increasingly with AI workloads in scope.
Demand Steady. The AI-era version of this role is the Applied AI Architect (see the Forward Deployed path), which both labs hire for heavily (our count, §2.3).
What the role is
Cloud Solutions Architects translate business requirements into cloud architectures: landing zones, networking, identity, data platforms, application hosting, resilience and cost. Partner, vendor and consulting roles are customer-facing; internal roles serve product teams.
In 2026 most solution architecture work includes AI workloads: private model access, retrieval platforms, data governance and cost control. If you are aiming at the AI labs, use the Forward Deployed / Applied AI path instead; this path suits cloud-vendor, partner and enterprise roles.
Level signals
- Well-architected trade-offs: reliability, security, cost, performance, operations.
- Customer discovery and clear documentation.
- Migration planning with realistic risk.
- Certifications help at vendors and partners; experience matters more.
The typical loop
No single public source. Common shape for cloud architect roles.
| Stage | What it tests | Basis |
|---|---|---|
| Recruiter and hiring manager | Platform depth, customer experience | Common industry pattern; no single source |
| Architecture case / whiteboard | Design a solution from requirements | Common industry pattern; no single source |
| Presentation | Present an architecture to a mixed audience | Common industry pattern; no single source |
| Technical depth | Networking, identity, data, AI services | Common industry pattern; no single source |
| Behavioural | Customer and stakeholder stories | Common industry pattern; no single source |
Track order
Work top to bottom. Ticks come from the lessons you mark complete.
- 01The design methodSystem design track. Including the building-blocks map with Azure and AWS equivalents.
- 02The trade-offsSystem design track. Reliability and data trade-offs.
- 03Working with customersCustomer discovery and technical consulting track. Discovery and objections.
- 04Worked promptsSystem design track. Enterprise Q&A and migration prompts.
- 05Building blocksLLM and agent engineering track. AI workloads are now in scope.
- 06Securing AI systemsSecurity engineering for AI systems track. Data protection and identity for AI workloads.
- 07Behavioural rounds at Staff levelLeadership and behavioral track. Customer-impact stories.
- 08Mock roundsMock rounds track. Customer case and design mocks.
Role practice set
Prompts written for this site. They are not reported interview questions.
- Design a landing zone for a regulated company adopting LLMs: networking, identity, policy, logging, model access.
- Present a migration plan for 200 VMs to a mixed audience in 15 minutes.
- Answer the six enterprise objections from the consulting track for an Azure-hosted assistant.
Your résumé and story angle
- Enterprise Solutions Architect on Azure is the exact profile. [Largest customer or estate, outcome.]
- Kubernetes and distributed systems distinguish you from architects who only draw diagrams. [Hands-on story.]
- AI workloads: [AI integration work] positions you for the growing AI architecture demand.