Curated videos, articles, and guides to help you prepare for interviews. Use our on-site quiz and flashcards, and refer to these external links when you want to go deeper.
Card of the day · Compute
Practice more flashcards →Live search filters by title, description, interview angle, and tags.
Official re:Invent keynotes, launches, and session recordings—useful for "what's new" and architecture discussions.
Interview angle: Expect questions on latest AWS launches, how you'd use new services in real projects, and trade-offs between new and existing options.
Key takeaways
Pillars: operational excellence, security, reliability, performance, cost. Used in design discussions.
Interview angle: Interviewers ask how you'd trade off cost vs performance or security, and how you apply the pillars to real architectures.
Key takeaways
Check your knowledge
3 quick questions based on this resource.
Recommended AWS course on Udemy for certification and hands-on cloud skills.
Interview angle: Demonstrates hands-on AWS experience; interviewers may ask you to walk through services you've used in labs or projects.
Key takeaways
Add your preferred Coursera course. Replace this URL with the actual course or specialization page.
Interview angle: Structured cloud and DevOps knowledge; interviewers expect you to connect course concepts to real-world scenarios.
Key takeaways
Solid foundation for shell, filesystem, and scripting—often tested in DevOps/SRE interviews.
Interview angle: Expect questions on shell commands, file permissions, piping, and simple scripts—often in live coding or whiteboard form.
Key takeaways
Official tutorial: build, run, and share containers. Essential for container-related questions.
Interview angle: Interviewers ask how you build and run containers, debug images, and use Docker in CI/CD.
Key takeaways
Official docs: pods, deployments, services, configmaps, and the control plane.
Interview angle: Expect questions on pods, deployments, services, and how you'd run and debug workloads in Kubernetes.
Key takeaways
Check your knowledge
3 quick questions based on this resource.
Write infrastructure as code for AWS: provider, resources, state, and workflows.
Interview angle: Interviewers ask how you manage IaC, state, and collaboration (e.g. remote state, workspaces, modules).
Key takeaways
Saga, CQRS, API gateway, service discovery, and other patterns with diagrams.
Interview angle: Design discussions often touch on service communication, consistency, and failure handling—these patterns give you the vocabulary.
Key takeaways
Free online book: SLOs, error budgets, on-call, postmortems, and automation.
Interview angle: SRE interviews focus on SLOs/SLIs, error budgets, blameless postmortems, and how you balance reliability with feature work.
Key takeaways
Check your knowledge
3 quick questions based on this resource.
Coding and behavioral prep, resume tips, and company-specific guides.
Interview angle: Covers coding rounds, system design, and behavioral questions—interviewers expect clear communication and structured answers.
Key takeaways
Resource naming, HTTP methods, status codes, versioning, and security—common backend interview topic.
Interview angle: Expect questions on designing or reviewing REST APIs: naming, status codes, versioning, and idempotency.
Key takeaways
OAuth flows, tokens, and security in plain language. Helps with auth/identity questions.
Interview angle: Auth is a common interview topic; expect questions on flows (e.g. authorization code), tokens, and secure implementation.
Key takeaways
Open-source guide to system design: scalability, load balancing, databases, caching, messaging.
Interview angle: Interviewers use system design to assess how you scale systems, choose databases, and handle consistency and availability.
Key takeaways