Scrum Master interview questions for recruiters

Technical screening questions

Ask for one example per question and listen for specifics.

• How do you handle a team that misses sprint goals repeatedly? A good answer: Looks for root causes in estimation, scope or blockers.
• What do you do in a retrospective that goes quiet? A good answer: Changes format and builds safety.
• How do you work with a product owner who changes priorities mid-sprint? A good answer: Protects the sprint and agrees a change process.
• Which metrics do you use? A good answer: Velocity trends, cycle time and predictability, used with care.
• Which certifications do you hold? A good answer: CSM or PSM with dates.

Quick screening questions

Use these when you have only a few minutes.

• How many teams did you serve at once?
• Describe an impediment you removed.
• How do you handle a team that keeps missing sprint goals?

What separates the levels

Match the level to the requirement before you submit.

• Junior: facilitates ceremonies.
• Mid: coaches a team.
• Senior: coaches several teams and the organization.

Red flags

Any of these is a reason to probe further.

• Acts as a project manager only.
• Cannot describe an impediment removed.
• Certification only.

Tools you should hear mentioned

A Scrum master with real experience usually names several of these without prompting.

• JIRA
• Confluence
• Scrum framework
• Kanban boards
• Velocity and cycle time metrics
• Retrospective tools

Run the call well

Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.

Frequently asked questions