tideline

live · checked 03:02 UTC

Cloud and DevOps interview preparation

General preparation, not from any one company

Cloud, DevOps and site reliability interviews test how you run systems: automation, reliability, security and what you do when things break. Expect hands-on questions about the tools in the posting.

  1. Infrastructure as code

    What they’re checking: Whether you build environments that can be repeated, reviewed and rolled back, rather than changed by hand.

    • How would you structure infrastructure code for three environments that should stay the same?
    • A change applied cleanly in staging and failed in production. How do you find out why?

    How to prepare: Be ready to sketch one setup you’ve built: what was in code, what wasn’t, and how a change reached production.

  2. Reliability and incidents

    What they’re checking: How you think about uptime, alerts that matter, and learning from failure without blame.

    • How do you decide what deserves a page in the middle of the night?
    • Walk me through an incident you handled, from the first alert to the review afterwards.

    How to prepare: Prepare one incident in the STAR shape, including what you changed so it wouldn’t happen again.

  3. Pipelines and releases

    What they’re checking: Whether you can ship often and safely: tests, staged rollouts, and a way back.

    • Describe a deployment pipeline you’d trust. Where would it stop a bad release?
    • How would you roll out a risky change to a service with heavy traffic?

    How to prepare: Know the release steps of a pipeline you’ve worked on, and one thing you would improve in it.

  4. Containers and orchestration

    What they’re checking: Practical understanding of how services are packaged, scheduled and scaled, beyond the tool names.

    • A container keeps restarting. What do you check, in what order?
    • How would you decide how much memory and CPU a service gets?

    How to prepare: Review the basics of the platform in the posting, and be honest about which parts you’ve used yourself.

  5. Security and cost

    What they’re checking: Whether you treat access, secrets and spending as part of the job rather than someone else’s problem.

    • How do you keep secrets out of code and logs?
    • The cloud bill doubled last month. How do you find out why?

    How to prepare: Have one example where you reduced access, risk or cost, with what you measured before and after.

Answering well

For “tell me about a time” questions, the STAR shape keeps an answer clear: the situation, your task, the action you took, and the result, with what you learned. Use your own stories; there is no right script to memorise.

Companies differ: check what each one publishes about its own interviews before you prepare for it.