JuniorBehavioural

Tell me about a time you helped a teammate who was stuck or blocked. What did you actually do?

What they are really testing: They want to see whether you notice other people at all, and whether your help unblocks the person or just takes the work away from them.

A real interview question

Tell me about a time you helped a teammate who was stuck or blocked. What did you actually do?

What most people say

drag me

I am a team player, so whenever someone is stuck I always jump in and help them out. I like helping people.

It is a personality claim with no story, no specifics, and no evidence that anyone was actually unblocked.

The follow-ups they ask next

  • What if the person does not want your help?

    Offer once, make it low pressure, and leave a written pointer instead of pushing.

  • How do you help without doing their work for them?

    Say you keep your hands off the keyboard and ask questions until they find it.

  • How did you know they were stuck?

    Point at a concrete signal, a repeated standup update or a stale pull request.

What the interviewer is listening for

  • Names the person and the exact technical block, not a vague description
  • Separates teaching from taking over the work
  • Fixes the system, for example the onboarding doc, not just the incident
  • Has a number attached to the outcome

What sinks the answer

  • Answers with a personality trait instead of a story
  • Takes over and solves it silently so the teammate learns nothing
  • Cannot say what the teammate was actually stuck on
  • Frames the teammate as slow or incompetent

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 big example of this yet, but here is the closest thing and how I would reason about it. In my last project someone was blocked on ..., I would first ask them to show me what they see rather than guess, then ...

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