Cloud engineer interview (AWS, Azure, GCP): what is really assessed
· 9 min read
In a cloud role, the question is never "do you know this service". It is "why that one rather than another, and at what price". A candidate reciting a service catalogue loses to one who can make trade-offs.
Which architecture questions come up most?
- Designing an application that survives losing a zone: they expect you to discuss redundancy AND what it costs.
- Choosing between virtual machines, containers and serverless for a given workload — and being able to say when serverless is the wrong call.
- Separating environments and managing access: least privilege must be a reflex, not a phrase.
- Storing and rotating secrets without writing them in code or in a committed environment variable.
- Explaining your backup strategy, and above all the last time you tested a restore.
Why does the cost question always come up?
Because it is the best signal of real experience. Anyone who has run infrastructure knows a cloud bill runs away through egress traffic, forgotten volumes and test environments left on over the weekend. A candidate who has never had to justify a bill talks architecture without ever mentioning money — and that shows within two minutes.
Is a certification enough to land the role?
It opens the door; it does not walk through it. A certification proves you know the vocabulary and the official best practices; it does not prove you have lived through an outage at 3am. If your experience is mostly certified, own it clearly and compensate with a real personal project — infrastructure you built, broke and fixed is worth more than a badge.
Do you need infrastructure as code?
Yes, it has become a prerequisite rather than a bonus. Terraform, Bicep, CloudFormation: the tool matters less than your ability to explain why nobody clicks through a console to create durable resources any more. You will be asked how you manage state, how you review a risky change, and what you do when reality has drifted from the code.
How do you answer if you do not know THEIR provider?
By showing transferability, not by bluffing. Concepts overlap heavily across providers: private networking, identity management, object storage, load balancing. Say what you can do on one, name the equivalent on the other if you know it, and acknowledge what you will have to learn. A recruiter prefers that honesty to shaky vocabulary they will dismantle on the next question.
How is this different from a DevOps interview?
The scopes overlap, but the emphasis shifts: a cloud interview digs into architecture, availability and cost, while a DevOps interview digs into the delivery pipeline and automation. Many postings blend the two — which is why reading the posting closely matters before deciding what to lead with.
In a cloud role, the candidate who impresses is not the one who knows the most services. It is the one who knows which ones not to use.
The rest plays out out loud, as always: explaining an architectural trade-off aloud is a skill of its own. See our article on why hire you and, if the interview is in English, interviewing in English.