Interview questions by role

Scrum master interview questions

Scrum master interviews test whether you understand Scrum well enough to apply it with judgement, not just recite it. Expect questions about what you do day to day, how you run a retrospective that leads to change, what you do when a stakeholder pushes extra work into a sprint, how you fix a daily scrum that has become a status meeting, how you remove impediments, how you work with a product owner, and which metrics you use without turning them into targets. Interviewers want real teams, real problems and what changed because of you.

Mock Interview Copilot practice room: an AI interviewer asks a follow-up question while the candidate's spoken answer and pace appear in the transcript
Practising answers out loud in Mock Interview Copilot: the interviewer follows up when an answer is vague, and your pace and pauses are measured.

How the interview usually runs

The process usually includes a screen, an interview with an agile coach, delivery lead or engineering manager, and often a conversation with members of the team or a product owner. Some ask you to facilitate a short retrospective with the panel. Job adverts often mention a certification such as Certified ScrumMaster (CSM) or Professional Scrum Master (PSM), but the interview itself focuses far more on experience.

The panel checks that you know the framework: the three accountabilities (product owner, developers and scrum master) and the events (the sprint, sprint planning, daily scrum, sprint review and sprint retrospective). More than that, they want to know how you behave when the framework meets reality: a manager who wants status reports, a team that misses every sprint goal, a product owner who is never available. Answers that show you coach and facilitate, rather than assign tasks and chase people, come across strongest.

Common questions and what the interviewer is checking

  1. What does a scrum master actually do day to day?

    What they are checking: That you describe serving the team, the product owner and the wider organisation: facilitating, coaching, removing impediments and improving how work flows, not acting as a project manager.

  2. How do you run a sprint retrospective that leads to real change?

    What they are checking: Varied formats, a safe space to speak honestly, a small number of actions with owners, and checking at the next retrospective whether they happened.

  3. A stakeholder asks the team to add urgent work in the middle of a sprint. What do you do?

    What they are checking: That you direct them to the product owner, help everyone see the trade-off against the sprint goal, and protect the team without being obstructive.

  4. The daily scrum has turned into a status report to the manager. How do you fix it?

    What they are checking: Knowing the daily scrum is for the developers to plan their day toward the sprint goal, and coaching both the team and the manager on that purpose.

  5. Tell me about an impediment you removed.

    What they are checking: A real blocker outside the team's control, how you found it, who you worked with to remove it, and the effect on the team's flow of work.

  6. The team keeps missing its sprint goal. What do you look at?

    What they are checking: Curiosity rather than blame: refinement, sprint planning, unplanned work, dependencies and capacity, with the team finding the cause together.

  7. How do you work with a product owner who is rarely available?

    What they are checking: Coaching the product owner on the role, finding a rhythm that works, and making the impact on the team visible, rather than taking over the role yourself.

  8. Which metrics do you use, and how do you stop them being misused?

    What they are checking: That you use measures such as velocity or cycle time for the team's own planning and improvement, never to compare teams or as targets.

  9. What does servant leadership mean to you in practice?

    What they are checking: A concrete example of leading by enabling others: removing obstacles, building the team's self-management, and stepping back as the team matures.

How to structure a strong answer

Use STAR, and be clear about your role: in most good scrum master answers you facilitate or coach, and the team makes the change. Name the part of Scrum involved, but spend most of the answer on what people did differently.

Example answer

Tell me about a time a stakeholder put pressure on the team during a sprint.

I was scrum master for a team of seven building an internal billing tool. Halfway through a sprint, a sales director went straight to two of the developers and asked them to add a new report for a client meeting the following week. They started on it, and by the review we had missed the sprint goal.

I didn't want to block the director, because the request was reasonable. I met him with the product owner, explained how the sprint goal worked and showed him what had slipped because of the report. We agreed that urgent requests would go to the product owner, who would decide with the team whether to swap something out. I also coached the developers on saying “let's check with the product owner” without feeling they were turning down a senior person.

Over the next four sprints, two urgent requests came in through the product owner and were swapped in openly, and the team met its sprint goal each time.

Mistakes to avoid

Frequently asked questions

What questions are asked in a scrum master interview?

Expect what a scrum master does day to day, running retrospectives, mid-sprint requests from stakeholders, fixing a daily scrum that has become a status meeting, removing impediments, missed sprint goals, working with product owners, metrics and servant leadership.

Do I need a certification to become a scrum master?

Job adverts often mention a certification such as CSM or PSM, and some list it as required. Interviews still focus on experience, so be ready with examples of facilitating, coaching and removing impediments whether or not you hold one.

How do I answer scrum master questions with no scrum master experience?

Use times you facilitated meetings, improved how a team worked, coached colleagues or removed a blocker in another role, such as developer, tester or project coordinator. Show you understand Scrum and how you would apply it.

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

A project manager usually plans and controls the work and reports on it. A scrum master helps a self-managing team and the organisation use Scrum well, coaching and removing obstacles rather than directing the work.