How do you handle a critical blocked task?
This tests your proactivity, communication, and ability to manage dependencies. A great answer involves immediate investigation, clear async communication of status and impact, and actively driving the resolution by pulling in the right people.
What's really being asked
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.
The full answer
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.
The mistakes people make
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.
What usually comes next
"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).
A 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."
Interview question
Upon encountering a critical task blocker, what is the most effective initial course of action?
- a.Directly contact the individual or team responsible for the blocker to request immediate assistance.
- b.Conduct a brief self-investigation, then communicate the blocker, its impact, and potential resolvers in a public team channel.Correct
- c.Mark the ticket as "BLOCKED" and wait for the next team stand-up to discuss it.
- d.Immediately escalate to your manager, providing details of the blocker and its impact.
Why? this is the answer
The card emphasizes immediate self-investigation (15-30 mins) followed by clear, async communication in a public channel, stating the impact and identifying potential helpers. This proactive approach ensures the blocker is validated and the team is aware, driving resolution efficiently, rather than just directly contacting one person or waiting passively.
Just read this? Test yourself on what you have been reading.
- #agile
- #process
- #communication
- #problem-solving
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles