Top 20 Scrum Master Interview Questions (and How to Answer Them)

Scrum Master interviews test three layers: do you know Scrum as written, can you handle messy real-team situations, and can you influence an organisation without authority. Here are twenty questions that come up constantly, grouped by layer, with what a strong answer contains.

Framework knowledge

1. What is empiricism and why does Scrum depend on it? Name the three pillars — transparency, inspection, adaptation — and connect them to a concrete event (the Sprint Review inspects the Increment; the Retrospective adapts the process).
2. What is the Scrum Master accountable for? The team's effectiveness — not velocity, not delivery dates, not people management.
3. Walk me through the five events and their purpose. Keep each to one sentence; interviewers are checking precision, not stamina.
4. What are the three artifact commitments? Product Goal, Sprint Goal, Definition of Done — and why each keeps its artifact honest.
5. What happens to incomplete work at the end of a Sprint? It returns to the Product Backlog for reordering. It is never automatically rolled into the next Sprint.
6. Can a Sprint be cancelled? By whom? Only the Product Owner, only if the Sprint Goal becomes obsolete.

Situational judgment

7. A Developer consistently dominates the Daily Scrum. What do you do? Strong answers escalate gently: observe, coach privately, change the format (walk the board instead of round-robin), never humiliate publicly.
8. The Product Owner keeps changing priorities mid-Sprint. Explore why — real market pressure or missing refinement discipline? Protect the Sprint Goal, coach the PO on the cost of churn, propose shorter Sprints if volatility is genuine.
9. Management asks you for individual performance reports. Explain the damage to self-management and offer team-level outcome metrics instead. Interviewers want to see you hold the line diplomatically.
10. The team says the Retrospective is a waste of time. That's data. Vary the format, make improvement actions visible in the next Sprint Backlog, and measure whether anything actually changes — boredom usually means no follow-through.
11. Two Developers are in open conflict. Address it early and privately; facilitate a conversation about working agreements, not personalities. Unresolved conflict is an impediment like any other.
12. The team wants to skip the Sprint Review because "there's nothing to show". Dig into why there's no Done increment — that's the real problem, usually a weak Definition of Done or overcommitment.

Organisational coaching

13. How would you introduce Scrum to a sceptical department? Start with one team and a real problem, make results visible, let pull replace push.
14. How do you handle dependencies on non-Agile teams? Make them visible early, negotiate interfaces, escalate structurally (not per-ticket) when the pattern repeats.
15. What metrics would you show leadership? Outcome and flow measures — cycle time, escaped defects, goal success — never individual velocity comparisons.
16. How is a Scrum Master different from a project manager? Accountability for team effectiveness versus accountability for scope/schedule/budget; influence versus authority.
17. How do you coach a Product Owner who acts as a proxy for ten stakeholders? Help them build a real ordering model (value, risk, cost of delay) and the authority to say no.
18. Tell me about a failed improvement you drove. What did you learn? Have a real story. Interviewers trust scars more than triumphs.

Curveballs

19. Is velocity a good performance measure? No — it's a planning signal, local to one team, trivially gamed. Expect a follow-up on what you'd use instead.
20. Would you ever recommend a team stop using Scrum? Yes — for flow-based operational work, Kanban may fit better. Knowing the framework's limits is senior-level judgment.

How to prepare

Interviewers can tell the difference between memorised definitions and lived understanding within three questions. Structured training with role-plays — like the CSM course — builds the situational fluency the middle section tests; the Advanced CSM goes deeper on coaching and facilitation. Review the full syllabus in our CSM guide.

Frequently asked questions

Do I need a certification to get interviews?

Many enterprise recruiters filter on CSM or PSM, so a certification gets you into more conversations — but the interview itself is won with situational answers.

How technical will the questions get?

For software teams, expect enough to test literacy — CI/CD, technical debt, testing basics — not coding puzzles.