What does a cloud engineer do?
A cloud engineer builds and runs an organisation's systems on a public cloud such as AWS, Azure or Google Cloud. The work covers accounts and permissions, networks, compute and storage, backups, cost and the scripts or templates that create all of it. The cloud provider runs the data centres; the engineer is responsible for how the company uses them.
The Bureau of Labor Statistics has no profile for cloud engineers. The nearest is network and computer systems administrators, who "install, configure, and maintain organizations' computer networks and systems." BLS gives a median annual wage of $99,130 in May 2025, and projects employment of network and computer systems administrators to decline 4 percent from 2025 to 2035.
O*NET OnLine also has no cloud engineer occupation. The closest is computer systems engineers/architects (15-1299.08), which lists "Infrastructure Engineer" among its reported titles. Its tasks include "Configure servers to meet functional specifications" and "Monitor system operation to detect potential problems."
How were these cloud engineer questions chosen?
Each cloud engineer question here comes from a published duty or from public guidance by NIST and AWS, matched to what an interviewer would test. The questions are drawn from the job's published duties, not from a survey of real interviews, and they do not describe any named company's process.
| Duty or guidance (BLS, O*NET, NIST, AWS) | Question it tends to produce | What the interviewer is checking |
|---|---|---|
| Determine network and system needs | "Which service model fits this app, and why?" | Trade-offs of IaaS, PaaS and SaaS for the case at hand |
| Add users and assign security permissions | "How would this app get access to storage?" | Roles, temporary credentials and least privilege |
| Maintain network and system security | "Who is responsible for patching this server?" | The shared responsibility split for each service |
| Configure servers to meet specifications | "How do you create environments that match?" | Templates in version control, reviewed before apply |
| Monitor system operation for problems | "How would you know this service is unhealthy?" | Alerts on what users feel, with a runbook |
| Evaluate and optimize system performance | "The cloud bill doubled. Where do you look?" | Tags, usage data and a fix that does not break service |
What cloud model and responsibility questions come up?
Cloud model questions check that a cloud engineer can define the basics precisely. NIST's definition of cloud computing (SP 800-145) calls it "a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources." NIST says the model has five essential characteristics, three service models and four deployment models.
1. Explain IaaS, PaaS and SaaS with an example of each.
What they listen for: what you manage in each model and what the provider manages, with an example from your own work. Follow-up that tends to come next: "Which would you pick for a small team's internal tool?"
2. Who is responsible for security in the cloud?
What they listen for: the shared responsibility model. AWS says "Security and Compliance is a shared responsibility between AWS and the customer." Its shared responsibility page says AWS protects "the infrastructure that runs all of the services offered in the AWS Cloud," while the customer's part "will be determined by the AWS Cloud services that a customer selects." Follow-up: "Who patches the operating system on a virtual machine?"
3. When would you keep a workload on premises?
What they listen for: honest reasons such as data rules, steady load that costs less on owned hardware, or a dependency that cannot move. Follow-up: "How would you connect it to the cloud safely?"
What identity and access questions should you expect?
Identity questions matter most in a cloud engineer interview, because one broad permission can expose a whole account. AWS's IAM security best practices tell you to "grant only the permissions required to perform a task," to "Require multi-factor authentication (MFA)," and to require workloads to use temporary credentials with IAM roles. Interviewers listen for those habits in every design.
4. An application on a virtual machine needs to read files from a storage bucket. How do you give it access?
What they listen for: a role attached to the machine, temporary credentials, and a policy scoped to one bucket and one action. Follow-up that tends to come next: "How would you check nothing else can read that bucket?"
This question best shows the role, so here is a weak answer and the same answer fixed. Both are made-up examples.
Weak made-up example: "I'd create an access key for an admin user, put it in the app's config file, and make sure the file isn't in Git."
The weak answer gives the app far more power than it needs and stores a long-lived key where it can leak. Admin rights mean a leaked key exposes the whole account.
Fixed made-up example: "I'd create a role for this app with a policy that allows only reading objects from that one bucket, and attach the role to the instance. The app then gets short-lived credentials from the platform, so there's no key in config or code. I'd block public access on the bucket, turn on access logging, and check the policy with the provider's access analysis tool. If the app later needs to write, I'd add that one action after review."
5. How do you protect the root or owner account?
What they listen for: MFA on the root account, no daily use of it, no access keys for it, and alerts on any sign-in. Follow-up: "Who holds the MFA device?"
6. How do you review who has access to what?
What they listen for: a regular review of users, roles and unused permissions, with removal of what nobody uses. AWS lists "Regularly review and remove unused users, roles, permissions, policies, and credentials." Follow-up: "What would you do with a role nobody claims?"
What networking and build questions come up?
Networking and build questions test whether a cloud engineer can lay out a network and create it the same way every time. Interviewers ask where each piece sits, what can reach it, and how a change gets reviewed. O*NET lists "Verify stability, interoperability, portability, security, or scalability of system architecture" among the tasks.
7. Design a network for a web app with a database.
What they listen for: public and private subnets, the database reachable only from the app tier, a load balancer in front, and resources spread across zones. Follow-up: "How does the private tier get software updates?"
8. How do you build environments that match each other?
What they listen for: infrastructure as code in version control, a review of the planned change before apply, and the same template for staging and production with different settings. Follow-up: "Someone changed production by hand. How do you find out?"
9. A server can't reach the internet after a change. Where do you look?
What they listen for: the order you check routes, security rules, network access lists and DNS, and how you compare with the last working state. Follow-up: "How would you test the fix without guessing?"
What reliability and cost questions come up?
Reliability and cost questions check that a cloud engineer keeps services up without wasting money. BLS lists "Evaluate and optimize network and system performance" and "Diagnose and resolve problems when alerted by a user or an automated monitoring system" among the duties. Interviewers want measurements first and changes second.
10. How would you make this service survive the loss of one data centre?
What they listen for: running in more than one zone, health checks, data replicated or backed up elsewhere, and a tested failover. Follow-up: "When did you last test a restore?"
11. The monthly cloud bill doubled. What do you do?
What they listen for: break the bill down by service and tag, find the change behind the jump, then fix it (idle resources, oversized instances, data transfer). Follow-up: "How would you stop it happening again?"
12. A patch is released for a critical flaw. How do you roll it out?
What they listen for: test it on a small group first, roll out in stages, watch for errors, and keep a way back. O*NET lists "Research, test, or verify proper functioning of software patches and fixes." Follow-up: "What if the patch breaks an app?"
Which behavioral questions should you expect?
Behavioral questions ask a cloud engineer about real events, so answer each in STAR order: situation, task, action, result. Interviewers listen for your part in a migration or outage, how you kept others informed, and what you changed after. The guide to situational interview questions explains how these differ from what-would-you-do questions.
13. Tell me about a migration to the cloud you worked on.
What they listen for: how you chose what moved first, how you tested, the cutover plan and what went wrong. Follow-up: "What would you move differently now?"
14. Tell me about a time you found a security gap in your own setup.
What they listen for: how you found it, how fast you closed it, and who you told. Follow-up: "Was any data exposed, and how did you check?"
What follow-up questions tend to come next?
Follow-ups test whether your design holds when something fails. Expect a cloud engineer interviewer to take away a zone, leak a key, double the traffic or cut the budget, then ask what happens. Prepare by walking each system on your resume through those four events before the interview.
- "What does this cost each month, roughly?"
- "What happens if that zone goes down?"
- "Who can delete this resource?"
- "How long would a restore take?"
- "What did you automate, and what is still manual?"
How should you prepare for a cloud engineer interview?
Prepare one system you built or ran that you can draw from memory: network, access, data, monitoring and cost. Write four STAR stories: a migration, an outage, a security fix and a cost saving. Know the cloud named in the posting, and be ready to map its services to the ideas on this page.
The free interview question generator takes the posting and the round you pick, and returns likely questions, why they come up and what the interviewer listens for. Cloud loops overlap with nearby roles, so compare this page with the questions for a DevOps engineer, a solutions architect and a network engineer.
List the services and tools from the posting that you have used, with a result for each; the guide to resume keywords shows how. Prept's Mock room lets you answer out loud on a clock, scores each answer out of 10 and checks it against your resume, and it is included in the free plan.