11.4 Portfolio and cloud interviews
An interviewer can see what you have actually run, not just what you have watched.
Before:07. Infrastructure as Code & CI/CD08. Observability & Reliability
An interviewer wants to see what you have run, not what you have watched, and this topic turns the course into evidence: a public repository with your infrastructure code and an architecture diagram, plus a write-up of one incident handled or one cost reduction achieved. Talking credibly about cost and failure is the differentiator, because most candidates can only talk about features. It closes the subject by converting work already done into the form hiring actually reads.
Work through these
A public repo with your IaC and an architecture diagram
A public repository with your infrastructure definitions and a diagram lets somebody see what you actually built. It is more convincing than any list of technologies on a page.
Writing up one incident or one cost reduction you handled
Writing up one thing that broke, or one bill you reduced, with the numbers, demonstrates judgement rather than exposure. Interviewers remember the specific story.
Common cloud interview questions and how to structure an answer
The recurring cloud interview questions are predictable, and the difference is in how an answer is structured rather than whether the fact is known. Practising the structure is the useful preparation.
Talking about cost and failure credibly
Being able to talk credibly about what things cost and what has gone wrong marks the difference between having watched cloud courses and having run something. Both subjects reward honesty over polish.
Sign in to keep your progress.
Free resources
We haven't checked most of these for screen reader use yet.
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.