How do you handle a critical blocked task?

WHAT THIS TESTS: This question evaluates your sense of urgency, ownership, and communication skills within a team context. The interviewer isn't just checking if you know how to mark a ticket as "blocked." They are testing your ability to act immediately instead of passively waiting, clearly articulate the impact of the blocker, drive the resolution process even if the solution lies elsewhere, and manage communication effectively across different channels.

A GOOD ANSWER COVERS: A strong answer outlines a multi-step process. First, immediate self-service investigation: spend 15-30 minutes confirming it's a true blocker and you haven't missed something obvious. Second, immediate communication: post in a relevant public channel (e.g., team Slack) stating the task, the blocker, the impact ("this delays feature X"), and who you believe can help. Third, formalize the state: update the ticket with a "BLOCKED" label and a comment summarizing the issue and linking to the async discussion. Fourth, actively engage: directly message or call the person/team responsible for the block, offering to pair or provide context to expedite their work. Finally, prepare a concise update for the next stand-up, focusing on the resolution plan.

COMMON WRONG ANSWERS: A major red flag is passivity. Weak answers describe a process of waiting, for example: "I'd mark the ticket as blocked and wait for the next daily stand-up to tell everyone." This shows a lack of urgency and ownership. Another poor response is just saying "I'd tell my manager." This escalates prematurely and abdicates your responsibility to solve problems at your level first. Finally, failing to mention the impact on the sprint goal or release is a missed opportunity to demonstrate strategic awareness.

LIKELY FOLLOW-UPS: "What if the person blocking you is unresponsive?" (Tests your escalation path: their manager, your manager, public channel reminders). "How does this process change if the blocker is an external team?" (Tests handling of formal communication and setting expectations). "How would you prevent this type of blocker from happening again?" (Tests ability to think systemically via retrospectives).

ONE CONCRETE EXAMPLE: "A task to deploy a new microservice was blocked by the infra team, who hadn't provisioned database credentials. I spent 15 minutes checking runbooks to ensure it wasn't a self-service step. Then, I posted in our shared #dev-infra-support channel: '@here, our payments service deployment (TICKET-123) is blocked on DB creds. This blocks the entire Q3 payment feature. @InfraTeam, can someone help?' I tagged the ticket, then DM'd the infra team's lead with a link. This got a response in under 10 minutes, whereas waiting for stand-up would have cost half a day."