How Scrum Master interviews work
Scrum Master interviews test Agile and Scrum knowledge, facilitation and coaching skills, conflict resolution, and metrics understanding. Most interviews include a mix of theoretical Scrum knowledge questions and scenario-based behavioral questions. Senior Scrum Master interviews go deeper on organisational change management and scaling frameworks (SAFe, LeSS, Nexus).
Interviewers distinguish between candidates who know Scrum theory and those who have actually facilitated teams through difficult situations. The behavioral component matters as much as the theoretical one. Prepare examples from real teams where you removed blockers, facilitated difficult retrospectives, or helped a team through conflict.
Agile and Scrum theory questions
"What is the difference between Scrum and Kanban, and when would you recommend each?" Scrum uses fixed-length sprints with defined ceremonies and roles, making it suitable for teams with iterative product development. Kanban is a continuous flow system with no fixed iterations, suited to teams with unpredictable or support-heavy work. Some teams use a Scrumban hybrid. The key is choosing the framework that fits the work type, not applying Scrum universally because it is more well-known.
"What is the purpose of a Definition of Done and how do you establish one?" The Definition of Done (DoD) is a shared understanding of what completed work looks like. It sets a quality standard that every increment must meet before it can be shipped. A good DoD is established collaboratively with the team, includes testing and documentation standards, and is revisited periodically as the team matures. A DoD that no one remembers is not doing its job.
Ceremony facilitation questions
"How do you run a retrospective for a team that always says everything is fine?" Teams that say everything is fine are usually avoiding something uncomfortable. Techniques to surface real issues include: using anonymous input tools before the session, varying the format (sailboat, mad-sad-glad, 4Ls), focusing the retrospective on a specific recent event rather than the general sprint, and creating psychological safety by sharing your own observation first. Show that you treat a flat retro as a diagnostic rather than accepting it at face value.
"Walk me through how you facilitate a sprint planning session when the team consistently overcommits." Overcommitment usually reflects optimism bias, pressure from management, or a poorly calibrated velocity. Address it by reviewing historical data (what the team actually completed in similar sprints), using story points anchored to reference stories the team agrees on, and making the consequences of overcommitment visible in the retrospective. Coach the team to own the forecast rather than letting it be set for them.
Removing blockers and impediments
"Tell me about the most significant impediment you removed for a team." Good impediment removal stories involve issues that span team boundaries: dependencies on another team, infrastructure delays, unclear requirements from stakeholders, or organisational policies that slowed delivery. Show that you escalated appropriately, involved the right people, and tracked the resolution through to completion rather than just flagging the issue.
"How do you handle a situation where a blocker is coming from someone who has more authority than you?" Scrum Masters rarely have formal authority. Show that you frame impediment removal in terms of delivery impact rather than process compliance, that you build relationships with stakeholders before you need something from them, and that you use data to make the cost of the blocker visible. Escalating to your manager is sometimes necessary but show that you exhaust influence-based approaches first.
Team dynamics and conflict questions
"How do you handle a high-performing developer who dismisses Agile ceremonies as a waste of time?" Show that you listen to the specific concern rather than defending the ceremony. Often a developer who skips retrospectives has had bad experiences with unproductive ones. Show what a well-run ceremony looks like by facilitating it effectively, involve the developer in designing the format, and link the ceremony outcomes to things they care about: fewer interruptions, faster delivery, less rework.
"Describe a time you coached a team through significant interpersonal conflict." Scrum Masters are expected to create psychological safety and address conflict before it affects delivery. Show that you addressed conflict directly (not by hoping it resolved itself), involved both parties in finding a solution, and created team agreements that prevented similar issues from recurring. Be honest about how difficult it was and what you learned.
Metrics and reporting questions
"What metrics do you track for a Scrum team and how do you use them?" Velocity (story points completed per sprint) for capacity planning, burndown for in-sprint progress tracking, cycle time for understanding flow efficiency, and defect rate for quality trends. Metrics are tools for the team to improve, not weapons for management to evaluate performance. Show that you present metrics transparently and use them to start conversations about improvement rather than to assign blame.
"How do you report sprint progress to stakeholders who do not understand Agile?" Translate into business language: what was delivered this sprint, what is the current status toward the release goal, and what are the risks to the timeline. Use visual formats where possible. Avoid Agile jargon with non-Agile stakeholders and focus on outcomes (what the customer can now do) rather than process (ceremonies completed, velocity achieved).