30+ interviewer questions across six sets, each with why it is worth asking and what a good answer sounds like, plus a 1-to-5 scorecard and a red-flag checklist. Built for small teams hiring without HR. Download as DOCX.
The first Scrum Master I ever interviewed answered every question correctly and was still the wrong hire. He could recite the framework, name every event, and quote the guide. What he could not do, and what I failed to ask about, was tell me a single story about a blocker he had personally removed for a team that could not remove it itself. That is the whole job, and I spent forty minutes not asking about it.
Interviewing for this role is unusually easy to get wrong, because the vocabulary is learnable in a weekend and the work is not. A candidate who sounds fluent can turn out to be a project manager with a new title, or a facilitator who runs pleasant meetings while the same problems repeat every sprint. The fix is to ask for specifics and to know in advance what a good answer sounds like.
At FirstHR we build for small businesses that hire without an HR department, where the founder usually runs the interview alone and often does not run Scrum well themselves. This page gives you six question sets, each question paired with why it is worth asking and what a strong answer contains, plus a 1-to-5 scorecard and a red-flag checklist you can use straight after the interview.
TL;DR
Interview a Scrum Master on five things: Scrum fundamentals and the role boundary, facilitation of the events, impediment removal and stakeholder courage, coaching and conflict, and delivery metrics. Ask the same questions of every candidate and score each area 1 to 5. Pay anchors near $102,320, the median for project management specialists.
What to Assess in a Scrum Master
Assess a Scrum Master on what changes because they are there, not on how well they describe Scrum. The role is accountable for the team's effectiveness, for the framework being understood and enacted, and for removing impediments, and none of those are demonstrated by reciting the accountabilities correctly.
That distinction matters most at the boundary with project management. A project manager owns scope, schedule, and assignment. A Scrum Master owns how the team works and has to get results through influence rather than authority. Both are legitimate jobs, but a team that expects a servant leader and gets a taskmaster will disengage inside a month.
The most reliable way to test any of this is a structured interview, where every candidate answers the same core questions and is scored on the same rubric. That is why this page is built around fixed question sets and a scorecard rather than a browsable list of prompts.
The Five Question Areas
The questions below are grouped into five areas plus a scorecard. Each area tests a different part of the role, and a strong candidate performs across all of them rather than only on the fundamentals questions they have rehearsed most.
Fundamentals and Role Boundary
Scrum Master or PM?
Whether the candidate understands the accountabilities or has been doing delivery management under a new title. The set that catches the most expensive mistake on this hire.
Facilitation and Events
Useful or endured?
How they run the Daily Scrum, Sprint Planning, the Review, and the Retrospective, including what they do when an event has gone stale or silent.
Impediments and Stakeholders
Do they actually unblock?
Named blockers removed, escalation with data, protecting the Sprint Goal from mid-sprint additions, and talking to leadership without lecturing.
Coaching and Conflict
Can they change behavior?
Facilitating a technical disagreement, coaching a first-time Product Owner, building safety, and giving hard feedback without formal authority.
Metrics and Improvement
Do they improve delivery?
Which metrics they use and why, the limits of velocity, diagnosing unfinished sprints, the definition of done, and what they learned from an experiment that failed.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric across all five areas plus an eight-item red-flag checklist, so the decision rests on written evidence rather than the interview that felt best.
Weight the Areas to the Problem You Are Hiring For
Write down the two or three delivery problems this hire exists to solve, then weight the questions accordingly. If your sprints keep ending with unfinished work, lean on the metrics and delivery set. If the founder interrupts the sprint three times a week, lean on impediments and stakeholders. If the team has gone quiet and the retrospective produces nothing, lean on facilitation and coaching. Ask at least two questions from every area regardless, and always run the fundamentals set first, because it is the one that catches a project manager in Scrum Master clothing.
30+ Questions and a Scorecard to Download
Download all six sets as a single Word document, or copy any set individually. Every set follows the same shape: when to use it, the questions with a note on why each one is worth asking and what a good answer sounds like, what to listen for, and space for notes. The sixth file is the scorecard and red-flag checklist.
Download All 6 Scrum Master Question Sets
Fundamentals, facilitation, impediments, coaching, metrics, and a 1-to-5 scorecard with red flags. All in one DOCX.
Set 1: Scrum Fundamentals and Role Boundary
The set that catches the most expensive mistake on this hire. Tests whether the candidate understands the accountabilities, knows what they are not responsible for, and can size the framework to a five person team. Start here with every candidate.
Scrum Fundamentals and Role Boundary Questions
SCRUM MASTER INTERVIEW: FUNDAMENTALS AND ROLE BOUNDARY
Candidate: __
Interviewer: __
Date: __
HOW TO USE THIS SET
Start here. This set tells you whether the candidate is a Scrum Master or a
project manager with a new title, which is the most common and most expensive
mistake on this hire. Each question lists why it is worth asking and what a good
answer sounds like, so you can judge the answers even if you do not run Scrum
yourself. Ask the same questions of every candidate and score them at the end.
QUESTIONS
1. What is a Scrum Master accountable for, and what are you not accountable for?
Why ask: The clearest single test of whether the candidate understands the
role or has been doing delivery management under a different label.
Good answer: Accountable for the team’s effectiveness, for Scrum being
understood and enacted, and for removing impediments. Not accountable for
assigning tasks, owning the backlog, or committing the team to dates on
someone else’s behalf. Says plainly that the team is self-managing.
2. Walk me through Scrum: the accountabilities, the events, and the artifacts.
Why ask: Basic fluency. Someone who cannot describe the framework cleanly
will not be able to teach it to your team.
Good answer: Three accountabilities (Scrum Master, Product Owner,
Developers), five events (the Sprint, Sprint Planning, Daily Scrum, Sprint
Review, Sprint Retrospective), three artifacts (Product Backlog, Sprint
Backlog, Increment). Explains each in their own words rather than reciting.
3. How is a Scrum Master different from a project manager?
Why ask: You need to know which one the candidate actually is, and which one
your team needs, before you write the offer.
Good answer: A project manager owns scope, schedule, and assignment. A Scrum
Master owns how the team works and influences without authority. A strong
candidate is visibly comfortable giving up command and control.
4. Where does your job end and the Product Owner’s begin?
Why ask: On a small team these two roles blur, and sometimes land on one
person. You need a candidate who knows the boundary and will hold it.
Good answer: The Product Owner owns the what: backlog, order, value. The
Scrum Master owns the how the team works. They overlap in refinement and
stakeholder communication. Flags the conflict of interest when one person
holds both.
5. When would you deviate from Scrum, and when would you refuse to?
Why ask: Dogmatists and pushovers both fail on a small team. This question
tests judgment, which is what you are actually buying.
Good answer: Names a real adaptation they made (a five minute Daily Scrum for
a three person team) and a line they held (keeping the Retrospective when
leadership wanted the time back). Gives the reasoning, not the rulebook.
6. We are a team of five shipping a web product. What would the first sprint
look like here?
Why ask: Tests whether they can size the framework to your reality instead of
importing a process built for a two hundred person engineering org.
Good answer: Asks questions before answering. Proposes something light: one
or two week sprints, a real Sprint Goal, a short Daily Scrum, a Review with
actual stakeholders, and a Retrospective that produces one change.
7. What does a self-managing team mean in practice, and how do you get there?
Why ask: The phrase is easy to say and hard to do. The answer tells you
whether this person coaches or controls.
Good answer: Describes moving decisions to the team over time, holding back
from assigning work, making impediments visible instead of solving everything
personally, and being honest that it takes months rather than a sprint.
WHAT TO LISTEN FOR
•Explains the framework in their own words, not as a memorized list
•Comfortable with influence instead of authority
•Adapts the process to team size and product, with stated reasons
•Knows the Product Owner boundary and states it without prompting
RED FLAGS
[ ] Describes the role as running standups and updating the board
[ ] Assigns work to developers
[ ] Treats every rule as untouchable, or treats none of them as real
[ ] Cannot name what they are not accountable for
NOTES
__
__
Set 2: Facilitation and Scrum Events
The visible half of the job, and the half your team will judge within two weeks. Covers the Daily Scrum, long Sprint Planning, a Review that has become a demo, a silent Retrospective, and remote facilitation.
Facilitation and Scrum Events Questions
SCRUM MASTER INTERVIEW: FACILITATION AND SCRUM EVENTS
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
Facilitation is the visible half of the job, and the half your team will judge
within two weeks. Use this set to find out whether the candidate runs events
people find useful or events people endure. Every question below includes why it
is worth asking and what a strong answer contains.
QUESTIONS
1. How do you run a Daily Scrum that the team actually finds useful?
Why ask: The Daily Scrum degenerates into a status meeting faster than any
other event, so this is where a weak Scrum Master shows up first.
Good answer: The developers run it, not the Scrum Master. It exists for the
team to inspect progress toward the Sprint Goal and re-plan the day, in about
fifteen minutes. Detailed problems move to a follow-up conversation. Says
outright that it is not a report to management.
2. Sprint Planning routinely runs three hours and ends without a clear goal.
What do you change?
Why ask: Tests diagnosis rather than vocabulary. Long planning is almost
always a symptom of something upstream.
Good answer: Traces it back to refinement and an unready Product Backlog,
works with the Product Owner on ready items, and insists on a single Sprint
Goal before the team pulls work. Proposes one change, then checks whether it
helped rather than changing five things at once.
3. What does a good Sprint Review look like, and who is in the room?
Why ask: Many teams turn the Review into a demo for one manager instead of a
working session with the people who care about the product.
Good answer: Real stakeholders, working software, an honest conversation
about what to do next, and backlog changes coming out of it. Not a slide
deck and not a sign-off ceremony.
4. Retrospectives have gone quiet and nothing changes. How do you fix it?
Why ask: A dead retrospective is the most common symptom of a team that has
stopped improving, and reviving it is core Scrum Master work.
Good answer: Names concrete moves: change the format, gather data before
opinions, make it safe, and above all pick one improvement, put it into the
next Sprint Backlog, and close the loop publicly. Treats silence as a safety
problem rather than a personality problem.
5. Give me three retrospective formats you have used and when each one fits.
Why ask: Range. A candidate with a single format will run the same meeting
for two years and the team will tune out.
Good answer: Names real formats and matches them to situations: a simple
start, stop, continue for a routine sprint; a timeline retrospective after a
long or painful release; a focused, blameless review after an incident.
6. How do you handle a stakeholder who dominates the Sprint Review?
Why ask: Facilitation under social pressure is the hard part of the job, and
at a small company that stakeholder is often the founder.
Good answer: Sets expectations before the meeting, redirects in the room
without embarrassing anyone, and follows up privately afterward. Protects the
team’s airtime without turning it into a confrontation.
7. How does your facilitation change when the team is fully remote?
Why ask: Most small teams are at least partly remote, and remote facilitation
is a separate skill from in-room facilitation.
Good answer: Names specifics: shorter events, one shared board everyone can
edit, written input collected before discussion so quieter people contribute,
camera norms the team agreed to rather than a mandate, and fair scheduling
across time zones.
WHAT TO LISTEN FOR
•Events described as serving the team, not informing management
•Diagnosis before prescription when an event is broken
•More than one facilitation technique, chosen for a reason
•Comfort managing a dominant voice in the room
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
The part of the role with the clearest business return and the least visible evidence on a resume. Push for the actual blocker, the actual action, and the actual outcome. Vague answers here matter more than anywhere else.
Impediments and Stakeholder Questions
SCRUM MASTER INTERVIEW: IMPEDIMENTS AND STAKEHOLDERS
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
Removing impediments is the part of the role with the clearest business return
and the least visible evidence in a resume. This set is built to get specifics.
Push for the actual blocker, the actual action, and the actual outcome. Vague
answers here are the strongest negative signal in the whole interview.
QUESTIONS
1. Give me an example of an impediment you removed that the team could not have
removed on its own.
Why ask: This is the most concrete measure of whether the candidate did the
job or simply attended the meetings.
Good answer: A specific blocker, a specific action, and a specific result: a
license or access delay chased down, a cross-team dependency renegotiated, a
decision escalated and closed. Weak answers describe removing blockers as a
general activity with no example attached.
2. How do you track impediments, and what do you do when one sits above your
level of influence?
Why ask: Escalation is where a Scrum Master either has courage or does not.
Good answer: Keeps a visible impediment list with owners and ages, escalates
with data and one specific ask, and follows up on a schedule. Does not let a
blocker sit for two sprints out of politeness.
3. The Product Owner keeps adding work mid-sprint. How do you handle it?
Why ask: The single most common failure mode at a small company, where the
Product Owner is often the founder and the interruptions come daily.
Good answer: Protects the Sprint Goal, makes the trade-off explicit (what
comes out if this goes in), and coaches the Product Owner toward the next
sprint. Firm without being obstructive, and clear that a genuinely urgent
item is a legitimate reason to change a sprint, as a decision rather than
a habit.
4. Leadership wants fixed scope on a fixed date for the quarter. What do you
say to them?
Why ask: Small companies ask this constantly, and the answer shows whether
the candidate can talk to executives without lecturing them.
Good answer: Forecasts from real data such as historical throughput ranges,
presents the trade-off honestly, and keeps the conversation about risk and
options. Does not deliver a speech about agile principles.
5. Tell me about a time you had to say no to someone more senior than you.
Why ask: The role requires influence without authority, so courage is not
optional. This question surfaces it directly.
Good answer: A real example, a respectful framing, and a stated outcome. Even
when they were overruled, listen for whether they made the cost visible and
wrote it down.
6. How do you keep stakeholders informed without turning the team into a
reporting machine?
Why ask: Reporting overhead is a hidden tax that a good Scrum Master keeps
low, and a weak one quietly doubles.
Good answer: Uses the Sprint Review and a visible board as the primary
channels, gives stakeholders self-serve visibility, and redirects ad hoc
status requests to what already exists instead of building a new report.
7. What would you do in your first thirty days here?
Why ask: Tests whether they observe before they reorganize, which is the
difference between a helpful hire and a disruptive one.
Good answer: Listens first: attends the events, talks to every team member
and the Product Owner, maps the current process and where it hurts, then
proposes one or two changes. A full transformation plan on day one, written
before they have met the team, is a risk rather than a strength.
WHAT TO LISTEN FOR
•Named blockers with named outcomes, not general statements
•Willingness to escalate with data and a specific ask
•Protects the Sprint Goal without becoming a gatekeeper
•Observes before changing things
NOTES
__
Set 4: Coaching, Conflict, and Team Dynamics
Facilitating a stalled technical disagreement, coaching a first-time Product Owner, spotting quiet disengagement, building safety, and giving hard feedback to peers you have no authority over.
Coaching, Conflict, and Team Dynamics Questions
SCRUM MASTER INTERVIEW: COACHING, CONFLICT, AND TEAM DYNAMICS
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
A Scrum Master changes how a team behaves, which means coaching and conflict are
daily work rather than occasional events. This set gets past the vocabulary of
coaching and into what the candidate actually did. Ask for the situation, the
action, and the result on every answer.
QUESTIONS
1. Two developers disagree on the technical approach and the sprint is stalling.
What do you do?
Why ask: Reveals in one answer whether the candidate facilitates a decision
or avoids the conflict until someone else settles it.
Good answer: Gets the disagreement into the open, focuses it on the Sprint
Goal and on the criteria for deciding, sets a timebox, and lets the
developers own the call. Brings in a technical lead only if the team asks.
2. Someone on the team has quietly disengaged. How do you find out why, and
what do you do about it?
Why ask: Disengagement surfaces late and costs a small team disproportionately,
and the Scrum Master usually sees it first.
Good answer: A private, curious conversation before anything public.
Separates a process problem they can fix from a personal or management
problem that belongs with the person’s manager. Knows that line, because a
Scrum Master is not the team’s boss.
3. How do you coach a Product Owner who is new to the role?
Why ask: On a small team the Product Owner is often a founder doing the job
part time, so coaching them is half the value of this hire.
Good answer: Practical and incremental: help write outcomes instead of task
lists, run refinement together, protect their time for stakeholder work, and
build a backlog that is genuinely ordered. Patient rather than doctrinaire.
4. Describe a time you changed a team’s behavior. What did you actually do?
Why ask: Behavior change is the whole role, and it is easy to claim and hard
to evidence, so the specifics matter more than the story.
Good answer: A named starting behavior, a specific intervention, and an
observable change over weeks. Watch for candidates who describe what they
told people rather than what changed afterward.
5. How do you build psychological safety on a team that does not have it?
Why ask: Without safety the Retrospective is theater, problems stay hidden,
and you find out about them at the worst possible moment.
Good answer: Concrete moves: model admitting mistakes, respond well the first
time someone raises bad news, run blameless reviews after incidents, and keep
the retrospective separate from performance conversations. Names time as a
factor rather than promising a quick fix.
6. What is the hardest feedback you have given, and how did you give it?
Why ask: Shows whether the candidate can be direct with peers over whom they
have no formal authority, which is most of the job.
Good answer: Specific, private, focused on behavior, and delivered soon after
the event rather than saved up. Listen for what happened next, including
whether the working relationship survived it.
7. A manager asks you for individual productivity metrics on each developer.
How do you respond?
Why ask: This request lands on small teams regularly, and the answer shows
both spine and diplomacy at the same time.
Good answer: Explains what individual metrics do to collaboration, offers
team level alternatives that answer the manager’s real question, and does not
simply refuse. Understands that the manager usually wants predictability
rather than surveillance.
WHAT TO LISTEN FOR
•Facilitates decisions instead of making them for the team
•Knows where coaching ends and management begins
•Concrete behavior change with an observable result
•Direct with peers and seniors, without being combative
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Separates a Scrum Master who improves delivery from one who runs meetings on time. Covers which metrics they use, the limits of velocity, diagnosing unfinished sprints, the definition of done, and an experiment that failed.
Metrics, Delivery, and Improvement Questions
SCRUM MASTER INTERVIEW: METRICS, DELIVERY, AND IMPROVEMENT
Candidate: __
Interviewer: __
Date: __
WHEN TO USE THIS SET
This set separates a Scrum Master who improves delivery from one who runs
meetings on schedule. It is also where misuse of metrics shows up, which matters
because the wrong number, used the wrong way, will damage a small team faster
than no number at all.
QUESTIONS
1. Which metrics do you actually use, and what do you do with them?
Why ask: The choice of metrics, and what they are used for, tells you how
this person thinks about improvement.
Good answer: A small set used for the team’s own inspection: throughput,
cycle time, work in progress, Sprint Goal success rate, escaped defects. Uses
them to start conversations in the Retrospective, never to grade individuals.
2. What is velocity good for, and what is it bad for?
Why ask: Velocity is the most misused number in agile delivery, and misusing
it is one of the fastest ways to break a team.
Good answer: Useful as a rough forecasting input for one team over time.
Useless for comparing teams, and actively harmful as a target, because points
inflate the moment they become a goal.
3. Our sprints keep ending with unfinished work. How would you diagnose that?
Why ask: Diagnosis is the skill. The causes are many and the right fix
depends entirely on which one is actually present.
Good answer: Investigates before prescribing. Checks whether the backlog is
ready, whether there is a real Sprint Goal, whether too much is started and
not finished, whether unplanned interruptions are constant, and whether the
definition of done is clear. Then tests one change at a time.
4. What is a definition of done, and how do you get a team to agree on one?
Why ask: A missing or weak definition of done sits behind most quality
problems on small teams, and fixing it is high leverage.
Good answer: A shared quality bar every increment must meet, written by the
team, covering testing, review, and release readiness. Describes drafting it
in a working session, keeping it visible, and tightening it deliberately.
5. How do you handle technical debt inside Scrum?
Why ask: On a small product, unmanaged debt is what eventually stops
delivery, and the Scrum Master influences whether it gets addressed at all.
Good answer: Makes the debt visible in the Product Backlog with its real
cost, helps the Product Owner weigh it against features, and uses the
definition of done to stop new debt appearing. Does not offer a fixed
percentage of every sprint as a slogan.
6. How do you know whether you are doing a good job as a Scrum Master?
Why ask: The self-assessment answer is one of the strongest signals in the
entire interview, because it reveals what the candidate optimizes for.
Good answer: Points at team outcomes rather than personal activity: the team
needs them less over time, impediments close faster, retrospective actions
actually ship, delivery becomes more predictable. A weak answer counts
meetings facilitated.
7. Tell me about an improvement you tried that failed. What did you learn?
Why ask: Continuous improvement means running experiments, and experiments
fail. A candidate who has never failed has never really experimented.
Good answer: A specific change, an honest account of why it did not work, and
what they did next. Openness here usually tracks with the humility the role
requires day to day.
WHAT TO LISTEN FOR
•A small, deliberate set of metrics with a stated purpose
•Understands the limits and the risks of velocity
•Diagnoses before prescribing, and changes one thing at a time
•Measures their own success by the team’s outcomes
NOTES
__
Set 6: Scorecard and Red-Flag Checklist
A 1-to-5 rubric across all five areas plus an eight-item red-flag checklist, so the decision rests on written evidence. This is the asset most question lists leave out, and it is the one that changes decisions.
Scrum Master Interview Scorecard and Red Flags
SCRUM MASTER INTERVIEW SCORECARD AND RED-FLAG CHECKLIST
Candidate: __
Interviewer: __
Date: __
HOW TO SCORE
Score each area from 1 to 5 immediately after the interview, while the answers
are fresh. Anchor every score to something the candidate actually said. If more
than one person interviews, each scores independently before the group discusses,
so a single strong impression does not anchor everyone else. Use the same rubric
for every candidate, because a consistent, evidence-based process is both fairer
and easier to defend later.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Scrum fundamentals and role boundary: knows the accountabilities, and knows what
the role is not
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Facilitation: events that serve the team, more than one technique, handles a
dominant voice
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Impediments and stakeholders: named blockers removed, escalates with data,
protects the Sprint Goal
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Coaching and conflict: facilitates decisions, builds safety, gives hard feedback
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Metrics and improvement: uses a small metric set well, diagnoses before
prescribing, learns from failure
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Fit for a small team: adapts the framework to your size instead of importing
heavy process
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
RED FLAGS (WEIGH CAREFULLY)
[ ] Describes the role as running standups and updating the board
[ ] Assigns work to developers or speaks about the team as direct reports
[ ] No specific impediment they personally removed
[ ] Recites the framework but cannot adapt it to a five person team
[ ] Blames past teams or past management for everything that went wrong
[ ] Treats velocity as a target or compares teams by it
[ ] Arrives with a full transformation plan before meeting anyone
The questions open the conversation; the follow-ups decide the hire. On this role the single most valuable follow-up is what did the team do differently afterward, because it converts a story about what the candidate said into evidence about what changed.
Signals of a real Scrum Master
Names what they are not accountable for
Gives a specific impediment with an outcome
Measures success by the team needing them less
Follow-ups that pay off
What did the team do differently afterward?
Who made that decision, you or the developers?
What happened when you escalated it?
Fit for a small team
Sizes the framework to five people, not fifty
Comfortable coaching a founder Product Owner
Wears more than one hat without resentment
Red flags
Standups and board updates as the whole job
No named blocker they personally removed
Velocity as a target or a cross-team comparison
Two red flags deserve extra weight at a small company. A candidate who arrives with a full transformation plan before meeting anyone will spend their first month reorganizing rather than observing. And a candidate who cannot name an improvement that failed has probably never run a real experiment, which is most of the job. For broader technique, the behavioral question set pairs well with these, and situational questions help when a candidate lacks direct experience with a scenario you care about.
Certifications, Experience, and What Actually Matters
Treat a certification as a signal, not a qualification. A Certified ScrumMaster or Professional Scrum Master credential shows the candidate has covered the framework formally, which genuinely helps when your team is new to Scrum and needs someone to teach it. It tells you very little about facilitation under pressure or the courage to escalate.
In practice, a certified candidate who cannot give a specific example of an impediment they removed is the weaker hire. List the credential as preferred rather than required in your Scrum Master job description, then weight the interview toward evidence. One useful question: what did you learn in the course that did not survive contact with a real team.
Signal
What it tells you
How much to weight it
CSM or PSM certification
Formal exposure to the framework; can teach it
Useful when your team is new to Scrum; never decisive
Years in the title
Time served, not necessarily impact
Low on its own; ask what changed in that time
A named impediment removed
They did the job, not just the meetings
High; the single best predictor in this interview
Coached a first-time Product Owner
Can do the half of the job small teams need most
High at a small company; often the real value
Experience only on large teams
May import heavy process for a team of five
Probe directly; ask them to size it down
An improvement that failed
Runs real experiments and learns from them
High; the absence of one is a red flag
Experience on very large teams is worth probing rather than assuming. Someone who has only run Scrum at scale may reach for the process weight that made sense there, which is exactly what a five person team cannot absorb. Ask them to describe the first sprint at your size and listen for whether they subtract.
How to Run the Interview
Running this interview well is mostly structure and consistency: prepare the questions, ask the same core set of everyone, score on the rubric, and decide from written evidence. The steps below work whether you are a single founder or a small panel with a developer in the room.
Step
What to do
1. Define the problem
Name the two or three delivery problems this hire must fix
2. Prepare
Pick questions across all five areas, weighted to those problems
3. Standardize
Ask the same core questions of every candidate, in the same order
4. Probe for evidence
For every claim, ask what the team did differently afterward
5. Include the team
Put a developer in one round with the same questions and scorecard
6. Score
Rate all five areas 1 to 5 with evidence, independently
7. Decide and offer
Compare written scores, then make the offer and onboard
Score immediately after each interview while the answers are still fresh. If more than one person interviews, each should score before the group talks, so the loudest impression does not anchor everyone else. That written record also feeds a clean interview feedback step and keeps the whole hiring process defensible if you are ever asked how the decision was made.
One practical note on logistics: most small teams track candidates in a spreadsheet and a shared inbox, which works until you have more than a handful of applicants and two people scheduling. Keep the interview records and scorecards somewhere they will not be lost, because the notes are what let you compare a candidate from week one against a candidate from week three. Applicant tracking is coming soon to FirstHR.
Fair, Legal, and Structured Interviewing
A good interview is fair, legal, and structured, and the three reinforce each other. Asking the same job-related questions of everyone keeps you compliant, reduces bias, and produces better hires at the same time. This is the part most question lists skip entirely.
Ask about the job, not the person
Federal anti-discrimination law prohibits basing hiring decisions on protected characteristics, and questions that probe them create risk even when they are asked as small talk. Avoid age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. Scrum Master interviews have a specific trap: the role is often described as a culture fit hire, and culture fit conversations drift toward personal life fast. Keep every question tied to facilitating a team, removing impediments, and improving delivery. This is general information, not legal advice.
Ask every candidate the same core questions
Consistency is what makes the comparison meaningful. When each candidate answers the same questions and is scored against the same rubric, you are comparing evidence rather than rapport, and you have a defensible record of how the decision was made. This matters more on a Scrum Master hire than most, because the role is relational and the interview is unusually easy to run as a pleasant conversation that tells you nothing. Write the questions in advance, ask them in the same order, and score them.
Score independently, then discuss
If a developer or your Product Owner joins the interview, have each person fill in the scorecard alone before anyone talks. Otherwise the most senior or most confident voice sets the tone and everyone quietly aligns to it. Compare the written evidence first, discuss the gaps second. For a founder who is also the hiring manager, the discipline is the same: write your scores down before you start building a story about the candidate you liked.
Let the team meet the candidate
A Scrum Master works through the team, so the team has information you do not. Include at least one developer in a round, give them two or three of the same questions to ask everyone, and give them the same scorecard. Be clear that this is input to your decision rather than a veto, and that the questions stay job-related for them too. A candidate the developers will not open up to cannot do this job, no matter how well the founder interview went.
Structure Beats a Good Conversation
A structured interview, where every candidate answers the same questions and is rated against defined criteria, is the approach professional HR guidance consistently recommends over a free-flowing conversation, precisely because standardized rating criteria let interviewers judge the quality of an answer rather than the comfort of the exchange (SHRM). The same discipline is what makes the comparison between an unstructured conversation and a scored one worth having at all.
Keep every question tied to the job and avoid the small-talk traps around age, family, origin, and religion; the federal rules on this are summarized by the EEOC, and a fuller list sits in our guide to illegal interview questions. This is general information, not legal advice.
Interviewing a Scrum Master Without HR
At a large company this candidate runs through coordinated panels with a recruiter managing the scorecards and an agile practice lead grading the craft. At a small business the founder usually runs the interview alone, between everything else, and often without deep Scrum experience of their own. Here is how to make that single interview rigorous anyway.
You are hiring a Scrum Master without running Scrum well yourself
Most owners making this hire know the vocabulary and not much more, which makes it hard to tell a fluent candidate from a competent one. That is exactly why every question in these sets carries a note on what a good answer sounds like. You are not grading their Scrum knowledge against a certification syllabus. You are checking for three things any non-expert can hear: a specific example instead of a general claim, a named outcome instead of an activity, and a candidate who asks about your team before prescribing anything for it. If you want a second opinion, put a developer in the room with the same questions and the same scorecard.
At your size, the job is not a full-time facilitation role
One team of five does not generate forty hours of facilitation a week, so the honest question is what else this person does. Common answers are a hybrid Scrum Master and Product Owner (it can work, but the conflict of interest is real and should be named), a Scrum Master who also does delivery coordination across a couple of teams, or a part-time engagement. Ask candidates directly how they would spend the other half of the week here, and listen for whether they invent process to fill the time. A candidate who says they would also coach the Product Owner, clean up the backlog, and work on the definition of done is describing real work. A candidate who proposes three new ceremonies is describing overhead.
The interview is the easy part; the offer and the first month are where it lands
Once you pick someone, the work shifts from evaluating to hiring well: a clear offer with the salary and classification in writing, the new hire paperwork, tool access, and an introduction to the team and the Product Owner before day one. A Scrum Master succeeds through relationships, so a slow, disorganized first week costs more here than in most roles. FirstHR covers this side for a small business: e-signature for the offer, an onboarding workflow that runs the same setup for every hire, document management for the signed paperwork and any certifications, and training modules for orientation. FirstHR is an onboarding and HR platform, not a payroll provider and not a work-tracking tool, so connect those separately. Applicant tracking is coming soon to FirstHR.
Responsibility
Scrum Master
Project Manager
Facilitates the Scrum events
Assigns tasks to individuals
Owns scope and schedule commitments
Removes impediments for the team
Coaches the team toward self-management
Leads through influence rather than authority
If your team needs someone to own scope and dates, hire for that and call it what it is; a project manager role is not a lesser hire. If your team needs someone to improve how it works and coach a first-time Product Owner, interview with these sets and hold the boundary in the offer.
Scrum Master Pay and the Offer
Scrum Master has no standalone federal occupation code, so the closest anchor is project management specialists (SOC 13-1082). Use it as a reference band rather than a target, since the classification blends many project roles and dedicated Scrum Master pay tends to run somewhat higher.
Median $102,320 a Year (BLS OEWS, May 2025)
Project management specialists had a median annual wage of $102,320 (about $49.19 an hour), with the lowest 10 percent under $61,580, the 25th percentile at $78,440, the 75th at $133,100, and the highest 10 percent above $167,970, according to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025) (U.S. Bureau of Labor Statistics).
Adjust for your region, industry, seniority, and whether the role is remote, and price the actual scope if the position is part time or hybrid with Product Owner work. The role is typically salaried and exempt under the administrative exemption rather than the computer-employee exemption, since facilitation is not systems analysis or programming; confirm it against the duties using the Department of Labor fact sheet and any stricter state rule before you write the offer. This is general information, not legal advice.
From Interview to Hire
The interview is step one. Once you choose someone, the process shifts to hiring well: a clear offer letter with salary and classification in writing, the new hire paperwork, tool access, and introductions to the team and the Product Owner before day one. A Scrum Master works through relationships, so a slow first week costs more here than in most roles.
Prepare the question set
Pick questions across all five areas, weighted toward what your team needs most, and ask the same core set of every candidate.
Score on the rubric
Have each interviewer score 1 to 5 with evidence independently, then compare the written notes before anyone discusses.
Send the offer
Confirm the salary, the classification, and the start date in writing, with e-signature so the record is clean from day one.
Onboard for the first month
Introduce the team and the Product Owner early, grant tool access before day one, and agree what to observe before changing anything.
Give the new hire an explicit brief for the first month: observe the events, meet everyone, map the current process and where it hurts, and propose one or two changes rather than a program. A 30-60-90 day plan makes that expectation concrete, and an onboarding template keeps the administrative side from eating the first week.
More question kits for adjacent roles sit in the hiring templates library. FirstHR connects the offer, the paperwork, e-signatures, and the onboarding workflow in one place, and stores the signed documents and any certifications on the employee profile, so a small business can run hiring through to onboarding from a single system. FirstHR is an onboarding and HR platform, not a payroll provider and not a work-tracking tool, so pair it with those. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Assess a Scrum Master on five areas: fundamentals and role boundary, facilitation, impediments and stakeholders, coaching and conflict, and delivery metrics.
Ask what the candidate is not accountable for; it is the fastest way to spot a project manager with a new title.
Demand a named impediment they personally removed, with the action and the outcome; it is the best single predictor in this interview.
Treat CSM or PSM as a preferred signal, never a substitute for evidence that they changed how a team worked.
Ask what the first sprint would look like on a team of your size, and listen for whether the candidate subtracts process.
Score all five areas 1 to 5 with written evidence, independently, before anyone discusses the candidate.
Pay anchor: a $102,320 median for project management specialists (BLS OEWS, May 2025), with Scrum Master roles often above it.
Frequently Asked Questions
What questions should I ask a Scrum Master candidate?
Ask across five areas: Scrum fundamentals and the role boundary, facilitation of the events, impediment removal and stakeholder handling, coaching and conflict, and delivery metrics. The highest-yield questions are what are you not accountable for, give me an example of an impediment you removed that the team could not remove itself, retrospectives have gone quiet and nothing changes so how do you fix that, the Product Owner keeps adding work mid-sprint so how do you handle it, and how do you know whether you are doing a good job. Each one forces a specific answer rather than a definition. Add one question sized to your reality, such as what the first sprint would look like on a team of five, because a candidate who cannot scale the framework down will import process you do not need. This page provides six downloadable question sets, each question paired with why it is worth asking and what a good answer contains.
How do I tell a real Scrum Master from a project manager with a new title?
Ask what they are not accountable for, then listen for whether they mention assigning work, owning the backlog, or committing the team to dates. A Scrum Master owns how the team works and influences without authority; a project manager owns scope, schedule, and assignment. The tell is usually in the verbs: a candidate who says they assigned tasks, drove the team, or held people to their commitments is describing project management. A candidate who says they made impediments visible, coached the Product Owner, and let the developers decide is describing the actual role. Follow up by asking who made a specific decision in their example, them or the developers. Neither background is disqualifying, but you should know which one you are buying, because a team that expects a servant leader and gets a taskmaster will disengage within a month.
Does a Scrum Master need a CSM or PSM certification?
Treat certification as a signal, not a qualification. A Certified ScrumMaster or Professional Scrum Master credential shows the candidate has covered the framework formally, which is genuinely useful when your team is new to Scrum and needs someone to teach it. It says almost nothing about facilitation skill, courage with stakeholders, or the ability to change how a team behaves, and those are what you are hiring for. In an interview, a certified candidate who cannot give a specific example of an impediment they removed is a weaker hire than an uncertified one who can. The practical approach for a small business is to list certification as preferred rather than required, then weight the interview toward real examples. Ask candidates what they learned from the course that they later found did not survive contact with a real team; the honest answers are informative.
What is the difference between a Scrum Master and a Product Owner?
The Product Owner owns what gets built: the Product Backlog, its order, and the value the product delivers. The Scrum Master owns how the team works: facilitating the events, removing impediments, coaching the team and the Product Owner, and improving the way the group operates. They overlap in backlog refinement and in stakeholder communication, which is where friction usually appears. On a small team the two roles sometimes land on one person, and that can function but is not ideal, because the same person then both sets the priorities and protects the team from priority changes. If you are considering the hybrid, name the conflict of interest openly in the interview and ask the candidate how they would handle it. A good candidate will describe the boundary clearly and tell you where they would need someone else to hold them accountable.
How do I interview a Scrum Master if I do not run Scrum well myself?
You do not need to grade Scrum knowledge against a syllabus. You need to hear three things any non-expert can recognize. First, a specific example rather than a general claim: a named blocker, a named action, a named outcome. Second, a result rather than an activity, so follow up with what did the team do differently afterward. Third, curiosity about your situation before any prescription, because a candidate who proposes a process before asking how your team works will do the same thing on the job. Each question in the downloadable sets on this page includes a note on what a good answer sounds like, so you can score against that rather than against your own Scrum knowledge. Put a developer in one round with the same questions and the same scorecard if you want a technical second opinion.
What are the red flags in a Scrum Master interview?
The most common red flag is describing the job as running standups and keeping the board updated, which reduces a coaching role to administration. Watch for a candidate who assigns work to developers or refers to the team as direct reports, since neither matches the accountability. Others worth weighing: no specific impediment they personally removed, an inability to adapt the framework to a five person team, treating velocity as a target or comparing teams by it, blaming past teams and past management for everything that went wrong, and arriving with a full transformation plan before having met anyone. Finally, a candidate who cannot name an improvement that failed has probably not run many experiments, and continuous improvement is most of this job. The downloadable scorecard on this page includes an eight-item red-flag checklist you can work through right after the interview.
How much does it cost to hire a Scrum Master?
Scrum Master is not a standalone federal occupation, so the closest anchor is project management specialists. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), that occupation had a median annual wage of $102,320, with the lowest 10 percent under $61,580 and the highest 10 percent above $167,970. Treat the median as a broad reference rather than a target, because the classification blends many project roles and dedicated Scrum Master pay tends to run somewhat higher, especially in expensive tech markets and at senior levels. Adjust for your region, your industry, the seniority you need, and whether the role is remote. If the position is part time or hybrid with Product Owner work, price the actual scope rather than the title. The role is typically salaried and exempt, so confirm classification against the duties before you write the offer.
What questions are illegal to ask in a Scrum Master interview?
Avoid anything that probes a characteristic protected under federal law: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. In practice that means not asking how old someone is, whether they have or plan to have children, where they are originally from, what they observe religiously, or about health conditions, even as friendly small talk. You may ask whether a candidate can perform the essential functions of the job and whether they are legally authorized to work. This role carries a specific trap, because it is often framed as a culture fit hire and culture fit conversations drift toward personal life quickly. Keep every question tied to facilitating a team, removing impediments, and improving delivery, and ask the same job-related questions of every candidate. This is general information, not legal advice.
