The Agile Coach Is Dead. Long Live the... What, Exactly?

If you held an Agile Coach title in 2023, there is a non-trivial chance you do not hold it today.

Capital One started the cascade in January 2023, eliminating roughly 1,100 positions across its entire Agile job family. Agile Delivery Leads, Agile Portfolio Leads, coaches, and the rest of the support layer were absorbed back into engineering and product management on the theory that the transformation had matured past the point of needing dedicated stewards. Three years later, the cascade has not stopped. It has accelerated.

Atlassian, in March 2026, cut 1,600 roles, about 10 percent of its workforce. The composition matters. Reporting from Tech-Insider grouped the cuts into content creation, customer support, quality assurance, and project management, with roughly 800 net new roles created in AI engineering, machine learning operations, and AI safety. Across the broader market, Layoffs.fyi tracked nearly 246,000 tech jobs eliminated in 2025 and another 128,000 through mid-May 2026. The numbers themselves are not new. What is new is what is getting cut and what is getting hired in its place.

Job postings for Agile Coach and Senior Scrum Master are down sharply year over year. The titles that are appearing in their place include Team Coach, Enterprise Coach, Delivery Lead, Engineering Manager, and a handful of hybrid roles that read like someone bolted three job descriptions together. The framing is shifting. The question worth asking is what actually died, and what is going to outlive the role.

What Actually Died

The standalone change-agent role died.

The version of the Agile Coach who sat outside the delivery org, ran trainings, facilitated workshops, and answered to a transformation lead instead of to a delivery org with its own budget to defend is the version that is gone. That role was always politically fragile. It depended on a sponsor at the executive level who believed in the transformation enough to fund a layer of people whose output was hard to measure on a quarterly basis. When sponsors changed, budgets tightened, or the transformation hit its expected maturity curve, the role had no organic place to land.

Capital One said the quiet part out loud when they made the cuts. Agile delivery, in their framing, was no longer a separate discipline that needed dedicated practitioners. It was a way of working that engineering and product should own directly. The argument is not wrong on its face. It just leaves a lot of practical questions unanswered about who handles the work the coaches were actually doing.

What did not die is the underlying need for someone to handle facilitation, dependency management, team health, and the slow grinding work of getting cross-functional groups to operate well together. That work still exists. It still has to happen. The question is whether it gets done by someone with a job title that names it, or by an engineering manager who picks it up on top of their day job.

The Macro Version of the PM Career Ceiling

I wrote earlier about the way the market typecasts experienced PMs into Scrum Master and RTE roles regardless of whether they want to be there. That was a personal account of a structural problem. This is the same problem at scale, viewed from the other side.

When companies eliminate the coach role, they do not eliminate the demand for coaching skills. They redistribute it. Some of it lands on engineering managers who now have to run retros and unblock dependencies on top of their existing responsibilities. Some of it lands on product owners who suddenly own backlog health and team facilitation. Some of it lands on Senior Scrum Masters who get rebranded as Team Coaches and asked to take on twice the scope for the same compensation.

The PMs and coaches who get caught in this redistribution face the same career problem from a different angle. The market keeps offering them roles that are titled one thing and scoped as another. A coach gets offered a Delivery Lead position that is actually engineering management with a different name. A PM gets offered a Senior Scrum Master role with PM responsibilities buried in the third paragraph of the job description. The pattern is the same. The ceiling is the same. Only the door it shows up at has changed.

RTEs: Coach-Adjacent With Specificity

There is a reasonable question about whether the Release Train Engineer role is the next domino. I will not pretend the role is immune, because nothing is immune. But the RTE role has structural protections that the standalone coach role did not have.

An RTE owns specific events with specific deliverables. PI Planning has a defined cadence, a defined output, and a defined set of stakeholders who notice immediately when it does not happen. ART Sync, Coach Sync, Scrum of Scrums, and the Inspect and Adapt workshop are not optional ceremonies that the org can quietly stop running. The dependency board is a physical artifact that someone has to maintain or features start missing their target PIs. The work is tied to operational rhythm in a way that pure coaching work is not.

