Tell me about being blocked on something only one unresponsive colleague could give you. Walk me through everything you tried.
Why this works
A stalled dependency is a small test with an honest reading: some candidates send the same email three times and file the missed deadline under someone else's name. "Everything you tried" invites the full sequence, showing whether they treat a colleague's silence as an excuse or as a problem to work.
Follow-up probes
- What did you try after the second nudge failed?
- What turned out to be competing for their attention?
- At what point did you involve anyone else, and how?
- What happened to your deadline in the meantime?
What good looks like
An escalating sequence of channels and framings rather than repeats, the ask made smaller and easier to answer, the block flagged early to whoever owned the deadline, and no bridge burned once it resolved.
Red flags
One email and a shrug with the outcome filed as the colleague's fault, or the opposite — an immediate cc to their manager; the colleague described with contempt; the ask never once adapted.
More Teamwork & collaboration questions
All 12 teamwork & collaboration questions
Related across competencies
Build the interview around it
One vetted question is an ingredient, not the meal. Plan the interview and three short steps will work out which competencies your role needs, no account required. Or subscribe and get new vetted questions and interview guides as we publish them.