Wrexa Edge All mock interviews →

Scrum Master Agile Scrum Master Interview

Scrum framework depth, servant leadership and facilitation, impediment removal, Agile metrics, and scaling — coach, don't command.

Professional role Global Web-verified 2026-08
Start the Scrum Master mock interview → See all boards

A free AI panel interview that questions you in Scrum Master’s style, follows up when an answer is thin, and returns a scored, evidence-backed report — seeded from your own practice history on Wrexa Edge.

5Interview rounds
10Key topics
3Practice modes
FreeAI mock interview

The Scrum Master interview, in brief

The Scrum Master interview tests both textbook command of the Scrum framework and the softer craft of coaching a team to self-manage. Interviewers separate candidates who have memorised the Scrum Guide from those who can apply it: facilitating events, protecting the team, removing impediments, and coaching without commanding. Expect a blend of framework questions (roles, events, artifacts), scenario questions ("your team missed the Sprint Goal — what do you do?"), and behavioural questions on servant leadership, conflict, and stakeholder management.

A typical loop starts with a recruiter or HR screen on background and certifications (PSM, CSM, SAFe), then one or two rounds with an Agile lead or hiring manager mixing framework depth with real-world scenarios, and often a panel or stakeholder round with engineers or a product owner probing facilitation and collaboration. Some companies add a practical exercise — facilitate a mock retrospective, resolve a role-play conflict, or critique a broken board. The framework is fixed, so differentiation comes from judgement in ambiguous, team-specific situations.

Interview rounds

  • Recruiter / HR screen 20–30 min · non-technical
    Experience, certifications (PSM/CSM/SAFe), team sizes, and the Agile environments you have worked in.
  • Scrum framework & fundamentals 45 min · Q&A
    Roles, the five events, the three artifacts and their commitments, Definition of Done, and the difference between Scrum and other Agile approaches (Kanban, XP).
  • Scenario / situational 45–60 min
    Handling missed Sprint Goals, scope creep, a disengaged team, a dominating stakeholder, or a Product Owner who bypasses the process; you narrate how you coach and facilitate rather than dictate.
  • Behavioural / servant leadership 45 min
    STAR stories on removing impediments, coaching self-management, resolving conflict, and influencing without authority.
  • Panel / stakeholder 45 min
    Cross-functional round with engineers, a PO, or leadership testing communication, metrics literacy, and how you protect and enable the team.

Key topics assessed

Scrum roles, events & artifactsThe Scrum Guide & Scrum valuesServant leadership & coachingFacilitation techniquesImpediment removalAgile metrics (velocity, burndown, burnup)Sprint planning & estimationRetrospective formatsScaling frameworks (SAFe, LeSS, Nexus)Kanban & flow metrics

The defining round

The scenario/facilitation round is the Scrum Master's equivalent of a design interview: given a dysfunctional team situation, you must design an intervention. A strong answer diagnoses the root cause before acting — is a low velocity a capacity problem, an estimation problem, or hidden impediments? — and treats velocity as a diagnostic signal, never a performance target to be gamed. You would describe facilitating the relevant event (a focused retrospective, a refinement session, or a stakeholder conversation), coaching the team toward its own solution, escalating only the impediments the team cannot clear itself, and following up to confirm the change stuck. For scaled contexts you would explain when a framework like SAFe or LeSS is warranted (multiple interdependent teams needing PI Planning or cross-team coordination) and the risks of adopting heavy process prematurely.

Behavioural round

Behavioural rounds assess servant leadership: empathy, active listening, and the discipline to facilitate solutions rather than impose them. Interviewers look for coaching over commanding, patience with team self-organisation, courage to surface impediments and shield the team, and the influence to align stakeholders without formal authority. Ground answers in STAR and show that you helped the team solve the problem rather than solving it for them.

Representative question categories

Patterns in Scrum Master’s style — not verbatim proprietary questions.

  • FrameworkExplain the Scrum events and the commitment attached to each artifact.
  • Servant leadershipHow do you coach a team to self-manage rather than directing it?
  • ImpedimentsWalk through how you identify, track, and remove a blocker the team cannot clear.
  • MetricsHow do you use velocity and burndown without turning them into targets?
  • ScenarioYour team keeps missing the Sprint Goal — what do you do?
  • ScalingWhen would you recommend SAFe or LeSS, and what are the trade-offs?

How to prepare

