Scrum Master Interview: How to Prepare (2026)

Cohesyve · Practice for candidates

Preparing for a Scrum Master role? Start by finding out where you stand.

Import the actual job you're going for, run a simulation built from it, and get a scored report showing which of these areas you're weakest in — before you spend weeks studying the wrong thing.

free assessments

no card required

Full

scored report every run

Every

question type included

3 free assessments · No card required · Pro from $16/mo

Overview

Scrum master interviews split sharply between organisations that want a facilitator and organisations that want a delivery manager with a different title. The first will probe your coaching instinct and how you handle dysfunction you cannot fix by decree; the second will ask about dependencies, forecasting and reporting. Most panels will also test whether you understand the framework beyond its ceremonies, because certificate-holders who cannot explain why a practice exists are common. This page covers the stages, the topics that separate candidates, and how to prepare.

The hiring process, stage by stage

Recruiter screen

Covers how many teams you have supported, in what domain, whether the environment was scrum, kanban or something hybrid, and your certifications. Also checks how you describe your role — teams or projects.

How to prepare: Have a clear description of your last team: its size, what it built, how long you were with it, and one specific improvement in how it worked while you were there. Be honest about hybrid environments rather than dressing them up as textbook scrum.

Hiring manager interview

Situational and behavioural. Expect scenarios about a team that is missing sprint goals, a product owner who is absent, an engineer who dominates, and a stakeholder who bypasses the process.

How to prepare: Prepare an example for each of those four situations with a specific intervention and its result. Avoid answers that end in escalation; interviewers want to see what you tried first.

Framework and practice discussion

Direct questions about the purpose of each event and artefact, the difference between the scrum master and a project manager, and how you would handle a team that wants to drop a ceremony.

How to prepare: Be able to state the purpose of every scrum event in one sentence each, and to explain the intent behind it. Prepare a considered view on when abandoning a practice is right, because rigid answers score poorly.

Team or panel session

Often a session with engineers and a product owner, sometimes observing you facilitate a short exercise such as a retrospective on a supplied scenario. They are assessing presence, listening, and whether you talk more than everyone else.

How to prepare: Practise facilitating with strangers: setting a frame, drawing out quieter participants, timeboxing without being abrupt, and closing with an owned action. Rehearse handling one participant who resists the exercise.

Leadership or delivery conversation

With an engineering or delivery lead. Focused on metrics, forecasting, cross-team dependencies, and how you report progress upwards without turning velocity into a target.

How to prepare: Be able to explain what flow metrics tell you and what they cannot, and how you would answer a director asking when something will be done. Prepare one example of surfacing a dependency early enough for it to matter.

What to study

Facilitation

It is the observable part of the job. A panel can usually tell within ten minutes whether you have run real sessions or only attended them.

Retrospective formats beyond the default, and when each is appropriateHandling a dominant voice and a silent participant in the same sessionTimeboxing that keeps the discussion alive rather than cutting it deadClosing every session with a named owner and a next step

Coaching and influence without authority

The role has no line management. Employers want evidence you have changed team behaviour through influence rather than by imposing process.

Asking questions that let a team reach a conclusion instead of announcing itWorking with a product owner who is unavailable or writing poor backlog itemsHandling an engineer who has decided the process is a waste of timeKnowing when coaching has failed and a direct conversation is required

Flow, forecasting and metrics

Delivery leads will test whether you can give a defensible forecast without turning velocity into a performance target.

Cycle time, throughput and work in progress, and what each revealsWhy velocity should not be compared across teams or used as a targetForecasting with ranges and confidence rather than a single dateSpotting the difference between a capacity problem and a dependency problem

Impediments and dependencies

In larger organisations most delay comes from outside the team. Panels want to know whether you chase these actively or log them and wait.

Making dependencies visible early and negotiating sequencing with another teamEscalating with evidence and a proposed resolution rather than a complaintDistinguishing an impediment from work the team should simply doTracking recurring impediments so the underlying cause gets addressed

Adapting the framework to the organisation

Almost no team runs textbook scrum. Interviewers are wary of candidates who treat the guide as scripture and equally wary of those who have abandoned it entirely.

Which practices carry most of the value and which are safe to adjustWorking within governance, audit or regulatory reporting requirementsSupporting several teams at once without becoming a meeting schedulerHow scrum interacts with kanban, and when a team should shift

Cohesyve for candidates

Practise a Scrum Master assessment before the real one

Run the same AI job simulations companies use to evaluate applicants. You get a scored report showing where you're strong and where you're not, plus what to work on.

Your preparation plan

Four weeks out

Rebuild the evidence that you changed how a team worked, not just that you ran its meetings.

•Write down three specific improvements you drove, with the before and after state
•Recall the metrics you had access to and what they showed over your tenure
•Reread the scrum guide properly and note anywhere your practice diverged and why
•Research how the employer organises delivery — scaled framework, single teams, or something bespoke

Two weeks out

Practise facilitation aloud, because describing it is not the same as doing it.

•Run a real retrospective for a team or a friend and ask for feedback on your facilitation
•Rehearse the four standard scenarios: missed sprint goals, absent product owner, dominant engineer, process bypass
•Prepare a clear, non-defensive answer on the difference between this role and a project manager
•Practise giving a forecast with a range to someone who wants a single date

The final week

Tighten your examples and prepare for the practical session.

