Everything on your CV is labs and personal projects. You have never run anything in production. Why should we take that risk?
What they are really testing: They are testing whether you understand what production actually means, on call, blast radius, other people's money, or whether you think a passing terraform apply is the same thing.
A real interview question
Everything on your CV is labs and personal projects. You have never run anything in production. Why should we take that risk?
What most people say
drag me
“I know I have not worked in production but I am a fast learner and I am very passionate, so I am sure I would pick it up quickly.”
It concedes the weakness and then offers only enthusiasm to cover it, so the interviewer is left with exactly the doubt they started with and no evidence to argue against it.
The follow-ups they ask next
What do you think would surprise you most about our production environment?
Answer with scale and blast radius, the number of dependent services and the fact that your mistake now affects other teams, not just you.
How would you approach your first change to production here?
Small, reversible, reviewed, in a low traffic window, with a rollback tested first and someone watching. Say you would ask what normally breaks.
Have you ever been on call?
If no, say no. Then describe what your closest equivalent was and what you already do, alerting, a runbook, a known rollback.
What the interviewer is listening for
- Concedes the gap honestly instead of arguing with the premise
- Has one project where real users felt a real failure
- Describes a fix that outlived the incident, such as staging or a rollback path
- Understands blast radius as the real difference, not tooling
What sinks the answer
- Claiming labs are basically the same as production
- Enthusiasm and fast learner as the entire defence
- No story where anything they built ever broke
- Cannot say what they would do differently on a real change
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I have not run production at your scale, so let me tell you the closest thing I have. Here is a project where real people depended on me, here is the day it broke, and here is what I changed because of it.”
Keep going with behavioural
Foundation
Tell me about a time you had to learn a new technology quickly. How did you go about it?
Foundation
So, why cloud? You have not worked in cloud before, so walk me through what actually pulled you here.
Foundation
Why are you leaving your current job?
Foundation
Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?
Junior
You join a team and inherit a service with no documentation and the original author has left. Walk me through your first week.
Junior
Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free