Scrum Master Interview Questions UK: 8 Real Questions and What Interviewers Want
Most Scrum Master interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 25, each with a note on what the interviewer is really after.
Eight Scrum Master interview questions, and what the interviewer is thinking
1. What is the role of a Scrum Master, and how does it differ from a project manager?
Why they ask: This is almost always the first question and reveals whether you understand servant leadership.
2. Can you walk me through the Scrum events and what you do in each?
Why they ask: They want to confirm you know the framework and how you facilitate it.
3. What are the three Scrum accountabilities, three artefacts and the five values?
Why they ask: A common knowledge check, particularly for those with PSM or CSM certification.
4. The daily stand-up regularly lasts 40 minutes and people are disengaged. What would you do?
Why they ask: This is a classic scenario to see how you coach rather than dictate.
5. How do you run an effective retrospective, and how do you keep them fresh?
Why they ask: Retrospectives drive continuous improvement and are often where Scrum Masters stand out.
6. A stakeholder keeps adding work to the sprint and bypassing the Product Owner. How do you handle it?
Why they ask: They want to see how you protect the team while supporting the Product Owner's authority.
7. Tell me about a time you helped a team improve the way it works.
Why they ask: They want a real example of coaching and measurable change.
8. What does a typical day or week as a Scrum Master involve?
Why they ask: They want to check you understand the real shape of the work, which is mostly not meetings.
A sample answer to question 1
What is the role of a Scrum Master, and how does it differ from a project manager?
The Scrum Guide describes the Scrum Master as accountable for the Scrum Team's effectiveness and for establishing Scrum as defined. I do that by serving the team, the Product Owner and the wider organisation. I coach team members in self-management and cross-functional working, help them focus on creating high-value increments, remove or help remove impediments, and make sure Scrum events happen and are positive and productive. I also help the organisation understand Scrum, and work with leaders on removing obstacles that the team can't solve alone. A project manager typically plans, assigns tasks, tracks against a schedule and reports on progress. I don't assign work or hold the team accountable for dates. Instead I create the conditions for the team to decide how to deliver, and I measure my success by how well the team improves and delivers value rather than by control.
Common mistake to avoid: Describing yourself as team manager; Reducing the role to running meetings
Want the rest?
Full model answers, key points and common mistakes for all 25 questions are on the Scrum Master interview questions page. The first five are free, no sign-up needed.

Comments