Scrum master interview questions
The short answer
A scrum master interview asks what changed for the team because you were there. Running the events is expected; the questions go to an impediment you removed, a habit you helped change, a stakeholder you held back mid-sprint and how you knew the team was getting better. Interviewers listen for coaching and outcomes, and they are wary of velocity offered as an achievement.
Practice these questions in Claude with Interview Coach, free
How to use these questions
Each question comes with what a hiring manager usually listens for. Prepare one story per question from your own record: the board, the retrospective notes, the team's flow data, the working agreement. Tell it as the situation, what you did yourself, what changed and how you know. Use "I" for what you did and "the team" for what the team did. The difference is what the interviewer is listening for.
Behavioral questions
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: 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.
Tell me about a team habit you helped change. How did you know it had changed?
In the Interview Coach question bank
Listen for: the habit before and after, how you helped the team change it rather than ordering it, and the signal that showed it stuck.
Tell me about a project or a decision that did not go to plan. What was your part in it?
In the Interview Coach question bank
Listen for: a practice you introduced that did not work, your part in it, and what you changed. Pick a practice you really dropped, not a small adjustment.
Tell me about a retrospective that changed something real.
Listen for: the problem the team named, the action it chose, who followed it up, and what was different two or three sprints later.
Situational questions
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.
A senior developer skips every stand-up and says it is a waste of time. What do you do?
Listen for: curiosity first, the purpose of the event explained in the team's terms, and a willingness to change the format if the team agrees it is not working.
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).
Management asks you to compare the velocity of two teams. How do you respond?
Listen for: why story points do not compare across teams, and an offer of a measure that answers the real question behind the request.
Scrum master questions
How many teams did you serve at once, and what was the product?
Listen for: the number of teams, the product or domain, how distributed the teams were and at what stage. It sets the weight of the rest of your answers.
When did you advise a team against the framework by the book?
Listen for: the situation, why the standard practice did not fit, what you suggested instead and how it went. Interviewers listen for judgment, not loyalty to a framework.
Whom did you coach, and how did you know it worked?
Listen for: a person or a team, what they could do at the end that they could not at the start, and how you saw it.
Stakeholder questions
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: how you made the cost of the change visible, the product owner's role in the decision, and what happened to the sprint goal.
How did you help a product owner say no to a stakeholder?
Listen for: the request, the evidence you helped prepare, and that the product owner made the call. You support the decision; you do not make it for them.
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: who had to act outside the team, why they had no reason to, and the steps you took.
Metrics and evidence questions
Which measure did the team look at to see whether it was getting better, and where did the number come from?
Listen for: a flow measure such as cycle time, throughput or forecast accuracy, its starting point, and the tool that holds it. A figure the team's tool cannot show will be tested.
How did you know a change was the team's doing and not just a quiet quarter?
Listen for: what else changed in the same period, and an honest view of how much of the change you can attribute to the team's new practice.
How did you read team health, and what did you do with what you learned?
Listen for: the signals you used (retrospectives, surveys, attrition, onboarding time) and one action you took because of them.
Practice these with Interview Coach in Claude
Interview Coach has a scrum master track, which also covers agile coach titles. The questions marked above as in its bank come from it, and it adds questions that quote your own resume lines and the requirements of the posting.
- 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.
Resources
Your answers start from your resume. The resume guide for this role shows how to write each line so you can back it up.
- Resume guide: Scrum master resume guide
Questions
What do hiring managers listen for in scrum master interview answers?
They listen for change you helped cause: an impediment cleared, a habit changed, a flow measure that moved, a product owner who could say no. Descriptions of the events you ran tell them what the job was, not what you did with it.
Should I talk about velocity in a scrum master interview?
Only as a planning tool for one team, never as an achievement. If you want to show improvement, use a flow measure with a starting point and a source, and say what else changed in the same period.
How do I show impact if my team's work was hard to measure?
Describe the starting state and the end state in plain words, such as how long a release took or how often work came back. Name the record that shows it, even if it is the team's board or the retrospective notes. Never estimate a figure you cannot source.
Keep going
- Role hub: Scrum master resume and career help
- Related: Product owner interview questions
- Related: Delivery manager interview questions
- Guide: AI resume review: what Reed checks
Last updated: October 13, 2026