GUIDE 2026

Scrum manager interview questions: How I’d prepare

Josh Fechter
By
Josh Fechter
Josh Fechter
Josh Fechter
Josh Fechter is the co-founder of Product HQ, founder of Technical Writer HQ, and founder and head of product of Squibler. You…
More About Josh →
×

Scrum Manager / Scrum Master interviews reward coaching stories and conflict judgment—not Agile vocabulary bingo. I’d prepare for servant-leadership evidence, impediment removal with specifics, and metrics used as learning—not weapons. Wave7 scrum-manager-interview marker Sep27

Here’s how I’d approach the questions that usually separate coaches from ceremony administrators.

Themes they usually probe

Theme What good sounds like What weak sounds like
Servant leadership Outcomes for the team; you absorb friction “I run the ceremonies”
Impediments Concrete blockers you removed end-to-end Vague “I escalated”
Coaching range Different tactics for PO vs quiet engineer One script for everyone
Metrics Flow, quality, predictability—with caution Velocity as a performance score
Scaling pain Dependencies, politics, fake Agile honesty More meetings as the answer

Question types I’d rehearse

Type Example prompt What I’d show
Motivation Why Scrum Master / Manager? Team outcomes, not ceremony love
Behavioral Tell me about a conflict you facilitated Specifics, your role, lasting change
Situational PO keeps changing sprint scope mid-sprint Options, tradeoffs, coaching path
Technical-adjacent How do you partner with eng on quality? Definition of Done, WIP limits, root cause
Org Leadership wants velocity +20% Reframe to outcomes; protect sustainable pace

How I’d answer a conflict prompt

  1. Context in 20 seconds — team, stakes, who was stuck.
  2. What I did — facilitation moves, 1:1s, data I brought.
  3. Outcome — decision, delivery, or relationship change.
  4. System change — what we altered so it wouldn’t recur.

I’d avoid hero narratives where I “fixed people.” The best stories show the team owning a better working agreement.

Topics I’d study without memorizing the Scrum Guide

  • When Kanban flow metrics beat sprint theater
  • How to coach a PO without becoming a shadow PM — compare Scrum Master vs Product Owner
  • Healthy vs weaponized burndown/velocity conversations
  • Cross-team dependencies without inventing a PMO by accident

Two-week prep plan

Days Focus
1–3 Bank 6–8 STAR stories (conflict, impediment, coaching, metrics)
4–7 Situational drills: mid-sprint chaos, stakeholder squeeze, hiring a SM
8–10 Mock interviews; record yourself; cut jargon
11–12 Read the company’s public engineering blog / product surfaces
13–14 Rest; light review of skills checklist

Pair prep with the skill bar in essential scrum manager skills.

Day-of habits

  • Restate the scenario and who is hurting before prescribing a ceremony
  • Offer two options with tradeoffs (protect sprint vs replan) instead of a single rigid “Scrum says”
  • Name the working agreement you’d update afterward
  • If they push velocity theater, calmly reframe to predictability and quality outcomes

I’d show I can coach toward outcomes without becoming a project manager in disguise.

I’d also prep one short take on “fake Agile”: lots of ceremonies, little inspection/adaptation. Interviewers at serious companies listen for whether you’ll protect learning loops when leadership wants theater.

Skills evidence still beats slogans—pair stories with the checklist in essential scrum manager skills when you self-assess gaps before the loop.

FAQ

Do I need Scrum certifications to pass?

Sometimes they help screening; rarely they replace stories. I’d rather show a before/after on team predictability than flash a badge alone.

Is “Scrum Manager” the same as Scrum Master?

Often overlapping. Some orgs use Manager for people-leadership or multi-team scope. Ask what success metrics and direct reports look like before assuming ceremony-only work. Context: Scrum overview.

How technical should answers be?

Fluent enough to partner on quality and delivery risks; not a substitute for eng leads. Depth on facilitation and systems beats fake coding credentials.

My take

I’d prep Scrum Manager interviews as evidence of coaching and systems change—not glossary recitation. Strengthen craft with product manager certification when you partner heavily with PMs, and stay current via the Product HQ newsletter.

Josh Fechter
Josh Fechter
Josh Fechter is the co-founder of Product HQ, founder of Technical Writer HQ, and founder and head of product of Squibler. You can connect with him on LinkedIn here.