Cloud Engineer
Practice cloud engineering: AWS, Azure and GCP basics, IAM, VPC networking, storage, serverless, Terraform, cost control and disaster recovery.
- Questions
- 100
- Interview Qs
- 30
- Judged problems
- 38
- Skills
- 10
About the role
A Cloud Engineer designs, builds and runs systems on public cloud platforms such as AWS, Microsoft Azure and Google Cloud. Day to day this means creating networks, compute, storage and databases, wiring up identity and access, and making sure applications are secure, reliable and affordable.
Most modern cloud work is done as code. Cloud Engineers write Terraform or OpenTofu modules, review pull requests for infrastructure changes, automate deployments in CI/CD pipelines, and keep environments consistent across development, staging and production. They also watch monitoring dashboards, respond to alerts and tune resources when traffic grows.
The role sits between developers, security and finance. You help developers ship faster with good platform defaults, help security teams enforce least privilege and encryption, and help finance understand and reduce the monthly bill. Strong Cloud Engineers know the trade-offs behind each service, not just how to click through a console.
Practise by level
Open the full question bank (100 questions) →Mock interview
Screening round
4 questions · 4 min each · pass 50%
mediumTechnical round
5 questions · 4 min each · pass 60%
hardFinal round
6 questions · 3 min each · pass 70%
Coding problems for cloud engineers
- Compare Release Versionseasy
- Exponential Backoff Timelineeasy
- First Failing Buildeasy
- How Much Error Budget Is Left?easy
- Is There a Corridor Route?easy
- Latency Percentileseasy
- Load Parcels Onto Vanseasy
- Parse an Access Log Lineeasy
- Sum of Prices in a Rangeeasy
- Cheapest Route With Limited Layoversmedium
- CPU Jobs with Cooldownmedium
- Does a Cron Expression Match?medium
Skills in this track
Learning roadmap
- 1
Learn cloud and Linux basics
Understand regions, availability zones, the shared responsibility model and core services. Get comfortable with Linux, SSH, DNS and basic networking (IP, CIDR, ports, TCP vs UDP).
- 2
Master one provider deeply
Pick AWS, Azure or GCP and learn IAM, VPC networking, compute (VMs, containers, functions), object storage and managed databases. An associate-level certification is a good milestone.
- 3
Automate with Infrastructure as Code
Learn Terraform or OpenTofu: providers, resources, modules, variables, remote state and locking. Practise plan and apply in CI pipelines with code review.
- 4
Design for security and reliability
Apply least privilege, encryption with KMS, private networking and secrets management. Design multi-AZ systems, backups, and DR strategies that meet clear RTO and RPO targets.
- 5
Operate, observe and optimize cost
Set up monitoring, logging and alerting. Learn pricing models, tagging, rightsizing, Savings Plans and Spot. Read the Well-Architected Framework and review real workloads against it.
Top Cloud Engineer interview questions
- Explain the difference between IaaS, PaaS and SaaS with an example of each.
- What is a VPC and what are its main building blocks?
- Explain IAM users, groups, roles and policies. When would you use a role instead of a user?
- How would you make a simple web application highly available in the cloud?
- What pricing models do cloud providers offer for compute, and when would you use each?
- What is the difference between containers and virtual machines, and when would you choose each?