26 questions · Scrum Master

Scrum Master Interview Questions

A hiring manager's question bank for Scrum Masters — the Scrum framework, facilitation, servant leadership, removing impediments, and navigating conflict. Built to separate people who recite the Scrum Guide from people who actually make a team faster and happier.

A Scrum Master is one of the easiest roles to fake in an interview and one of the most valuable to get right, because a great one quietly unblocks a whole team while a weak one becomes a ceremony administrator who slows everyone down. Knowing the framework is table stakes — the events, the roles, the artifacts, the difference between a Scrum Master, a Product Owner, and a manager — but reciting the Scrum Guide proves nothing about whether someone can coach real humans. The stronger signal is servant leadership and facilitation: does the candidate see their job as serving the team rather than commanding it, do they run a retrospective that surfaces honest problems instead of going through the motions, and can they explain how they made a specific team better? You want concrete stories about removing impediments, protecting the team from mid-sprint scope changes, coaching a Product Owner on a messy backlog, or handling the developer who dominates every standup. Metrics awareness matters too — velocity as a planning aid, not a productivity weapon, and the maturity to push back when leadership wants to weaponise it. Above all, this is a people role, so how a candidate handles conflict, influences without authority, and balances process against pragmatism tells you more than any certification. The questions below run from framework knowledge through facilitation and servant leadership into real-world conflict and metrics. Pair a couple of framework questions with several behavioural scenarios, and you will quickly tell whether someone has genuinely served teams or just collected a certificate.

How to use these questions

Choose six to eight questions, leaning heavily on the behavioural categories rather than framework trivia. Confirm they know the mechanics with one or two Framework questions, then spend most of the interview on Facilitation, Servant Leadership, and Conflict scenarios. Follow every answer with "tell me about a specific time" — a real Scrum Master answers with stories, not the Scrum Guide.

Scrum Framework

  1. Walk me through the Scrum events and the purpose of each — what breaks if you skip one?
  2. What is the difference between the roles of a Scrum Master, a Product Owner, and a development team?
  3. What are the three Scrum artifacts, and what does each commit to?
  4. What is the difference between the product backlog and the sprint backlog?
  5. What is a Definition of Done, and why does the team, not the Scrum Master, own it?
  6. How is Scrum different from Kanban, and when might Kanban fit a team better?
  7. What does "potentially shippable increment" really mean?

Facilitation & Ceremonies

  1. How do you run a retrospective that surfaces real problems instead of the same surface complaints?
  2. A daily standup has turned into a status report to you. How do you fix it?
  3. How do you facilitate sprint planning so the team commits to realistic work?
  4. How do you handle a sprint review where stakeholders keep requesting new scope?
  5. How do you keep meetings focused without shutting down honest discussion?
  6. What do you do when the team consistently overcommits and misses the sprint goal?
  7. How do you help a team that treats estimation as a promise rather than a forecast?

Servant Leadership & Impediments

  1. What does servant leadership mean to you, and how is it different from managing?
  2. Tell me about a significant impediment you removed for a team.
  3. How do you protect the team from mid-sprint scope changes without alienating stakeholders?
  4. How do you coach a Product Owner whose backlog is a mess?
  5. How do you help a team improve without dictating how they should work?
  6. How do you influence people when you have no authority over them?

Conflict, Metrics & Judgement

  1. How do you handle a team member who dominates every discussion?
  2. Two developers strongly disagree on an approach and it is blocking work. What do you do?
  3. Leadership wants to use velocity to compare and rank teams. How do you respond?
  4. What metrics do you find genuinely useful, and which do you distrust?
  5. Tell me about a time you failed as a Scrum Master. What did you change?
  6. When is it right to bend the process, and when do you hold the line?

Tips for interviewing Agile / Scrum candidates

  • Lean on behavioural stories; framework recall is easy to fake, but real facilitation experience is not.
  • Reward candidates who talk about serving the team; anyone who describes commanding it misunderstands the role.
  • Probe the velocity-as-a-weapon question hard; how they protect a team from misused metrics reveals their spine.
  • Ask for a specific impediment they removed — vague answers usually mean thin real experience.
  • Watch how they handle conflict scenarios; this is a people role and diplomacy is the core skill.
  • Do not over-weight certifications; a CSM or PSM is a baseline, not proof of coaching ability.

Frequently asked questions

Hiring a Scrum Master? JuggleHire ranks, screens, and schedules candidates for you.

JuggleHire goes beyond simple job posting. Leverage custom forms, powerful screening filters, and automated social media previews to find the perfect fit for your team.