How do you escalate a blocking external dependency?
Tests your ability to quantify impact, show ownership, and empower leaders. A great answer details the business cost, documents your due diligence, and defines a clear 'ask' for the leader.
What's really being asked
This question assesses your maturity beyond just coding. It tests your ability to take ownership of a problem, quantify its business impact, and understand the role of an agile leader as a facilitator, not just a task-master. Interviewers are looking for evidence that you can escalate problems constructively and with data, rather than just complaining or waiting to be told what to do. It separates senior engineers who solve systemic problems from junior ones who only solve technical tasks.
The full answer
An excellent answer provides a structured plan with three key components. First, quantify the impact: state the cost of the block in concrete terms like story points delayed (e.g., "13 points this sprint"), feature deadlines at risk, or even engineering-hours wasted (e.g., "40 engineer-hours lost so far"). Second, document your due diligence: provide a concise summary of every action you've already taken, including links to tickets, names of people contacted, and dates of communication attempts. Third, define a clear 'ask': specify exactly what you need the leader to do. This isn't 'please fix it,' but rather 'can you use your 1:1 with the other team's EM to get ticket #XYZ prioritized?' The key difference from traditional management is that you are providing ammunition for your leader to act, not abdicating the problem to them.
The mistakes people make
A frequent red flag is escalating with emotion or vague complaints, such as "The other team is always slow" or "They're ignoring us." This shows a lack of professionalism and data-driven thinking. Another mistake is showing no ownership, implying it's the Scrum Master's or EM's job to have already known about and fixed the problem. A senior engineer is expected to try resolving issues at the lowest possible level first before escalating. Finally, asking the manager to 'handle it' without providing context or a specific request is a junior-level approach that fails the test.
What usually comes next
Expect follow-up questions like "What would you do if your EM was unable to resolve the impediment?" which tests your understanding of broader escalation paths. Another common one is "How would you work to prevent this type of dependency from blocking your team in the future?" which probes your strategic thinking about architectural solutions (like an anti-corruption layer), cross-team planning, or formalizing Service Level Agreements (SLAs).
A concrete example
"Our team was blocked by the Auth service, which needed to add a new scope for our feature. After two days with no reply on their public Slack channel, we filed a ticket. A week later, the ticket was still unassigned. We calculated this blocked 2 engineers and 15 story points, putting our quarterly goal at risk. I prepared a one-page summary for our EM with the timeline of events, a link to the ticket, and the calculated impact. My specific ask was: 'Can you bring this up in the weekly engineering leadership sync to get it prioritized?' This armed my EM to advocate for us effectively."
Interview question
When escalating a blocking external dependency to a leader, which approach demonstrates the MOST effective and mature problem-solving?
- a.Quantify the business impact, summarize actions already taken, and propose a specific, actionable request for the leader.Correct
- b.Inform the leader that the other team is consistently slow and ask them to "handle it" as part of their management duties.
- c.Document all communication attempts, explain the technical root cause, and request the leader's direct intervention.
- d.Clearly state the problem, list all team members affected, and ask the leader to intervene.
Why? this is the answer
An effective escalation quantifies the business impact, documents due diligence (actions taken), and provides a clear, specific 'ask' for the leader to act upon. Option B represents a common wrong answer by being vague and lacking ownership, while options A and B miss crucial elements like quantifying business impact or providing a specific, actionable request.
Just read this? Test yourself on what you have been reading.
- #agile
- #scrum
- #stakeholder management
- #escalation
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