Hiring a scrum master means testing facilitation, not counting certificates. Watch a candidate run a mock retrospective with real tension in the room, hear how they removed a specific impediment and measured the result, and check whether they coach behavior upward instead of policing tickets and reporting status.
The reliable seam is people who did the work before facilitating it. Engineers, testers and technical leads who moved into coaching bring credibility that pure process backgrounds rarely match, because they can call out an unrealistic estimate or a hidden dependency. Agile meetups, community-run conferences and open-space events attract practitioners who argue about flow, not templates. Consultancy alumni have seen many teams and often carry the widest pattern library, though some default to imposing a framework rather than reading the room. Internal promotion works well when a respected team member already facilitates naturally. Given how widely the title is applied, weigh what someone actually changed over their title history, and set out expectations clearly in the [scrum master job description](/job-descriptions/scrum-master).
Say which job this really is. Many advertisements labelled scrum master describe delivery management: chasing dates, reporting status upward and coordinating releases. That work is legitimate, but attracting coaches to a tracking role produces fast turnover and mutual resentment. State how many teams the person serves, who they report to, and whether leadership has committed to changing its own behavior or expects the teams to absorb every constraint. Describe the current maturity honestly, including which ceremonies exist in name only and which teams resist them. Name the mandate: are they there to run events, or to fix a delivery problem the organization already recognizes? Ambiguity attracts certificate collectors instead of practitioners.
Ask for one specific change, start to finish. A useful prompt is: describe a dysfunction on a team you served, what you tried first, what failed, what eventually worked, and how you knew it worked. Weak candidates answer with framework definitions; strong ones tell a story with awkward detail and a measurement. Probe which numbers they actually watch, and listen for flow measures such as cycle time, work in progress and throughput rather than velocity treated as a productivity score. Ask what they changed about a manager's behavior, since much of the real job is upward. Certificates confirm attendance at a course, nothing more, so treat them as background and put the evidence weight on demonstrated change. Structured comparison in your [hiring platform](/hiring-software) keeps that assessment consistent.
Have them facilitate. A mock retrospective with three or four of your people, briefed to bring a genuine tension, tells you more in twenty-five minutes than an hour of questions. Watch whether quiet participants get drawn in, whether the dominant voice gets managed without humiliation, and whether the session ends with actions and owners rather than a shared list of complaints. Then role-play a stakeholder pushing new scope mid-sprint and see whether they protect the team without becoming obstructive. Add a conflict scenario between two engineers who disagree publicly. Finally, let the team they would serve meet them and weigh that opinion heavily. Draw prompts from the [scrum master interview questions](/interview-questions/scrum-master) to keep panels aligned.
The market is lopsided. Certified entry-level candidates are plentiful, while experienced practitioners who have genuinely improved delivery across several teams are much harder to find, so expect a longer search at the senior end. Those people evaluate you as carefully as you evaluate them, and the question they care about is mandate: will leadership actually change anything, or is the role decoration around existing habits? Show them a constraint the organization already fixed. Introduce them to an engineering manager who supports the work. Be candid about the dysfunction they would inherit, because discovering it later is the fastest route to a short tenure. Common questions on agile roles are collected in the [answers library](/answers).
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
