Preparation isn't cramming Scrum trivia. It's three things: know your stories, know the company and the role, and rehearse out loud. Most candidates over-study theory and under-prepare the parts that actually win, telling a clear story, asking sharp questions, and sounding calm. Get the run-up right and the interview feels like a conversation you've already had.
Key takeaways
- A week or two of focused prep beats a frantic all-nighter. Spread it across stories, research and rehearsal.
- Map three to five stories to the competencies a panel grades, so any question has an answer ready.
- Research their world, the product, how they deliver, the people, so you can talk about them, not just yourself.
- The boring logistics (a tested setup, a planned intro, good questions) prevent most of the avoidable losses.
A prep timeline that works
You don't need weeks of full-time study. You need the right thing at the right time. Here's how to spread it so nothing's left to the last minute.
Build your foundation
Shape three to five STAR stories and rehearse them out loud. Read the job posting closely and research the company and how they deliver. This is where most of the real work lives.
Sharpen and personalise
Look up your interviewers, prepare three sharp questions to ask, and map your stories to what this specific role needs. Do one practice run, ideally with someone playing the interviewer.
Logistics and rest
For remote, test your camera, mic and the meeting link. For onsite, confirm the route and timing. Re-read your stories once, lay out anything you need, and then stop. Sleep beats cramming.
Show up calm
Arrive or log in early, take a breath before each answer, and treat it as two practitioners talking. Lead with your stories, ask your questions, and let preparation carry you.
Close it out
Send a short, specific thank-you within a day. Note what they asked while it's fresh, and bank any new stories for next time. Then let it go.
Research the company and the role
The fastest way to stand out is to walk in able to talk about their world. You don't need to become an expert, you need enough to ask good questions and tailor your answers. Five things are worth the time.
- The job posting, closely. What are they actually hiring for, a pure Scrum Master, a delivery lead, a hybrid? Their words tell you which competencies to lead with.
- The product and the business. What do they make, who pays for it, and what does delivery look like there? You'll sound like an insider, not a tourist.
- How they run delivery. Single-team Scrum or scaled Agile? If they're an enterprise on SAFe, brush up on Agile Release Trains and PI Planning.
- Recent news. A funding round, a launch, a reorg. One relevant, current reference shows you did the work.
- The people. Look up your interviewers and the team. Knowing who you're talking to takes the edge off the nerves and helps you read the room.
Map your stories to what they grade
Panels rate a handful of competencies, so prepare a story for each. The trick is that one good story often covers two or three, so you need a small, sharp set, not a long list. Fill this in for your own experience before you walk in.
| Competency they grade | Your story |
|---|---|
| Conflict resolution | a disagreement you defused... |
| Delivery under pressure | a slip you recovered, or a tough release... |
| Influence without authority | a time you moved people without power... |
| Failure & learning | a real mistake and what you changed... |
| Stakeholder management | a difficult stakeholder you turned around... |
Build each one with the STAR method, then rehearse it out loud until it's tight. A story you've said three times sounds calm and specific; one you've only thought about comes out as a ramble.
On the day
By now the prep is done, so the job is to show up well and not beat yourself. A few things make the difference between a good performance and a nervous one.
First impression and nerves
Arrive or log in five minutes early. A short walk or a few quiet minutes beforehand settles you more than a last-minute re-read. Slow your pace, take a breath before each answer, and remember you're a practitioner talking shop, not a student being examined.
During the answers
Lead with your prepared stories, structure them with STAR, and check in if a question is broad ("happy to go deep on any part of that"). It's fine to take a moment to think; a considered answer beats a fast, shapeless one.
If it's remote
Look at the camera, not the faces, when you speak. Have your notes and questions just off-screen, keep water nearby, and close everything that might ping. A clean, tested setup quietly signals that you run things well.
Are you actually ready?
Tick what's genuinely done. The bar fills as you go, and the verdict tells you where to put your last hours.
Prep your answers on paper too
The free Interview Answer Scoresheet helps you break down and score each story as you build it, one sheet per question.
The follow-up
The interview isn't quite over when you log off. A short, well-judged follow-up is a cheap, positive signal, and how you handle the wait says something too.
The thank-you note
Send a short one within a day. Thank them, reference one specific thing from the conversation, and reaffirm your interest in a line. Keep it genuine and brief. It rarely wins the job alone, but its absence is occasionally noticed.
While you wait
Note what they asked while it's fresh and bank any new stories you wish you'd told. If you don't hear back by the date they gave, a single polite nudge is fine. Then keep applying, because the best protection against one outcome is more than one process.
Prepare like it matters, then perform like it doesn't. The calm comes from the work you did before you walked in.