Scrum master situational interview questions
The short answer
Situational questions start with "what would you do if" and describe a hard spot: a product owner who will not prioritize, a manager who wants velocity compared, a team that skips the retrospective. Interviewers listen for judgment and for a sequence: what you would look at first, who you would talk to, what you would not do. The strongest answers end with a short real example where you did exactly that.
Practice these questions in Claude with Interview Coach, free
How situational questions are judged
A situational question tests how you think when the facts are thin. The interviewer gives you a scene with gaps on purpose and listens for the questions you ask back, the order of your moves and the limits you set on your own role. A scrum master who jumps to a fix, or who takes a decision that belongs to the product owner, gives the answer away in the first sentence.
Situational and behavioral questions reward the same thing. The best way to answer "what would you do" is "here is what I would look at first, and here is a time I did". The real example turns an opinion into evidence, and it can be checked the same way a behavioral answer is: situation, your own action, result, record.
- Ask one question back. What is the sprint goal, how long has this gone on, who owns the decision. One good question shows you do not act on a headline.
- Name your first move. Not a plan with six steps: the first thing you would look at, and why that first.
- Say what you would not do. Decide for the product owner, compare teams by velocity, report a person to their manager first. Limits show you know the role.
- Close with a real case. One or two sentences from your own record. It is what the interviewer remembers.
How to use these questions
Under each question is what a hiring manager usually listens for. A scrum master's stories are easy to tell in the team's voice and hard to tell in your own, so go back to the board, the retrospective notes and the flow data, and mark in each story the moves that were yours: the question you asked, the person you went to, the measure you put on the wall. The team's part in one sentence, your part in order, then where the change shows.
Team situations
The team says the retrospective is a waste of time and wants to skip it. What do you do?
Listen for: curiosity about why, a look at what the last retrospectives produced, a change of format before a defence of the event, and a measure of whether actions got done.
A senior developer takes every story and the rest of the team waits for instructions. What do you do?
Listen for: a private conversation first, a look at how work is pulled, a change the team agrees to such as pairing or a pull rule, and the signal that the pattern changed.
The team's velocity keeps rising, but releases keep slipping. What do you look at?
Listen for: that velocity is not the goal, and a look at flow instead: work in progress, cycle time, the definition of done and what happens after the sprint ends.
Product owner situations
Your product owner is rarely available and the backlog is thin. What do you do this sprint?
Listen for: how you protect the sprint now, how you raise the gap with the product owner and their manager, and what you would not do: take over the product owner's decisions.
The product owner accepts stories without looking at them. What do you do?
Listen for: the risk you name (rework, a wrong feature shipped), the conversation with the product owner about what acceptance is for, and the change you propose to review.
Tell me about a time a stakeholder pushed work into a sprint midway. How did you handle it?
In the Interview Coach question bank
Listen for: a real case: how you made the cost of the change visible, the product owner's role in the decision, and what happened to the sprint goal.
Management situations
Management asks you to compare the velocity of two teams. How do you respond?
Listen for: why story points do not compare across teams, the question behind the request, and the measure you would offer instead.
A director tells you the team must commit to a fixed scope and date three months out. What do you say?
Listen for: a forecast from the team's own data with a range, the options when scope and date collide, and the conversation about what the director really needs.
Tell me about a time you had to get people to act when they did not report to you.
In the Interview Coach question bank
Listen for: a real case: who had to act outside the team, why they had no reason to, and the steps you took.
Judgment under pressure
Two team members argue in a stand-up and the rest go quiet. What do you do in the next ten minutes, and after?
Listen for: ending the public argument without taking sides, the separate conversations after, and what you bring to the retrospective only if both agree.
Tell me about an impediment that blocked your team for more than a sprint. What did you do?
In the Interview Coach question bank
Listen for: a real case: the impediment, why the team could not clear it alone, who could, what you did to get it cleared and what changed for the team afterwards.
Answers as written, and what the check says
Illustrative, not a real client. Each answer below replies to the question Interview Coach asks as "Tell me about a time a stakeholder pushed work into a sprint midway. How did you handle it?" and was sent on its own through the answer check. All four 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 the sales director pushed a demo feature into the sprint late in the second week, the cost of the change was put on the board and the options were taken to the director, and the sprint goal was delivered and the demo feature shipped in the next sprint, per the decision log. | No sentence says what you did yourself, with I. | Say which of these steps were yours, with I. |
| When the sales director pushed work into the sprint, we sized it, we re-planned, we swapped stories, we retested and we updated the forecast. I costed it and I took options to the director, and the goal was delivered, per the decision log. | 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 put the cost of the change on the board for the product owner and I took the options to the director with the product owner the same day, and the sprint goal was delivered and the demo feature shipped in the next sprint, per the decision log. | No context is set before the action. Add what was at stake. | Open with what was at stake before you acted. |
| When the sales director pushed a demo feature into the sprint late in the second week, I put the cost of the change on the board for the product owner and I took the options to the director with the product owner the same day, per the decision log. | No result is named. Say what changed. | Say what changed in the end, and where it shows. |
The check never adds a figure or a decision for you. If the sprint goal broke, say so, and say what the product owner chose and what the team recorded about the choice.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer to the same question 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 served a reporting team at a logistics software company, the sales director pushed a demo feature into the sprint on day seven of ten, for a prospect meeting the following week. I put the cost of the change on the board that morning: two committed stories out and the sprint goal gone, or the demo built from a prototype branch. I took both options to the director together with the product owner the same day and I asked them to choose, because the trade was theirs to make, not mine. They chose the prototype branch, the sprint goal held, and the feature shipped properly in the next sprint, per the sprint review notes and the release log. Before that quarter, late pushes had broken the goal in three of five sprints; after I started costing every push on the board, the next eight sprints lost the goal once, per the team's sprint report, and the director now brings prospect requests to refinement instead.
Why it works. The scene is set with the day and the reason. The actions are the speaker's own and leave the decision with the director and the product owner. The result is tied to named records and a before and after pair of sprint counts, which is what the evidence check reads.
Choosing your stories
- Keep a real case ready for each scene. Every situational question on this page has a behavioral twin. Prepare the story, then use it as the close of your answer.
- Pick cases where you stayed in role. You made the cost visible, asked the question, ran the conversation. The product owner or the manager chose.
- Pick one case where you were wrong. A situational interview often asks what you would do differently. A real example beats a hypothetical regret.
Your resume is where an interviewer picks these stories from, and a line such as "improved team velocity" invites the hardest version of these questions. Get a free AI review of your resume and see which lines Reed flags first.
Practice these with Interview Coach in Claude
Interview Coach asks the scrum master track of its question bank. A situational question is answered best with a real story that shows the same judgment; write that story the way you would say it and ask for a check.
- Paste your resume and the job posting. Interview Coach returns the lines a hiring manager is likely to ask about, each as a question that quotes your own line, with the points a strong answer covers.
- It matches the requirements of the posting to your resume and turns the gaps into questions to prepare.
- Write one answer at a time and ask for a check. It looks for a situation, your own action, a result and a before and after figure or a named record. It does not judge whether the story is true.
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.
Free in Claude, no account. We do not store the text you send through it.
Questions
Should I answer a situational question with a story from my past?
Yes, after you have said what you would look at first and what you would not do. The story is the evidence for your judgment; on its own it can sound like you did not hear the question.
What if I have never faced the situation described?
Say so, then reason through it out loud: what you would ask, what you would look at, who owns the decision. Interviewers use situational questions precisely to see thinking, and a plain "I have not faced this, here is how I would approach it" is a strong opening.
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, and it never adds a figure you did not give. You decide what to say.
Keep going
- Role hub: Scrum master resume and career help
- All questions: Scrum master interview questions
- Same role: Scrum master interview questions in healthcare
- Same role: Scrum master interview questions in fintech and banking
- Same role: Scrum master interview questions at a SaaS company
- Same role: Scrum master behavioral interview questions
- Resume guide: Scrum master resume guide
- Guide: AI resume review: what Reed checks
Last updated: October 15, 2026