The agile coach job post

Some job posts tell you a team is growing. A few tell you the way the company works is about to change. An enterprise agile coach is one of those.

Nobody hires an agile coach to keep delivery the same. The role exists only when someone senior decided the current way is too slow, too expensive or too unpredictable.

Why these roles turn into spend

Transformation roles are different from delivery roles. A Java developer post means more Java gets written. An enterprise agile coach, a head of platform engineering, a director of developer experience or a VP of delivery excellence means someone is rewriting how the whole engineering org operates.

That kind of change has a sponsor, a budget and a deadline. And it almost never waits for the hire. The search takes three to six months. The program was approved before the post went up. Somebody is already on the hook for showing progress.

So the sponsor brings in a team to start. Coaches, platform engineers, consultants who've stood up an internal developer platform before. The hire, when they arrive, inherits that work and often keeps the firm that started it.

The difference between a backfill and a new program is the whole game here. A transformation role is almost never a backfill.

Where these posts live

The company's careers page and LinkedIn jobs. Search the titles directly. Enterprise agile coach, agile transformation lead, head of platform engineering, director of developer experience, developer productivity lead, delivery excellence, engineering effectiveness, ways of working lead.

Then read the post itself. The tech stack is in there, which I covered in the tech stack hiding in plain sight in job posts. So is the reporting line, the scope and, often, the reason.

Look for clusters. One agile coach post can be a team-level hire. Three coaching posts plus a platform lead plus a transformation office role in the same month is a program. What a cluster of engineering job posts tells you covers how to read that pattern.

Reading the post

Strong language names a program. "Lead our enterprise transformation." "Build our internal developer platform from the ground up." "Stand up a delivery excellence function." Words like build, establish and first mean nothing exists yet.

Strong posts report high. A head of platform engineering reporting to the CTO is a different signal than one reporting to a director of infrastructure.

Strong posts name a scale. "Coach 40 teams across three business units" is a program. "Support two scrum teams" is a team lead with a fancier title.

Noise looks like evergreen posts open for a year, recruiter reposts with no company named, and scrum master roles at the team level. Those are real jobs. They're not transformation.

Who's carrying it

The CTO or VP of engineering usually sponsors the change. They told the CEO delivery would get faster, and now they're accountable for proving it. The CIO feels it if the program touches enterprise systems. Sometimes a CFO is behind it, when the push is about engineering cost per feature rather than speed.

Then there's the hiring manager for the role. That's the person carrying the program until the hire lands, often on top of their real job.

Say Brightwater Insurance posts for an enterprise agile coach, a head of platform engineering and two developer experience engineers in the same three weeks. Here's an opener to the VP of engineering, Priya Nandakumar.

Brightwater posted for an agile coach and a platform engineering lead in the same month. That reads like a delivery change with your name on it and the senior seats still empty. My guess is the program has a date the hires won't make, and the platform work can't wait for a head of platform to start. Is that close, or is the pressure coming from somewhere else?

The hook is the posts. The trigger is her name on the program. The hypothesis is the gap between the deadline and the hiring timeline. The exit is one question she can answer in a sentence.

The window between post and hire

The window opens the day the posts go up and closes once the hire starts and settles in. That's usually three to six months. Reach out in the first few weeks. After the hire arrives, they'll want to make their own choices, and you're selling to a new leader instead of a stretched sponsor.

These posts stack well with a new CTO, a cost program in an earnings release, or an announced cloud or ERP program. A new CTO who posts for a platform lead in their first quarter is telling you exactly what they plan to change.

A transformation hire is a program with an empty chair. Somebody is running it from a second desk right now. Find them and name the gap.