HeroApply
Auto Apply to hundreds of jobs in a few hours
English (US)EspañolItalianoPortuguêsFrançaisDeutsch日本語한국어
Sign up

Agile Coach interview questions and how to answer them

An Agile Coach interview isn't a Scrum quiz. The panel already assumes you know what a sprint review is. What they're testing is whether you can change how people work when you have no authority over them, and whether you'll tell a director something they don't want to hear.

11 questions8 minute read

Part 1

1.How is coaching a team different from managing it or consulting for it?

Why they ask

This is the core of the job. Plenty of candidates call themselves coaches but really prescribe fixes. The panel wants to hear that you know the difference between telling, teaching, and coaching, and when each one fits.

How to answer

  • Name the stances plainly: teaching when a team lacks knowledge, mentoring when they need your experience, coaching when they have the answer and need to find it
  • Give a real moment where you chose to ask instead of tell, and what the team came up with
  • Admit when you've stepped in and directed, and why that was the right call at the time
  • Say how you decide which stance to take, such as how new the team is or how urgent the problem

2.Tell us about a team you coached that kept improving after you left.

Why they ask

The whole point of a coach is to make yourself unnecessary. A team that falls apart when you leave means you were a crutch, not a coach.

How to answer

  • Describe where the team started, in plain terms, such as retros that produced the same complaints every time
  • Explain what you did to build their own ability, like rotating facilitation or teaching the Scrum Master to run hard conversations
  • Say how you knew they were ready and how you stepped back gradually
  • Share how you learned it stuck, such as a message from the team or a later check-in

3.A senior leader wants agile but keeps setting fixed scope and fixed dates from the top. What do you do?

Why they ask

This is the most common reason transformations fail. They want to see whether you'll coach upward or just keep the teams busy with ceremonies.

How to answer

  • Start by understanding what the leader is actually worried about, usually predictability for a customer or the board
  • Show them data from the teams, like a cumulative flow diagram or throughput from Jira, so the conversation is about evidence
  • Offer a small experiment, such as forecasting one release with ranges instead of a single date
  • Be honest that you'd tell the leader directly if their approach was undercutting the teams
4.How do you measure whether your coaching is working?

Why they ask

Coaching is easy to fake and hard to prove. Hiring managers are tired of coaches who report ceremony attendance as progress.

How to answer

  • Separate outcome signals, like cycle time and how often teams ship, from vanity counts like story points completed
  • Mention qualitative signals too: whether teams raise problems on their own and whether retros lead to real changes
  • Explain that you agree on what better looks like with the team and their manager up front
  • Warn against turning flow metrics into targets, because teams will game them
5.Walk us through how you'd start your first few weeks here.

Why they ask

Coaches who arrive with a rollout plan before they've met anyone tend to get ignored. The panel wants to see you observe before you act.

How to answer

  • Spend the early days listening: sit in standups, planning, and retros without changing anything
  • Hold one-on-ones with Scrum Masters, managers, and a few engineers to hear what frustrates them
  • Build a short picture of the system, including where work waits and who makes which decisions
  • Agree with your sponsor on a small first focus rather than a full transformation roadmap

Part 2

6.Scrum, Kanban, or SAFe: how do you decide what a team or department should use?

Why they ask

They want to see that you're not loyal to a single framework. A coach who pushes Scrum onto a support team with unpredictable work isn't reading the situation.

How to answer

  • Start from the kind of work: planned product work, interrupt-driven operations, or many teams building one product
  • Explain when Kanban fits better, like a platform team handling requests from everywhere
  • Be honest about what scaled frameworks cost in overhead and when that's worth it
  • Say you'd let teams adapt the framework once they understand why each part exists
7.A Scrum Master you're coaching is running every ceremony but nothing improves. How do you help them?

Why they ask

Coaching other coaches and Scrum Masters is a big part of this job. They want to see you develop someone rather than replace them.

How to answer

  • Observe a few of their sessions before saying anything
  • Ask them what they think is happening and what they've tried
  • Pick one skill to work on, such as asking open questions in retros instead of summarizing
  • Pair with them, then step back and debrief after they run it alone
8.Tell us about a time a team or leader rejected your coaching.

Why they ask

Every coach gets pushed back on. They want to hear how you react, and whether you learn from it or blame the client.

How to answer

  • Describe the pushback honestly, including what you said that didn't land
  • Explain what you found out about their real concern once you listened
  • Show what you changed in your approach
  • Be willing to say when you walked away from a battle that wasn't worth it
9.How would you run a retro for a team that has stopped talking in retros?

Why they ask

A silent retro is a classic sign of low trust. This checks your facilitation toolkit and whether you look for the cause.

How to answer

  • Look for the cause first, such as a manager attending or past action items that went nowhere
  • Change the format: anonymous input in Miro or Mural, small pairs before the whole group
  • Pick one action the team controls and follow it through visibly
  • Talk privately with the manager if their presence is the issue
10.What does psychological safety look like on a team, and how do you spot when it's missing?

Why they ask

It's the ground coaching stands on. They want concrete signs, not a textbook definition.

How to answer

  • Name visible signs: people admit mistakes in standup, juniors disagree with seniors in planning
  • Name the warning signs: bad news only comes out at the sprint review, or never
  • Describe something you did to rebuild it, like the lead going first in admitting a mistake
  • Connect it to delivery, since hidden problems show up later as missed releases

Part 3

11.Why do you want to move into coaching, or keep doing it?

Why they ask

Coaching is slow and often thankless. They want to know you understand that and still want it.

How to answer

  • Give a specific moment that made you want this work
  • Be honest about the frustrating parts you've already lived through
  • Say what kind of coaching you're best at, such as team level or leadership
  • Link it to what this company is trying to do

Questions to ask them

Ask at least two. It shows you're picking them too.

  • Who sponsors this role, and what would they need to see from me to call it a success?
  • What's been tried before to change how teams work here, and why did it stall?
  • How much access will I have to the leadership team, not just the delivery teams?
  • Which framework are you committed to, and how much room is there to adapt it?
  • What happened to the last coach in this role?

Related interview guides

Scrum MasterProduct Owner