Last updated: November 4, 2026
By Tom Kenaley, Senior Partner and President, KORE1
You hire an agile coach by first writing down what is broken and who sponsors fixing it, then matching contract or full-time to how long it will take, then watching finalists facilitate your own team before anyone looks at certifications. Plan on about three weeks. Transformation leads run six to nine.
Most companies interview agile coaches with a loop that was built for somebody else, usually the project manager loop with an HR culture screen bolted onto the end, and occasionally a Confluence page titled “Interview Kit v3” that a consultancy left behind in 2022. Three 45-minute conversations, a panel, the same question about handling resistance to change. Anyone with two years in the field has a polished answer to that one, so the panel ranks people on how well they talk about coaching, and I’ve watched that process produce some very articulate hires who left a release train exactly where they found it.
Our agile coach staffing desk runs a different process, and this is it, from deciding whether you need a coach at all through the 90-day check that tells you whether the hire is working. KORE1 earns a fee when a search closes through us, so read it with that in mind. None of the steps need a recruiter, and a couple of them may talk you out of the hire.
Do You Need an Agile Coach, or Something Cheaper?
An agile coach is a practitioner who improves how a group of teams, and the leaders above them, plan and deliver work. Unlike a scrum master, who serves one team, a coach works across teams and with executives, teaching, facilitating, and coaching until the organization can run its own practices without them.
The 2020 Scrum Guide doesn’t contain the phrase “agile coach” anywhere. It assigns “leading, training, and coaching the organization in its Scrum adoption” to the Scrum Master, which works fine at three teams and falls apart somewhere around eight, because one person can’t serve their own team’s daily needs while also rewiring how a VP of product funds work across a whole portfolio. The coach title is an industry answer to that scaling gap. Which means the first thing to establish isn’t which coach. It’s whether your problem actually sits above the team level, where a coach works, or inside the teams, where a scrum master is cheaper and better suited.
Forrester’s Diego Lo Giudice, summarizing the firm’s State of Agile Development 2025 research in January 2025, reported that 95% of professionals still call agile critical to their operations, 61% have run agile practices for more than five years, and only 7% of teams have reached full proficiency. Nearly everyone has adopted it. Almost nobody is great at it. Coaches get hired into that gap, and so do a fair number of people who probably shouldn’t have been.
A rough sort we use on the first call.
- If standups, sprint planning, and retros either don’t happen or have turned into status meetings, start with a scrum master hire. You’ll spend around $40,000 a year less and fix the actual problem.
- Five or six teams that each run well on their own, sharing a codebase or a release calendar, with nobody owning the dependencies between them. That one’s a coach, usually program level.
- “Which framework should we buy, SAFe or LeSS or something homegrown?” is a six-week consulting question, not a year-long coaching seat.
- When a CTO has put the word transformation on a board slide and nobody below the CTO can describe what finished looks like, you need a senior enterprise coach, and you should budget the six-to-nine-week search that comes with it.
- Late delivery caused by under-staffing, a vendor holding up an API, or estimates that were wrong from the start won’t be fixed by any coach. Hire engineers.
Most of the expensive mistakes we see live in the fourth category.
Write the Problem Statement Before the Job Description
Nearly every stalled agile coach req that reaches my desk was assembled from other companies’ postings, SAFe 6.0 required, ICP-ACC preferred, “drive enterprise agile transformation,” eight to ten years of experience, and not one line about what is actually broken at this company, on these teams, this year. A strong coach reading that can’t tell whether your problem is one they’ve solved before, so they pass on it, and the applicants who do show up are mostly the ones who apply to every agile posting Indeed serves them that week.
Before anyone opens the JD template, write four sentences: how many teams and roughly how many people are in scope, what is going wrong in terms you could point to on a Jira dashboard or a missed quarterly date, who the executive sponsor is by name and title, and what has to be true six months from now for you to call the engagement a success. If the fourth sentence won’t come, wait, because a coach brought in to discover the goal will spend the first quarter doing that discovery at around $120 an hour, and they’ll be good at it, and you’ll still have paid roughly $60,000 to learn what you wanted. Once the four sentences exist, our agile coach JD template turns them into a posting.
The sponsor sentence is the one people leave out most. It’s also the first thing a strong candidate asks about on the screening call, often within ten minutes, since anyone who has coached for a few years has done at least one engagement where no one with budget authority would back them in front of a director, and they spent a year running meetings with “coach” in their email signature.
Contract, Contract-to-Hire, or Full-Time
The engagement model should follow the shape of the problem, and the headcount plan is a bad guide to that shape, because finance approves seats on an annual cycle while most coaching mandates have a natural end somewhere between month four and month nine.
| Model | Fits When | Typical Length | Watch Out For |
|---|---|---|---|
| Contract | A defined mandate with an end, such as a first PI planning cycle, a maturity assessment, or a reorg rollout | 4 to 9 months | No handoff plan, so the practices leave with the coach |
| Contract-to-hire | You suspect the role is permanent but aren’t sure the culture will accept a coach | 3 to 6 months, then convert | Strong enterprise coaches often decline C2H outright |
| Full-time | You’re building an internal coaching practice or the scope spans several business units for years | Open-ended | Coaches who stay three years can turn into process owners and stop coaching |
Cost has its own page, our agile coach salary guide, so only the anchor numbers go here. Coaches placed through contract staffing bill roughly $85 to $145 an hour depending on scope, and the closest observed figure KORE1 publishes, from the October 2026 Contract Rate Index, puts our IT project manager, program manager, and scrum master contract placements at a $116 median (n=21, mostly Southern California), which is about where a program-level coach lands and well below where an enterprise transformation lead does.
Where the Good Ones Actually Come From
Very few strong agile coaches come off job boards, since the ones worth hiring are usually eight months into somebody else’s engagement, reachable through a referral or a direct note, and inclined to read your sponsor’s name and your four sentences before they look at the comp line.
Most of our agile coach placements who were still in the seat a year later came from one of three backgrounds, the first and largest being former engineering managers who had run two or three development teams, got curious about why one shipped and the other didn’t, and drifted sideways into coaching, which is why developers tend to trust them within a week. Release train engineers from SAFe trains at banks and insurers, looking for more scope than a single train gives them, are the second group. The third and smallest group trained as coaches first, through an ICF credential or the full ICAgile coaching track, and came over from organizational development, so they are the strongest of the three with a CFO in the room and the most likely to get lost when two tech leads start arguing about trunk-based development versus long-lived feature branches.
Certifications such as ICP-ACC, SAFe SPC, CSM, PSM, and Kanban University’s KMP show that someone finished a course, and enterprise procurement teams usually require one, which makes them a reasonable filter and a poor decision rule. An SPC tells you the person is licensed to teach SAFe. It does not tell you whether they can persuade a skeptical VP of engineering in Irvine to stop demanding fixed dates on epics nobody has broken down yet, and that is much closer to the actual job.
The Interview Loop That Actually Tests Coaching
Our loop has five stages, and the three in the middle are the ones clients most want to cut, usually because they take calendar time from a sponsor and a team who are already overbooked, which is a fair objection until the wrong hire costs a quarter.
| Stage | Time | What You’re Watching For |
|---|---|---|
| 1. Screening call about a failed transformation | 30 min | A team count, a month, and the executive role that pulled support, not “leadership buy-in” |
| 2. Live facilitation of a real retrospective | 45 min | What they do when someone says retros are a waste of time |
| 3. Working session with the executive sponsor | 30 min | Whether they tell the sponsor something the sponsor didn’t want to hear |
| 4. Coaching one of your scrum masters | 30 min | Questions versus prescriptions |
| 5. References from both directions | 2 calls | One executive they coached and one team member who started out skeptical |
The screening call is the cheapest filter you have, and the question I’d ask first is about the transformation that went badly, because a coach who has done this for six or seven years and can’t name one, with the team count and the month the CFO froze the budget, either hasn’t done the work at the level the resume claims or isn’t going to be honest with your sponsor when things slip.
Stage two is the one clients push back on hardest, since it feels like making a senior person audition. Run it anyway. A regional insurance carrier outside Dallas ran it with two finalists last spring, both strong on paper. The first had a SAFe SPC and twelve years of experience, and when the QA lead told him the retro was pointless, he spent ten minutes explaining to her why retrospectives matter. The second had a CSM and an ICF PCC. She asked the QA lead to pick the topic for the next fifteen minutes, the QA lead picked the flaky regression suite in their Azure DevOps pipeline that had been failing one build in five since March, and the team had its first useful retro in months. They hired her, and I’d bet the first candidate’s resume beats hers in nine screening rounds out of ten.
Stage four borrows from our scrum master interview questions, turned around so the candidate is the one coaching. Your scrum master brings a problem they’re actually stuck on this sprint, maybe a product owner who rewrites priorities every Thursday, and you sit in the corner and count how many questions the candidate asks before offering an opinion. Two or three is good. Zero is a consultant. The full question bank we hand panels, sorted by coaching stance, is in our agile coach interview question guide.
Red Flags Worth Ending an Interview Over
A framework answer to every question is the first warning, because a candidate for whom SAFe, LeSS, or the squads-and-tribes model from the old Spotify slides has fixed every problem they’ve ever met has usually worked inside only one kind of company.
Velocity offered as the scoreboard is the second. Velocity is a planning aid that belongs to the team, and a coach who reports it upward as evidence of improvement will have teams inflating story points within two quarters, a change that is easy to miss because the chart looks better every sprint. The principles behind the Agile Manifesto named working software as the primary measure of progress in 2001, and the candidates worth hiring can say, without much prompting, what they would measure instead and why a customer would notice it.
The third is the absence of any failure story, since everyone with five years in this work has a transformation that fell apart, and a candidate who hides theirs in an interview will hide the next one from your sponsor.
The last only surfaces when the question is put directly. How many former clients still run the practices without you? Some candidates have a number, and some go quiet and then talk about “sustainability,” which usually means every engagement ended when the budget did.
The First 90 Days, and How You’ll Know It’s Working
The first 30 days should be mostly listening, which means sitting in ceremonies, holding one-on-ones with team leads and product owners, and finding the meeting where priorities actually get set, a meeting that is rarely on the agile calendar and, at one medical device client, turned out to be a 7:30 a.m. Tuesday call between the VP of product and two directors that the coach only learned about in week three. A coach who arrives on day one with a roadmap deck wrote it for somebody else’s company.
Around day 60 you should have a short written assessment, three or four pages, plus two or three experiments with an owner and a date on each.
Day 90 is for outcomes the teams already feel, such as lead time from commitment to production, the share of planned increment objectives that actually landed, and the number of cross-team dependencies discovered in the last week of an increment rather than the first. If you already pull DORA metrics through LinearB or GitLab’s value stream analytics, use them, and fix the baseline before the coach starts so nobody relitigates it in month three. The scrum masters will usually know first, and they will tell you if you ask privately.
The test I like best is one most clients haven’t tried, which is to schedule a week in month three when the coach is deliberately away from Slack and the standups and then watch which practices keep running and which quietly stop by Wednesday.
What Leaders Ask Us Before Opening the Req
Realistically, how long does an agile coach search take?
About three weeks for a program-level coach, measured from a clear problem statement to a hire, and six to nine weeks for an enterprise transformation lead.
KORE1 averages 17 days to fill across our IT roles. Agile coach searches run a little longer because the scope conversation takes about a week by itself, and the transformation-lead pool is small enough that the right person is usually mid-engagement and needs a notice period.
Can we promote our best scrum master into the coach role?
Sometimes, and it’s worth trying at program level. It fails more often at enterprise level, where the job is mostly persuading executives who outrank the coach.
If you go internal, give them an outside mentor for the first six months and a sponsor who’ll defend them publicly the first time a director pushes back. Without both, you’ll lose a good scrum master and gain a frustrated coach.
Which certification should be on the resume?
Wrong question, slightly. Certification predicts whether a candidate passes enterprise screening, not whether they can coach, so check for one only if your procurement team requires it.
When a client insists, ICP-ACC and SAFe SPC are the two we see most on successful placements. An ICF coaching credential is rarer and, in our experience, a better signal for executive-facing roles.
$85 to $145 an hour sounds like a lot. Is a full-time hire cheaper?
$135 an hour across a full year works out to about $281,000, so yes, if the engagement truly runs twelve months at full time. Most don’t.
Coaching mandates usually run five to seven months of heavy work and then taper. Price the real shape of the work. If the role clearly outlives any single mandate, direct hire wins and the math isn’t close.
Who should the coach report to?
The executive sponsor, or someone one level below them who sits outside the teams being coached.
Reporting into a PMO tends to turn coaches into process auditors. Reporting into one engineering manager makes them that manager’s assistant. Neither is fatal. Both are slower.
How do we end a contract engagement without losing the progress?
Name the internal owners in month one and have the coach spend the last third of the contract coaching them to run everything.
If nobody internal can run the cadence by the end date, extend by a month or two rather than letting it lapse. Practices that stop the week the coach leaves usually don’t restart.
Start With the Sponsor
If you take one step from this guide, take the first one. Write the four-sentence problem statement and put a sponsor’s name in it. Everything downstream, from the engagement model to the interview loop to the 90-day measures, gets easier once that’s on paper.
We’ve placed agile and delivery talent 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 at twelve months. That retention number is the one we care about here, because a coach who leaves in month seven takes most of the change with them. If you’d like a second set of eyes on your problem statement before it becomes a job description, talk to a recruiter who has run these searches recently. We’ll tell you if you need a scrum master instead.
