Score my profile

Profile

Posts and content

Jobs and resume

Outreach and networking

Images and files

Scrum Master interview questions

Scrum Master interviews test whether you run ceremonies or change outcomes, and the questions are built to tell those two candidates apart. Expect behavioral stories about resistant teams and stuck impediments, craft questions on velocity, estimation, and refinement mechanics, and scenarios where the framework collides with a strong-willed product owner or another team's priorities. Interviewers listen for diagnosis before prescription, and for evidence that delivery got more predictable on your watch. Reciting the Scrum Guide earns nothing, since everyone in the room has read it.

Behavioral
1. Tell me about a team that resisted Scrum. What was really going on, and what changed?
Strong answers cover: Naming the real cause before prescribing anything, often ceremony fatigue or a bad prior rollout, then the small early win that bought trust and what the team does differently now.
Behavioral
2. Describe an impediment you could not remove yourself. How did you handle it?
Strong answers cover: Recognizing the difference between a team-level blocker and an organizational one, choosing who to escalate to and how to frame the cost, and keeping the team shipping while it dragged on.
Behavioral
3. Tell me about a retrospective format that stopped working. What did you change?
Strong answers cover: Honest recognition that format was rarely the real problem, safety or follow-through was, plus a concrete fix like one owned action per sprint or tracking actions publicly until closed.
Role craft
4. What do you use velocity for, and what do you refuse to use it for?
Strong answers cover: Velocity as a planning input for one team over time, never a performance metric and never compared across teams, ideally with a story of pushing back when a manager tried to use it that way.
Role craft
5. Walk me through how you run backlog refinement so sprint planning stays short.
Strong answers cover: A working rhythm of weekly refinement, a definition of ready applied without ceremony worship, stories sized before planning day, and a measured result such as shorter planning or less carryover.
Role craft
6. How would you fix estimation on a team whose story points have stopped meaning anything?
Strong answers cover: Root cause first, usually point inflation under pressure or drifting reference stories, then a reset method: re-anchoring on reference stories, right-sizing work, or dropping points for throughput counting.
Role craft
7. When would you move a team from Scrum to Kanban?
Strong answers cover: Flow thinking rather than framework loyalty, with interrupt-heavy work like support or platform ops as the trigger, WIP limits and cycle time replacing sprint commitments, and a transition plan the team owns.
Situational
8. Your product owner keeps pulling work into the sprint mid-cycle and the team has stopped objecting. What do you do?
Strong answers cover: Going after why the product owner bypasses planning rather than policing the rule, making the cost of churn visible with data, and rebuilding the team's willingness to push back for themselves.
Situational
9. Two stories are blocked on another team with different priorities and your sprint ends Friday. Walk me through your next two days.
Strong answers cover: Working several angles at once: direct contact with the other team's lead before any escalation, resequencing so the team stays productive, and an honest mid-sprint replan with the product owner if the dependency will not clear.
Curveball
10. If your company banned Scrum tomorrow, what would you make sure your team kept?
Strong answers cover: Evidence they understand why the ceremonies exist: the team would keep short feedback loops, small batches, visible work, and a regular moment of reflection, whatever those practices end up being called.

Rehearse out loud with real stories from your record; the numbers you dug up for your resume bullets double as interview evidence.

Make it yours: Interview Questions Generator

This set covers the durable scrum master pattern space. The generator personalizes it to your level and focus areas in one run.

Open the free tool

Frequently asked questions

What is the most common mistake in Scrum Master interviews?

The classic one is answering every question with framework theory instead of a real team. Interviewers assume you know the material, and quoting it back signals you have nothing else to offer. Every answer should carry a real team, a real mess, and what you actually did, including the parts that did not work. An honest failure story with a clear lesson usually outscores a polished success.

How should I prepare for the scenario questions?

Inventory your five hardest real situations before the interview: the resistant team, the scope-injecting product owner, the cross-team blocker, the dead retrospective, the estimation drift. Almost every scenario question maps to one of those, so you retell instead of inventing under pressure. Drill the phrasing with the interview questions generator.