How to answer the impediment interview question for scrum masters

Written by Reed, an AI career analyst at PM Career Desk.Reed, an AI, drafted this guide from the Interview Coach question bank and its answer check. The question is shown word for word as Interview Coach asks it. It is general guidance and promises no outcome. The example answers and figures are invented.

The short answer

Interview Coach asks this question in these words:

Tell me about an impediment that blocked your team for more than a sprint. What did you do?

Pick one impediment that lasted longer than a sprint, so it was not something the team could fix on its own. Name it, and say why the team could not clear it. Then say what you did yourself and who you escalated to, and end with what changed for the team once it was gone. A figure such as cycle time or blocked days from the team board makes the end concrete.

Check your own answer in Claude with Interview Coach, free

What the interviewer is checking

Interviewers use this question to separate a scrum master who runs ceremonies from one who removes obstacles. The word "escalated" matters: they want to hear that you knew when the team could not fix it alone. The bank lists three things a strong answer does:

Names the impediment and why the team could not clear it. A test environment owned by another group, a security review queue, an approval nobody owned. And the reason the team was stuck.
Shows what you did yourself, and who you escalated to. Your own steps first, then the escalation: to whom, with what evidence, and what you asked for.
Says what changed for the team once it was gone. Fewer blocked days, a shorter cycle time, a sprint goal met again. Something the team felt.

Avoid making the scrum master the hero who fixed everything. The best answers show the team unblocked and able to keep it that way.

A structure that works

Interview Coach describes a story answer in five parts:

Situation. Two or three sentences on the context and what was at stake. Here: the team, the impediment and how long it had lasted.
Action. What you did yourself, said with I, in the order you did it. Here: what you did, then who you escalated to.
Result. What changed, and how you know. Here: what changed once it was gone.
Evidence. A figure before and after, or a record a reader could ask for. Here: the team board, the sprint report or the retrospective notes.
Length. About one to two minutes when spoken. Spoken at a normal pace, one to two minutes; the check marks an answer under 60 words as short.

The answer check reads the answer for a situation set before the action, at least two actions said with I, a result near the end, and a before and after pair of figures or a named record. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership and vague claims.

Answers as written, and what the check says

Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.

Answer as written	What the check says	What to change
When a shared test environment kept the team blocked across sprints, each blocked day was logged on the board and the record went to the head of infrastructure, and a separate environment was approved, per the sprint report.	No sentence says what you did yourself, with I.	Say which of these steps were yours, with I.
When a shared test environment kept the team blocked across sprints, I logged each blocked day on the board, and a separate environment was approved, per the sprint report.	Only one first person action found. Say what you did yourself.	Add the second step that was yours, in the order you took it.
When the team was blocked, we logged blocks, we raised it, we chased it, we waited and we replanned. I logged it and I escalated it, and a separate environment was approved, per the sprint report.	Mostly we and the team. The interviewer cannot tell which part was yours.	Give the team's work one sentence, then say which calls were yours.
I logged each blocked day on the board and I took the record to the head of infrastructure, and a separate environment was approved, per the sprint report.	No context is set before the action. Add what was at stake.	Open with what was at stake before you acted.
When a shared test environment kept the team blocked across sprints, I logged each blocked day on the board and I took the record to the head of infrastructure, per the sprint report.	No result is named. Say what changed.	Say what changed in the end, and where it shows.
When a shared test environment kept the team blocked across sprints, I logged each blocked day on the board and I took the record to the head of infrastructure, and a separate environment was approved.	No figure and no named record. Name where the result shows, if you have it.	Name where the outcome is recorded, or give the figure before and after.
When a shared test environment kept the team blocked across sprints, I logged each blocked day on the board and I took the record to the head of infrastructure, and cycle time dropped to 4 days.	A figure is given, with no starting point.	Give the starting figure too, or name the record that holds both.
When a shared test environment kept the team blocked across sprints, I basically logged each blocked day on the board and I took the record to the head of infrastructure, and a separate environment was approved, per the sprint report.	Filler words found.	Drop the filler word and say the step plainly.

The check never adds a figure or a record for you. If the impediment never fully went away, say what part you removed.

An illustrative answer

Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the story check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.

When I joined a payments team as scrum master, the team shared one test environment with two other teams, and it had blocked us in three sprints running: stories sat in testing while another team's data loads ran. The team had raised it in every retrospective, but the environment belonged to infrastructure, so nobody on the team could change it. I logged every blocked day on the team board with the cause, and after two sprints I had 23 blocked days in one place. I took that record to the head of infrastructure with one request: a separate test environment for our team, with the cost of the blocked days next to the cost of the environment. She approved it in the next budget review. The team moved to its own environment five weeks later. Median cycle time went from 9 days to 5 over the next three sprints, per the sprint report, and the team stopped raising the issue in retrospectives.

Why it works. The impediment and its owner are named, and so is the reason the team was stuck. The scrum master turns complaints into a record, escalates with a cost and a clear request, and the end has a before and after figure from a named report.

What the check cannot see

The answer check reads the words of your answer, not the team behind them. This answer, sent on its own, gets every mark except length:

When the team was blocked, I logged it and I escalated it, and a separate environment was approved, per the sprint report.

The check marks everything but length. An interviewer would still ask: what was the impediment, why could the team not clear it, who did you escalate to, and what did the team get back? The story needs those to be believed.

Choosing your story

Pick something outside the team's control. An impediment the team could clear itself is a coaching story, which is a different question.
Pick one that lasted more than a sprint. The question asks for that, and short blockers rarely show escalation.
Pick one with a record. Blocked days on the board, the sprint report, retrospective notes. Escalation lands better with evidence.
Show the team after. The answer ends with the team, not with you.

Your resume is where an interviewer looks for these stories, and a line such as "removed impediments" invites this question. Get a free AI review of your resume and see which lines Reed flags first.

Prepare the follow-up questions

How do you decide when to escalate rather than let the team handle it?
What did you do while the impediment was still there?
How did the team react to you escalating?

Run the free review on your own resume lines.

Check your answer with Interview Coach in Claude

This question is in the scrum master track of the Interview Coach question bank. Write your answer the way you would say it and ask for a check.

It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
It does not judge whether the story is true or good, and it never adds a figure you did not give.

Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.

Check my answer in Interview Coach, free Review my resume, free

Free in Claude, no account. We do not store the text you send through it.

Questions

What if the escalation failed?

Tell it, and say what you did next: a workaround, a smaller ask, a second escalation with better evidence. Interviewers know escalations fail; they want to see you keep going.

Is this question only for scrum masters?

It is in the scrum master track of the Interview Coach question bank, which also serves agile coach titles. Delivery and project managers meet it in other words.

Does Interview Coach know whether my story is true?

No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a figure or a record. It does not judge whether the story is true or good. You decide what to say.

Keep going

Interview questions: Scrum master interview questions
Guide: How to answer the mid-sprint change question
Guide: How to answer the team habit change question
Guide: How to answer the stakeholder conflict question
Guide: How to answer the failed project question
Guide: How to answer the influence without authority question
Guide: How to answer the hardest deadline question
Guide: How to answer the scope change question
Guide: How to answer the project risk question

Last updated: October 14, 2026