JuniorBehavioural

Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?

What they are really testing: They are testing your self rescue loop: how long you thrash before changing approach, and whether you can make progress without a rescuer. They also want to see judgement about when being blocked becomes a thing to escalate.

A real interview question

Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?

What most people say

drag me

There was no one around so I waited until the next day when my team lead came online and then he explained it to me.

Waiting is not an action, it shows no attempt at self rescue and it tells the interviewer your throughput is capped by someone else's calendar.

The follow-ups they ask next

  • How long do you thrash before you change approach?

    Give a real time box, for example thirty to forty five minutes, then you either change tactic or write up what you tried.

  • When does being blocked become something you escalate rather than solve?

    Tie it to impact and reversibility, for example anything touching production data or money goes up rather than being guessed at.

What the interviewer is listening for

  • Turns confusion into a testable hypothesis quickly
  • Uses git history, logs, tests and source as substitutes for a person
  • Makes the experiment cheap and reversible before touching production
  • Writes up the findings so the absent expert can verify later

What sinks the answer

  • Waited for someone to come back and did nothing meanwhile
  • Guessed and applied changes straight to production
  • Never says how long they were stuck
  • Hid the workaround instead of documenting it

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 had a full blackout like that, but my loop when I am stuck alone is: form one testable guess, look for evidence in git history and logs, and time box it. The closest I have come was ...

Keep going with behavioural

All 336 cloud engineer questions

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