On this page
Questions to practise
How do you run a daily stand-up?
They want to see if you keep meetings short, focused and useful for the team.
Give concrete habits. For example: fifteen minutes, a fixed order, each person speaks for one minute. Say that you talk about blockers, then solve them after the meeting with the right people.
What does a good retro look like for you?
Retros show how you help a team learn and improve over time.
Describe the steps: what went well, what was hard, what we try next. Mention one clear question you use. Say how you make sure the team follows up on one or two actions.
Our stand-ups take thirty minutes and people stop listening. What would you do?
They have a real problem and want to hear a practical solution.
Stay calm and practical. Suggest a time limit, a clear order, and moving long talks to after the stand-up. Give a real example from a past team, and say what changed.
Tell me about a retro you ran recently.
They want a real story, not theory, to see how you work in practice.
Say when it was, what the team discussed, and what you did as the facilitator. End with one action the team agreed and what happened next.
Tell me about a real conflict in a team you worked with.
Disagreements happen. They want to know how you help people work through them.
Say what the disagreement was, what you did yourself, and how it ended. For example: you met each person, listened, then helped them agree a rule together.
What did you do yourself to help them agree?
They want to hear your own actions, not only what the team did.
Use 'I' sentences. 'I met each person.' 'I asked questions.' 'I suggested a short trial.' Keep it simple and honest. Say what you learned.
How do you remove a blocker for the team?
Clearing problems fast is a key part of the Scrum master job.
Name one real blocker, who you talked to, and how fast it was cleared. For example: waiting for test servers, you spoke to the IT manager, and the team got them in two days.
What happens when you cannot remove a blocker quickly?
They want to know how you handle pressure and keep people informed.
Explain how you tell the team and the product lead early, look for a short-term solution, and keep following up. A short real example helps.
How do you help quiet team members speak in meetings?
Good meetings need everyone's ideas, not only the loudest voices.
Mention simple habits: a fixed order, writing ideas first, or asking a person directly in a kind way. Say what you noticed after you tried it.
What happened next? How did the team change?
They want to see a clear result from your actions.
Finish your stories with a result: shorter meetings, fewer arguments, faster delivery. Use numbers if you can, like 'fifteen minutes instead of thirty'. Be honest if the result was small.
Let me give you an example.
Clara
AI coach
Leo
AI coach
Lines to try
Let me give you an example.
In my stand-ups, each person speaks for one minute.
We keep long discussions for after the meeting.
I met each person separately to understand their view.
I asked the right person for help, and it was fixed in two days.
As a result, the team agreed on a clear rule.
Common questions
How long should my answers be?
Try to speak for about one to two minutes for each answer. Start with a short, clear sentence. Then give one real example. End with the result. If the interviewer wants more, they will ask.
What if my English is not perfect?
That is fine. Use short, simple sentences. Speak slowly. If you do not understand a question, you can say, 'Sorry, could you repeat that, please?' Clear examples matter more than perfect grammar.
Do I need to explain the rules of Scrum?
Usually not in detail. The interviewer wants to hear what you did in real teams. Talk about your habits, your actions and the results. Use Scrum words only when they help your story.