Do

  • Anchor framework answers in the current Scrum Guide vocabulary — the three accountabilities, five events, three artifacts and their commitments — and be precise about the Scrum Master as a servant-leader, not a manager.
  • For every scenario, diagnose the root cause first and describe coaching the team to its own solution rather than solving it yourself.
  • Treat metrics like velocity and burndown as diagnostic signals; explicitly reject using velocity as a target or a cross-team comparison.
  • Prepare STAR stories for impediment removal, conflict, a difficult stakeholder, and coaching a team toward self-management.

Avoid

  • Describing the Scrum Master as a project manager who assigns tasks, controls timelines, or owns delivery.
  • Using velocity as a performance target or comparing velocity across teams — a classic anti-pattern interviewers probe for.
  • Jumping to solve every impediment personally instead of coaching the team to self-manage and escalating only what it cannot resolve.

Who can apply

Most roles expect hands-on Agile experience and a recognised certification such as Professional Scrum Master (PSM), Certified ScrumMaster (CSM), or a SAFe credential; scaled environments may prefer SAFe SM/SASM. A technical or project-delivery background helps but no specific degree is mandated — treat exact requirements as company-specific.

Scrum Master interview FAQ

What is the difference between a Scrum Master and a project manager?
A Scrum Master is a servant-leader who facilitates the Scrum framework, coaches the team toward self-management, and removes impediments; they do not assign tasks, control the schedule, or own delivery the way a traditional project manager does.
How should a Scrum Master talk about velocity in an interview?
Treat velocity as a diagnostic and planning signal, not a performance target. A strong answer explains using low velocity to uncover root causes and explicitly avoids setting it as a goal or comparing it across teams, which drives gaming and burnout.
When does an organisation need a scaling framework like SAFe or LeSS?
Scaling frameworks help when multiple Agile teams work on interdependent products and need coordinated planning — for example PI Planning for quarterly alignment. For a single team they add unnecessary overhead.
What certifications help for a Scrum Master interview?
Professional Scrum Master (PSM) from Scrum.org and Certified ScrumMaster (CSM) from Scrum Alliance are the most common; SAFe credentials help for scaled enterprises. Certifications open doors, but interviews still test applied judgement in real scenarios.

Practise now

Rehearse the full loop with an AI panel modelled on Scrum Master’s process, in text, voice, or video.

Start the Scrum Master mock interview →

Other company interviews

NTT DATA interview →Optum interview →DXC Technology interview →Nagarro interview →Hexaware interview →IBM interview →SAP Labs interview →Virtusa interview →EPAM interview →Publicis Sapient interview →Thoughtworks interview →UST interview →Zensar interview →Cyient interview →KPIT interview →Birlasoft interview →Google interview →Amazon interview →Microsoft interview →TCS interview →Infosys interview →Accenture interview →Meta interview →Apple interview →Flipkart interview →Wipro interview →Cognizant interview →Capgemini interview →Uber interview →Adobe interview →Swiggy interview →HCLTech interview →Tech Mahindra interview →LTIMindtree interview →Salesforce interview →Atlassian interview →Zomato interview →Mphasis interview →Persistent Systems interview →Coforge interview →Oracle interview →Nvidia interview →Paytm interview →JPMorgan Chase interview →Goldman Sachs interview →Deloitte interview →Cisco interview →Netflix interview →PhonePe interview →Zoho interview →Careem interview →noon interview →talabat interview →Property Finder interview →Tabby interview →Tamara interview →Visa interview →Mastercard interview →PayPal interview →Razorpay interview →LinkedIn interview →Morgan Stanley interview →Bayut & dubizzle interview →Kitopi interview →MNT-Halan interview →Anghami interview →UPSC Civil Services interview →State PSC interview →Defence SSB interview →Police Sub-Inspector interview →Judicial Services interview →Banking PO interview →MBA Admissions interview →Product Manager interview →Security Engineer interview →Cloud Architect interview →Network Engineer interview →IT Support interview →AWS Solutions Architect interview →Software Engineer interview →Financial Analyst interview →Management Consulting interview →Assistant Professor interview →Staff Nurse interview →CA Articleship interview →Medical PG interview →

Verified from

Wrexa Edge is an independent exam-prep platform and is not affiliated with, authorised by, or endorsed by Scrum Master. This guide is based on publicly documented interview practice; it does not reproduce any employer’s internal rubric or question bank, and it does not predict a hiring outcome.