That specificity is what gives the role staying power inside SAFe organizations that are still running ARTs. It is also why RTEs who want career mobility outside that context have to think hard about how their skills translate. The event facilitation is portable. The dependency mapping is portable. The lean budget collaboration with Business Owners is portable. The SAFe-specific vocabulary, less so.

I covered what RTEs actually do all day in an earlier post. The short version is that the role is more operational than coaching-adjacent observers tend to assume, and the operational pieces are what will likely keep the role around even as the broader coaching layer thins out.

Survivors Are the Ones Closest to the Money

The pattern across the coaches I know who still have jobs is consistent. They are no longer titled Agile Coach. They are titled Delivery Lead, Engineering Manager, Product Operations Lead, or some variant that puts them inside the delivery org with budget responsibility.

The repositioning is not cosmetic. It changes how the work gets done. A Delivery Lead who owns a team’s roadmap and reports into engineering has different leverage than a coach who has to influence without authority. The decision rights are different. The escalation paths are different. The measurement is different. Output gets tracked against delivered features and reduced cycle time instead of team maturity assessments and engagement scores.

This is the part of the transition that practitioners coming out of pure coaching roles tend to underestimate. The skill set transfers. The disposition does not always transfer. A coach who was effective because they had no skin in the delivery game now has skin in the delivery game and has to make tradeoffs that they previously got to facilitate from the outside. Some people thrive in the new shape. Some people find that the part of the job they loved was the part that just got removed.

PMI’s 2025 Pulse of the Profession landed on business acumen as the differentiator for PMs going forward. The same finding applies to coaches making this transition. The ones who survive are the ones who understand the business decisions their teams are working inside, not just the practices their teams are using.

A Practical Transition Framework

For anyone in or near a coach role right now, the framework I would offer is this:

• First, audit your current responsibilities and separate them into the work that is tied to a specific operational outcome and the work that is tied to a transformation goal. The operational work travels with you. The transformation work travels only if there is another transformation to join.

• Second, identify the closest adjacent role inside your current org that owns its own budget. Delivery Lead, Engineering Manager, Product Operations, Program Manager with budget accountability. The goal is not to escape coaching. The goal is to embed the coaching work inside a role that has its own justification.

• Third, build the business-acumen vocabulary you will need to operate inside that role. Capacity planning in dollars, not just story points. Risk in terms of cost of delay, not just team velocity. Roadmap tradeoffs in terms of opportunity cost, not just sequencing. The technical work is the same work. The framing is different.

• Fourth, treat the next 18 months as a window. The pattern Atlassian set in March is going to repeat. The companies cutting coaching layers now are signaling what they intend to invest in instead. AI tooling, AI engineering, and product operations are the categories absorbing the freed-up budget. The coaches who reposition before the cut are in a better seat than the coaches who reposition after.

Final Thought

The Agile Coach role had a job to do. In a lot of organizations, that job got done. The practices stuck. The teams matured. The transformation hit the maturity curve the executives had been promised back in 2017 and the budget that funded the coaching layer got reabsorbed into the parts of the org that produce features and revenue. That is not a failure of Agile. It is the predictable end of one phase of an organizational change.

The coaches who treated the role as a permanent identity are having the hardest time right now. The coaches who treated it as a phase of work, with a beginning and an end, are mostly fine. They are doing the work somewhere else, under a different title, with better proximity to the decisions that actually shape what gets built.

The question in the title is not rhetorical. The thing that replaces the Agile Coach role is not a new title. It is a redistribution of the work into roles that already existed and were already accountable for outcomes the coach was only ever influencing from outside. Long live the engineering manager who can run a retro. Long live the delivery lead who can read a dependency map. Long live the PM who can hold a backlog conversation without needing a facilitator in the room. The work is still there. The labels are catching up to where the work always lived.

• Jeff