Last updated: November 6, 2026
By Tom Kenaley, Senior Partner and President, KORE1
The best agile coach interview questions make candidates switch between teaching, facilitating, mentoring, and coaching on a live problem, then defend what they measured and how they handled an executive who disagreed. Recited framework knowledge tells you almost nothing.
Everybody asks the resistance question. “How do you handle resistance to change?” A health insurer in Denver ran four finalists through its loop last year, and all four gave nearly the same answer. Meet people where they are, find the early adopters, celebrate small wins. The panel scored them within a point of each other. They picked the one with the most certifications, and she lasted five months.
The answer wasn’t wrong. It was memorized. Anyone with two years in this work has heard it in every loop they’ve sat through.
When the same insurer came back to us for the replacement, we swapped the resistance question for one about a specific director in their claims systems group who had already sat through two failed rollouts and said so in meetings. Three finalists. Three very different answers. One of them asked who the director’s boss was before saying anything else. That was the hire, and she’s still there.
I run the search side of our agile coach staffing practice, and this page is the question bank we hand clients. It’s built for hiring managers, though candidates are welcome to read it. Honest disclosure on money. KORE1 gets paid when a coach we found is hired. You don’t need us for any of this.
Some ground already has a home. Whether you need a coach at all is covered in our guide on how to hire an agile coach. So is the live retrospective. What each scope level costs is in the agile coach salary guide. Team-level questions live in our scrum master interview questions. What to put in the posting itself is in our job description for an agile coach. This page is just the questions, plus what a strong answer and a weak one sound like.
What an Agile Coach Interview Is Really Testing
An agile coach interview tests whether a candidate can improve how several teams and their leaders deliver work, by moving deliberately between teaching, mentoring, facilitating, and coaching. Good questions put a real problem in front of the candidate and watch which stance they pick, when they switch, and why.
The ICAgile Agile Coaching certification, the ICP-ACC that shows up on half the resumes you’ll read, describes its course as building “facilitation, teaching, mentoring, and team coaching skills.” So the candidate has probably been trained on the vocabulary. Fine. Vocabulary is cheap. The thing you can’t fake in a 45-minute conversation is picking the wrong stance and noticing.
Most companies already “do agile,” and most of them aren’t happy with it. In Digital.ai’s 17th State of Agile report, released in January 2024 from a survey of 788 software professionals, 71% said they use agile in their development lifecycle, but only 11% of agile users called themselves very satisfied, and just 43% of medium and large companies said enterprise agile worked very or somewhat well. The barriers named in the release were organizational resistance, mixed approaches, internal silos, and a lack of understanding among leadership. Not one item on that list is a framework problem.
So the coach you’re hiring will mostly be walking into a company that tried already. Ask questions that assume that.
Coaching Stance Questions
Start here. These five tell you more than the rest of the loop combined, and they work best asked about the candidate’s own past engagements before you give them a hypothetical.
A scrum master you’re coaching says, “Just tell me what to do.” Do you?
Sometimes, and the strong candidates say so without apologizing. If the scrum master is three weeks into the job and the sprint review is tomorrow, teaching is the right stance, and refusing to answer in the name of “coaching” is just unhelpful. If the same person has run forty sprints and keeps asking, the candidate should get curious about why. Is it confidence? A manager who punishes mistakes?
Listen for the switch. A good answer names the conditions under which they’d tell, and the conditions under which they’d ask a question back. A weak answer picks one stance and defends it as a philosophy. “I never give answers. I help people find their own.” That sounds wise for about a week.
Tell me about a time you used the wrong stance.
Everyone has one. A program coach we placed with a payments company in Irvine told this one in her interview, and I’ve repeated it since. She spent two months asking open questions of a release train engineer who, it turned out, had never seen a working PI planning event and had no picture of what one looked like. He didn’t need coaching. He needed someone to run one with him. She lost about eight weeks to that, and she said the number out loud.
Specifics are the test. Weeks, roles, what they changed afterward.
How do you decide when a team doesn’t need you anymore?
Short question. Long answer, if the candidate is good. Expect something concrete, like the team running its own retrospectives without the coach in the room, or a scrum master who now coaches a newer one. Ask how many of their past teams they actually left. A coach who has never ended an engagement on purpose has a business model, not a practice.
A team lead disagrees with you in front of their team. What happens next?
Most candidates go straight to “I’d take it offline.” Okay. Then what? The better answers treat the disagreement as information. Maybe the team lead is right. One candidate in a fintech search answered this by asking, “Was I wrong?” before anything else, which the panel loved and which I’d normally call a little rehearsed, except he followed it with a story about being wrong.
Walk me through a coaching conversation you had last month. Not the outcome. The questions you asked.
This is the closest thing to a work sample you’ll get without a live exercise. Strong coaches can reconstruct the actual questions. Weak ones summarize. “We talked through the team’s challenges and aligned on next steps.” Aligned on what? Ask twice. If they can’t reproduce a single question they asked, they probably didn’t ask many.
Facilitation and Teaching Questions
Facilitation gets tested live in the hiring guide’s retrospective stage, so keep these short and use them in the phone screen to decide who earns that stage.
- “Your PI planning has 140 people in a hotel ballroom and by 2 p.m. two trains are refusing to commit. What do you do in the next hour?” Look for a sequence, and for whether they protect the dependency board or abandon it.
- Ask them to explain a work-in-progress limit to a VP of finance in two minutes. No Kanban jargon allowed.
- “Which workshop do you run most, and what did you cut from it last time?” Coaches who never cut anything are running someone else’s slides.
- Remote facilitation. Miro, Mural, whatever they use. How do they get the quiet engineer in a distributed team to say something that matters, without cold-calling him in front of twelve people?
That second one is my favorite, by a wide margin. It’s teaching under a constraint, and the constraint exposes whether the candidate actually understands flow or just knows the words for it.
Questions for the Executive Layer
This is where enterprise coaches earn the money and where a lot of very good team-level coaches stall. The salary guide puts the jump from program to enterprise coach at roughly $35,000 in the middle of the band. These questions are how you find out whether a candidate can do the job on the other side of that jump.
The CTO wants a date for a feature nobody has broken down yet. You’re in the room. What do you say?
Strong candidates don’t lecture the CTO about estimation. They offer something the CTO can use, like a range, a date for a better date, or a smaller slice that can be committed now. A weak answer explains why dates are an anti-pattern, which is true in a conference talk and fatal in a quarterly planning meeting.
Who was the most senior person you coached, and what did they change?
Ask for the title. Then ask what the person did differently six months later. Not what they agreed to. What they did. A candidate who coached a COO into killing a funding gate that required three steering committee approvals has a real answer. A candidate who “ran leadership workshops” may also have one, but you’ll need to dig.
Your sponsor goes quiet. Two meetings missed, budget review coming. How do you get them back?
Every coach loses a sponsor eventually. The strong answer has a move ready before it happens, usually a short written update tied to something the sponsor already reports upward, plus a direct ask for 20 minutes. The weak answer waits. Ask, too, what they’d do if the sponsor never came back. “Finish the contract and leave a handoff plan” is an honest answer and a good one.
Measurement Questions
Velocity will come up. Let it. The principles behind the Agile Manifesto called working software the primary measure of progress back in 2001, and a coach who still offers story points as proof that a transformation worked is reporting a number the teams themselves can inflate whenever they like.
So ask what they measured on their last engagement, and why that, and who looked at it. Good answers name a handful of things, typically lead time from commit to production, the share of planned objectives that actually shipped, or how many cross-team dependencies were discovered late. If your teams already pull DORA metrics out of GitLab, Jira, or Azure DevOps, tell the candidate and ask which of those numbers they’d trust and which they’d ignore. Then ask the harder one. What did they measure that turned out to be useless?
The 2026 Additions
Two years ago nobody asked an agile coach about AI. Now almost every client does, because engineering teams are using GitHub Copilot, Cursor, and Claude in the daily loop, and planning practices built around a predictable sprint haven’t caught up with work that sometimes finishes in an afternoon.
- “A team’s throughput doubled after they adopted an AI coding assistant, and their defect escape rate went up by half. What do you look at first?”
- How would they adjust sprint length, or would they at all?
- Ask what happens to story point estimation when a developer can generate a first draft of a feature in twenty minutes. Some candidates have thought hard about this. Some are hearing it for the first time, and that’s fine, as long as they reason through it out loud instead of reaching for a slogan.
How to Score the Answers
Write the strong and weak signals down before the first interview, not after. Here’s the sheet we give clients.
| Question Area | Strong Signal | Weak Signal |
|---|---|---|
| Stance switching | Names when they’d teach and when they’d ask | One stance, defended as a philosophy |
| Wrong-stance story | Weeks lost, roles involved, what changed | “I learned to meet people where they are” |
| Ending engagements | Practices still running without them | Every engagement ended when budget did |
| Executive pressure | Gives the CTO something usable now | Explains why dates are bad |
| Measurement | Outcome measures, plus one that failed | Velocity as the scoreboard |
| AI-era planning | Reasons from throughput and quality data | A slogan about AI and agility |
Score each row one to four, independently and in writing, before anyone on the panel says a word about the candidate, because the first strong opinion voiced in a debrief has a way of becoming everybody’s opinion. If two interviewers are three points apart on the same row, they heard different things, and that’s worth ten minutes of the debrief.
Answers That Cost a Candidate the Offer
A few. Not many.
Success measured in rollout counts is the first. “I rolled SAFe out to 40 teams” describes a deployment, not a result, and when you ask what got better for customers the answer tends to drift. Blaming leadership for every failed engagement is the second, and it’s a subtle one, since leadership understanding really is one of the barriers the State of Agile release names. But a coach whose stories all end with “the executives didn’t get it” has never once figured out how to help them get it, which was the job. Third is any candidate who refers to “my framework” more than twice. And the last is quieter. Ask them what they’d do in their first week, and if the answer arrives fully formed, with a roadmap and a maturity assessment and a training calendar, they wrote it before they knew anything about your company.
If You’re the Candidate
Bring real numbers. Team counts, months, the title of the person who pulled your budget. Bring one story where you got it wrong, and tell it plainly. Hiring panels have heard the polished version of every agile answer, and the candidates we see get offers are almost always the ones who sound like they’re remembering something instead of reciting it. If a panel asks you only framework questions, it’s fair to ask them what’s actually broken. You’ll learn whether you want the job.
Questions Hiring Panels Send Us
How many interview rounds should an agile coach loop have?
Four or five, including at least one live exercise with your own team, finished inside two weeks so strong candidates don’t take another offer while you schedule.
The full stage-by-stage loop is in the hiring guide. KORE1’s average time-to-hire across IT roles is 17 days, and agile coach searches run a bit longer, mostly because the scope conversation takes a week by itself.
Should the same questions be used for a team coach and an enterprise coach?
Keep the stance questions identical and swap the weight, so team-level candidates spend more time on facilitation and enterprise candidates spend more time on the executive and sponsor questions.
Is a take-home exercise fair for a coach?
A short written one is fair, such as a one-page read of an anonymized team’s metrics, but skip anything over two hours, because senior coaches mid-engagement will simply decline.
Pay for it if it uses real company data. A few hundred dollars removes the “free consulting” objection, and we’ve seen it lift completion rates among candidates who already have offers in hand.
Who from our side should sit on the panel?
The executive sponsor, one scrum master or delivery lead the coach would work with, and one skeptic from engineering, ideally someone who has said out loud that the last transformation was a waste of time.
Leave HR’s culture screen for the end. Put the skeptic in the middle. You’ll learn more from the skeptic’s debrief than from anyone else’s.
Do certifications deserve their own interview questions?
Rarely, since an ICP-ACC, SAFe SPC, or CSM proves a course was finished, and one question asking what they disagreed with in that course tells you more than five questions about its content.
Put the Real Problem in Front of Them
The Denver insurer still uses the director question, and their current coach now asks it of every scrum master candidate too. That’s the whole trick, honestly. Swap the generic prompts for ones built from your own teams, your own stuck sponsor, your own CTO with a date in mind, and the candidates sort themselves.
We’ve filled agile and delivery roles across 30+ U.S. metros for more than twenty years, our recruiters average 15+ years in the business, and 92% of the people we place are still in the seat a year later. A lot of these engagements start on contract staffing terms before anyone talks about a permanent seat. If you want a second read on your question set, or a slate of coaches who’ve already handled questions like these, talk to a recruiter on our agile desk. We’ll tell you which of these questions will matter most for your seat.