•Cut each scenario answer to under two minutes ending in an outcome
•Do a mock facilitation with a participant instructed to be difficult
•Prepare your view on which practices you would keep, adjust or drop, with reasons
•Ask the recruiter whether any stage involves live facilitation so it does not surprise you

The day before and the day of

Arrive calm and ready to listen more than you speak.

•Reread your three improvement stories once and then set them aside
•Check your video setup, since facilitation over video is judged partly on presence
•Have a single page of prompts for a facilitation exercise, not a script
•Plan to pause before answering scenario questions rather than filling silence

Questions to expect

“The team has missed its sprint goal three sprints running. What do you do?”

What they're really asking: Do you diagnose, or do you apply pressure and more process?

How to answer: Start with observation rather than intervention: is it planning, interruption, dependencies, unclear goals, or estimation. Describe using the retrospective to surface it and the data to test it, then one change tried at a time. Give a real example including what the cause turned out to be.

“What is the difference between a scrum master and a project manager?”

What they're really asking: Do you understand the role you are applying for, and can you say so without sounding dogmatic?

How to answer: Frame it around accountability: one is accountable for the team's effectiveness and the flow of work, the other for scope, budget and plan against a defined outcome. Acknowledge that many organisations blend them and say which parts of the blend you are comfortable with.

“Your product owner is never available and the backlog is thin. How do you handle it?”

What they're really asking: Will you compensate quietly, escalate immediately, or address the cause?

How to answer: Describe finding out why first — competing demands, unclear expectations, or too many teams. Then the interventions: shorter focused sessions, preparing material to make their time cheap, and making the delivery impact visible to their manager if it does not improve. Avoid answers where you write the backlog yourself indefinitely.

“A director asks you when a piece of work will be finished. What do you tell them?”

What they're really asking: Can you forecast honestly under pressure without either refusing to answer or inventing certainty?

How to answer: Give a range with the reasoning: current throughput, remaining scope, known dependencies, and what would narrow the range. Say what you would commit to and what you would not, and offer to update at a specific point. Never give a date you know is unsupported.

“An experienced engineer says the ceremonies are a waste of their time.”

What they're really asking: Do you defend the process, or do you take the objection seriously?

How to answer: Treat it as data. Find out which sessions and why, since the complaint is often accurate about a badly run event. Describe changing the format or attendance to fix the real problem, and be willing to say which ceremony you dropped or shortened as a result.

“How do you measure whether a team is improving?”

What they're really asking: Do you have any measure at all, and do you understand the harm of the wrong one?

How to answer: Combine flow measures such as cycle time and work in progress with qualitative signals: predictability, how quickly problems surface, whether people raise issues in retrospectives. Say explicitly why velocity is not a target and what you would do if a manager asked you to use it as one.

What to bring as evidence

Three team improvements with the situation before and after, ideally with a flow measure attached
A retrospective format you designed or adapted, and what it uncovered
A dependency or impediment you resolved across team boundaries
An example of a practice you changed or dropped, with the reasoning
Your certifications, plus a specific thing you do differently because of the training
A conflict within a team that you helped resolve without escalating it

Common mistakes

Reciting the scrum guide instead of describing what you did with a real team
Describing the role as running ceremonies rather than improving how the team works
Answering every scenario with escalation to a manager
Treating velocity as a productivity measure, which delivery leads notice immediately
Talking over the panel in a facilitation exercise instead of drawing others out
Being dogmatic about practices in an organisation that is visibly hybrid

Questions to ask them

?
What does the product owner role actually look like here — is it one person per team, and are they available?
?
When a team here says something is blocked, what happens, and how long does it typically take?
?
How is delivery progress reported upwards, and is any team-level metric used as a target?
?
What was the last process change a team made on its own initiative?
?
How many teams would I support, and what does the organisation expect me to do for each?
?
Where does this organisation most want to improve — predictability, quality, or speed — and who decided that?

Frequently Asked Questions

Do I need a certification to be taken seriously?

A basic certification gets you past CV screening in most organisations and is cheap enough to be worth having. It carries almost no weight in the interview itself, where the panel is looking for specific things you changed on a real team. Do not build answers around what a course taught you.

What if my team was not doing textbook scrum?

Say so plainly — almost none are, and candidates who claim otherwise invite awkward follow-ups. Describe what you actually ran, why it diverged, and whether that divergence was a deliberate adaptation or an unresolved problem. Interviewers respect the distinction.

How do I answer when they clearly want a delivery manager?

Decide before the interview whether you want that job. If you do, lead with dependency management, forecasting and reporting, and be explicit that you are comfortable with delivery accountability. Trying to coach the panel out of their model during the interview rarely ends well.

Is a live facilitation exercise common?

It is increasingly common and it is where most candidates are separated. You will typically be given a scenario and asked to run a short retrospective or planning discussion with the panel acting as the team. Practise with people who will not be gentle.

Can I practise the assessment part in advance?

It is worth doing at least once before the stage that counts. Import the role into Cohesyve and run a scrum master simulation — you get a scored report covering your facilitation choices, coaching approach and delivery reasoning, and a pathway for whatever came out weakest. Your first three scored assessments are free, no card needed.

Practice

What a Scrum Master assessment tests, and how it's scored →

Career guide

What a Scrum Master actually does, and where the path leads →

Prepare for another role

Solutions Architect →Network Engineer →IT Support Specialist →Financial Analyst →