Technical screening questions
Ask for one example per question and listen for specifics.
- How do you organise Terraform state across environments? A good answer: Remote state, separate state per environment and locking.
- How do you give an application access to a storage bucket? A good answer: A role with least privilege, not shared keys.
- How do you design a network for a three-tier app? A good answer: Public and private subnets, routing, load balancer and security groups.
- How do you reduce a cloud bill? A good answer: Right-sizing, schedules, storage tiers, commitments and tagging for visibility.
- What do you do when a deployment fails halfway? A good answer: Inspect state, roll back or reapply, and add checks before the next run.
Quick screening questions
Use these when you have only a few minutes.
- Which cloud and which services did you run in production?
- How do you structure Terraform for several environments?
- Describe a cost or outage problem you fixed.
What separates the levels
Match the level to the requirement before you submit.
- Junior: follows existing modules.
- Mid: designs and delivers environments.
- Senior: sets cloud standards and guardrails.
Red flags
Any of these is a reason to probe further.
- Console clicks only, no infrastructure as code.
- Cannot explain a security group.
- No view on cost.
Tools you should hear mentioned
A cloud engineer with real experience usually names several of these without prompting.
- Terraform or CloudFormation
- The cloud CLI and console
- Kubernetes or managed container services
- CI/CD tools
- Cloud monitoring
- Python or Bash
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a cloud engineer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.