Hire Agile Coaches

Agile Coach specialist or generalist - which should you hire?

The honest answer depends on the half-life of your agile coach surface area. If you expect to keep investing in Agile Coaching and Scrum work over the next 18-24 months, a specialist agile coach will out-deliver a generalist on day-30 throughput and stakeholder confidence.

If your team is under ten people, or agile coach responsibilities are spread across two or three roles already, hire a strong generalist who has shipped this work in anger at least twice. The cross-disciplinary pattern recognition will pay for itself the first time priorities collide.

On Haystack we surface both - filtered by whether the candidate self-identifies as a agile coach specialist and verified against their last two roles. Expect to pay around £68k–£90k for a mid-level UK hire, scaling toward £95k–£135k for senior.

What strong agile coaches actually bring

A great agile coach is not the one with the longest CV - it is the one who has owned a hard Agile Coaching call and changed how they work because of how it landed. Across the product & delivery hires we have placed in 2025-2026, the same patterns keep showing up.

• An opinion on what NOT to do with Agile Coaching, backed by an example where adding it would have hurt the team.
• Agile Coachs who pair Scrum depth with cross-functional fluency - they bring product, design and data into their decisions, not just engineering.
• A written 30/60/90 plan in week one, anchored to Agile Coaching delivery milestones rather than ramp-up vanity metrics.
• Versioned, observable agile coach work - measurable outputs, structured logs of decisions, and a clear rollback path on every change.

Red flags when interviewing agile coaches

Every discipline has its own pattern of plausible-sounding answers that fall apart in production. For agile coaches, these are the patterns that most often correlate with a six-month regret hire on the employer side.

• Defines "senior agile coach" purely by years of experience, not by the scope of decisions they own.
• Lists Scrum on the CV but cannot describe a single trade-off they hit in production - all framework, no friction.
• Treats the agile coach role as a job title rather than a problem to solve - no opinion on what they would change about how the discipline is typically practised.
• Only ever worked on greenfield agile coach projects - inheriting a messy, half-built system is a different muscle.

A sample take-home for agile coach candidates

When teams ask us how to evaluate a agile coach beyond a CV and a chat, we recommend a 90-minute paid take-home that mirrors real work, not a trivia quiz. The brief below is one we have refined with employers hiring across product & delivery teams.

Give the candidate a small, intentionally imperfect artefact tied to "coach engineering and product leadership". Their task is to add a second capability - tied to "design team topologies and operating cadences" - while keeping existing behaviour intact. Then grade in three parts.

• Correctness: the new work satisfies the brief and at least one edge case the candidate flags themselves.
• Judgement: did they refactor, wrap or work around the existing imperfection? Any of the three is fine - we are listening for the reasoning, not the verdict.
• Communication: a short written note explaining what they would do differently with another week, what they noticed about Agile Coaching, Scrum and Kanban, plus working exposure to SAFe, Org Design and Coaching, and the assumptions they made along the way.

What to expect in the first 30 days from a Haystack agile coach hire

By week one, the new agile coach should have shipped a small, low-risk artefact to production or a stakeholder - a docs fix, a small process change, a first review on someone else's work. The goal is to validate the loop, not to ship anything heroic.

By week two, the agile coach is shadowing the active workstreams, attending standups in observe-mode, and asking pointed questions about why specific decisions were made. If they are not asking those questions, the hire is going to plateau.

By day 30, they own one cleanly-scoped slice of the agile coach surface area, have published a public ramp-up doc, and are the named point of contact for stakeholders inside that slice. Every Haystack employer gets a structured onboarding template, so you are not reinventing the playbook each hire.