Cloud Interviews.
Cloud and DevOps interview prep — AWS/Azure/GCP scenario questions, architecture reviews, and SRE concepts.
Beginner
Start here — no prior experience needed
What Cloud Interviews Test That Certifications Do Not
Cert prep drills service trivia; interviews ask you to size, cost, and defend a design. The five things being scored, and a costing script you can run.
VM, Container, or Serverless
The break-even calculation that decides between them, why serverless gets expensive at steady load, cold starts measured, and the questions each choice invites.
Storage Classes and the Egress Bill
Object, block and file storage, when a cheaper storage class costs more, retrieval fees and minimum durations, and the CDN arithmetic that pays for itself in a week.
VPCs and the Connectivity Debug Ladder
Subnets, route tables, security groups and NACLs, and the ordered checklist that finds why two things cannot talk — the most common hands-on cloud interview question.
IAM and Least Privilege
How a policy decision is actually evaluated, why an explicit deny always wins, roles versus long-lived keys, and the wildcard that looks scoped and is not.
Intermediate
For developers with core concepts down
Availability, Regions, and the Arithmetic of Nines
What an SLA number actually buys you, RTO versus RPO, why multi-region costs more than twice as much, and the failure modes redundancy does not fix.
Scaling, Queues, and Backpressure
Why autoscaling reacts too late, Little's law applied to a real queue, what a growing backlog actually means, and the retry storm that turns a blip into an outage.
The FinOps Round: Where the Money Goes
Reading a bill by line item, the commitment ladder priced out, the four wastes that account for most overspend, and unit cost as the metric that survives growth.
Advanced
Production-grade patterns for experienced engineers
A Full Architecture Design Round
One question worked end to end — clarify, size, sketch, fail it, cost it, trade off — with the weak version of each step shown alongside the strong one.
The Infrastructure-as-Code Round
Reading a Terraform plan for what it will destroy, state and locking, the drift question, and the review comments an interviewer is waiting to hear.