Interview Questions for a Scrum Master
Interview a scrum master by testing facilitation, servant-leadership, and the ability to improve delivery rather than just run ceremonies. Assess how they remove impediments, coach teams toward self-organization, run retrospectives that produce real change, interpret agile metrics like velocity and cycle time, and shield teams from disruption. Strong candidates make flow visible and grow team health, not control it.
Last updated
Run this interview to distinguish a true coach and impediment-remover from a ceremony scheduler. Use scenarios involving stalled teams, missed sprint goals, and stakeholder pressure to test judgment. The strongest scrum masters lead through influence and coaching, use metrics to diagnose flow rather than to police people, and create psychological safety so problems surface early and improvements actually stick.
Technical & Role-Specific
What to look for: Concrete facilitation techniques for planning, standups, reviews, and retros, with a focus on outcomes over going through the motions.
What to look for: Using metrics to diagnose predictability and flow rather than to compare or pressure individuals, and understanding their limits.
What to look for: Varied formats, getting to root causes, generating actionable items, and tracking follow-through across sprints.
What to look for: A systematic approach to surfacing blockers, escalating with stakeholders, and unblocking flow rather than logging issues passively.
What to look for: Practical understanding of more than one framework and choosing based on the team's work type rather than dogma.
What to look for: Clear role boundaries, facilitation of refinement, and keeping work ready while leaving prioritization decisions to the product owner.
Behavioral & Past Experience
What to look for: Coaching over directing, observable shifts in ownership and accountability, and patience with the team finding its own way.
What to look for: A specific blocker, the stakeholders involved, and a measurable or observable improvement in flow or predictability.
What to look for: Root-cause facilitation and a change that stuck rather than a one-off action item that faded.
What to look for: Creating psychological safety, surfacing issues early, and facilitating rather than imposing solutions.
Situational & Problem-Solving
What to look for: Shielding the team, managing stakeholder expectations, and protecting the sprint goal while staying collaborative.
What to look for: Investigating flow, dependencies, and team health with metrics as a signal, avoiding blame or arbitrary pressure to go faster.
What to look for: Conflict-resolution skill, neutral facilitation, and restoring a healthy working relationship rather than escalating to management first.
What to look for: Honest conversation about uncertainty, using metrics and forecasting, and protecting sustainable pace over false commitments.
What to look for: Refocusing the ceremony on the team's own coordination and impediments, reinforcing self-organization rather than control.
Collaboration & Culture
What to look for: Coaching, asking questions, and empowering the team rather than directing or becoming a bottleneck.
What to look for: Concrete practices that make it safe to raise problems, and modeling vulnerability and follow-through.
What to look for: Clear understanding of Scrum accountabilities and constructive collaboration across them.
Scrum Master interview scorecard
Score every candidate on the same criteria, immediately after the interview, using evidence you actually heard rather than an overall impression. Agree the criteria with the panel before the first interview — deciding what counts after you have met people is how the loudest interviewer wins the debrief.
| Criterion | Evidence to record | Score 1-5 |
|---|---|---|
| Technical & Role-Specific | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Behavioral & Past Experience | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Situational & Problem-Solving | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Collaboration & Culture | What the candidate actually said or did, in their own example — not your impression of it | 1 2 3 4 5 |
| Overall recommendation | Strong no / no / mixed / yes / strong yes, with the single reason that decided it | - |
Want this as a reusable document? Use the interview scorecard template.
Questions to avoid asking a Scrum Master
Exactly which questions are unlawful depends on where you are hiring, and the rules change — so treat this as the list of topics to route through your own employment counsel, not as a legal standard. The practical test that holds everywhere: if the answer could not change how the person does this job, you have no reason to ask it.
Related roles to hire
Frequently asked questions
What skills should a strong Scrum Master have?
How many interview rounds does hiring a Scrum Master usually take?
What is the most important quality to screen for in a Scrum Master?
Run these interviews structured, and compare candidates fairly
Pitch N Hire is an applicant tracking system with built-in interview scorecards. Load these questions into a scorecard so every interviewer assesses the same criteria and you can compare candidates side by side.
Free for 1 user · No credit card · Talk to a real hiring expert
See how much faster your team could hire
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
