Interview Coach
Cloud Engineer Interview Questions
Cloud Engineer interviews test whether you can design for failure and for the bill in equal measure. Expect an architecture round on a described workload, hands-on infrastructure-as-code, and detailed cost questions — because cloud spend is where most organisations feel the consequences of engineering decisions most directly. CVs are read for the scale of the estate and for cost and reliability numbers.
Build your story bank freeWhat cloud engineer interviews are scored on
Architecture design
Designing a workload end to end — compute choice, networking, storage, availability zones, failover. Interviewers check whether you design to a stated availability target rather than over-engineering by default.
Infrastructure as code
Terraform or CloudFormation: module structure, state management, drift, and how you avoid a destructive plan reaching production.
Cost engineering
Rightsizing, reserved versus spot, storage tiering, egress charges, and the ability to estimate what a design will cost before building it.
Reliability and security posture
Multi-AZ versus multi-region trade-offs, backup and restore testing, IAM least privilege, and network isolation.
Technical cloud engineer interview questions
Questions of this shape recur across cloud engineer loops. Practise them aloud — interviewers score how you reason, not only where you land.
- Design a highly available web application for 99.95% uptime. What does each nine cost you?
- When would you choose containers over serverless, and what does each lock you into?
- Explain how Terraform state works and what happens when two engineers apply at once.
- Your monthly bill jumped 40% with no traffic change. How do you investigate?
- How do you design least-privilege IAM without blocking every deployment?
- Walk me through a disaster recovery plan. What is your RTO and RPO, and have you tested it?
- How would you reduce data transfer costs in a multi-AZ architecture?
Behavioural questions for cloud engineer roles
Prepare one STAR story per theme. A single strong story usually answers two or three of these prompts.
- Tell me about a cloud outage you were involved in. What changed afterwards?
- Describe a significant cost reduction you drove and what you had to trade.
- Tell me about a migration that did not go to plan.
- Describe pushing back on an architecture you thought was over-engineered.
- Tell me about a security misconfiguration you found or caused.
Numbers that make cloud engineer answers credible
A STAR answer without a result is a story. These are the measures that carry weight in this role.
Questions worth asking your interviewer
- What is the current monthly spend, and is anyone accountable for it?
- How much of the estate is defined in code versus clicked together?
- Has disaster recovery ever been tested end to end?
- Single cloud or multi-cloud, and what drove that decision?
Cloud Engineer interview FAQs
Which cloud should I specialise in?+
AWS still has the largest share of postings and the deepest job market, so it is the safest default. Azure is strong in enterprises with existing Microsoft agreements, particularly finance, healthcare and government. GCP is smaller but concentrated in data and ML-heavy organisations. The concepts transfer well — compute, networking, IAM and storage tiers map across providers — so go deep in one and be conversant in a second rather than shallow in three.
What metrics belong on a Cloud Engineer CV?+
Cost, scale and reliability. Monthly spend managed and reduced (in percentage and absolute terms), workloads or accounts under management, uptime against SLO, RTO and RPO achieved, and percentage of infrastructure defined in code. "Cut AWS spend 38% ($1.1M/yr) through rightsizing, savings plans and storage tiering with no SLO regression" works because it shows financial impact with the reliability caveat that makes it credible.
How much cost knowledge do interviews really expect?+
More than most candidates prepare for. It is common to be asked to estimate roughly what a design will cost, to explain why egress charges surprise people, or to walk through investigating an unexplained bill increase. This is because cloud cost is a direct output of architecture decisions, and engineers who cannot reason about it design expensive systems. You do not need pricing memorised — you need the mental model of which choices are expensive and why.
Cloud Engineer or DevOps Engineer — what is the difference?+
They overlap heavily and titles are used loosely. Cloud Engineer skews toward infrastructure design, provisioning and cost — what the platform is. DevOps skews toward delivery pipelines, automation and developer experience — how software reaches it. In smaller organisations one person does both. Read the posting's tools: heavy Terraform, networking and cost language means cloud; heavy CI/CD, release and pipeline language means DevOps.
Need the CV before the interview?
See cloud engineer CV examples, before/after bullets, and the metrics reviewers look for.
Other interview guides
Turn your experience into answers
CVEdge reads your CV, drafts STAR stories from what you actually did, and matches them to the cloud engineer job you're interviewing for.
Start building free