Why pre-screen agile coaches before the interview
The visible output of a transformation is new meetings, a board and different vocabulary. Whether anything got better is a separate question that far fewer coaches can answer with evidence. Coaches worth hiring measure something before they start and can name a team where their approach did not work. A short screen asks for that team, which separates coaching from framework installation.
What actually matters when screening Agile Coach candidates
- 01
Subject and technical command
Check command of Scrum, Kanban and scaling frameworks (SAFe, LeSS): WIP limits, flow metrics, story slicing, Definition of Done, plus certifications like CSP-SC, PSM III or ICP-ACC.
- 02
How they actually teach
Probe their actual coaching stance: how they run a liberating structures workshop, coach a Product Owner on backlog refinement, or move a team from prescriptive training to self-organisation.
- 03
Group management and safeguarding
Assess facilitation of hard rooms: heated retrospectives, a dominant tech lead, a manager sitting in on standups, and how they protect psychological safety and surface conflict.
- 04
Progress and communication
Look for evidence of change: escaped defects, lead time, predictability or engagement scores before and after, plus how they reported progress to sponsors and leadership.
Pre-screening questions to ask Agile Coach candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Teams that improved
3 questions01Can you discuss the most successful team or project you have coached?
Listen forA team with a measured improvement in delivery, quality or predictability, not just a smoother process.
Success described as adopting a framework, or improvement claimed with no measurement behind it.
02What is your experience training or mentoring teams in these practices?
Listen forSustained coaching over months, with teams left able to continue without them present.
Engagement limited to training sessions, or teams that reverted as soon as the coach left.
03Can you describe a time when you helped a team solve a genuinely complex problem?
Listen forThe team's own capability improved rather than the coach solving it for them.
The coach as the person who fixed it, or the team no better able to handle the next problem.
Coaching not process
3 questions04What is your approach to coaching, and why do you work that way?
Listen forA coaching stance based on questions and observation rather than prescribing a standard process.
A single framework applied to every team, or coaching described as implementing a methodology.
05How do you adjust your approach for teams new to these ways of working?
Listen forApproach adapted to team maturity and context, starting from the problem the team actually has.
The same starting point regardless of team, or maturity models applied mechanically.
06How do you help teams understand the roles within their way of working?
Listen forRoles explained by the responsibility they carry, with an honest view of where they add nothing.
Roles taught by definition, or roles insisted on where the team does not need them.
Resistance handled
3 questions07What do you do when a team is resistant to changing how they work?
Listen forResistance treated as information, with the underlying concern investigated before any push.
Resistance framed as people not understanding, or overcome by escalating to management.
08How do you handle a lack of management support during a change?
Listen forManagers engaged on their own problems, with an honest position on when a change should not proceed.
Transformations pushed without sponsorship, or management resistance ignored rather than addressed.
09How do you approach cultural change when it is needed for a way of working to stick?
Listen forChanges to what leaders actually reward, with an understanding that structure often blocks the change.
Culture change described as values and posters, or organisational structure treated as fixed.
Improvement measured
3 questions10How do you measure a team's performance and improvement?
Listen forOutcome measures such as lead time, quality or predictability, with a baseline taken before starting.
Velocity used as a performance measure, or no baseline taken before the engagement began.
11What measures have you used to gauge progress on a team's work?
Listen forFlow measures used for the team's own decisions, with an awareness of how each can be gamed.
Measures used to compare teams, or velocity reported upward as a productivity number.
12How do you help teams balance delivery against technical quality?
Listen forQuality treated as a delivery constraint, with technical debt made visible to those setting priorities.
Quality treated as an engineering concern only, or debt never surfaced to decision-makers.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Subject and technical command
30%5Explains flow metrics such as cycle time and throughput, names framework trade-offs, and cites where they deliberately broke a framework rule.
How they actually teach
30%5Describes a concrete coaching arc for a named team, using questions and experiments rather than mandates, with visible behaviour change over sprints.
Group management and safeguarding
25%5Recounts a specific tense retro or dysfunctional team, names the facilitation technique used, and describes how the conflict was made discussable.
Progress and communication
15%5Cites baseline and post-engagement numbers for named teams, and shows how they handed off ownership rather than becoming permanently required.
A transformation produces new meetings; whether anything improved is a separate question. A one-way video screen asks for the evidence.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish teams that improved, test their coaching approach, and hear how they handled resistance and measurement.
How much should certifications count?
Very little. Entry-level agile certifications require a two-day course, and the field is full of them. Weight teams coached and outcomes measured far more heavily than any certificate.
Evaluating answers
What is the strongest signal when screening this role?
A team where it did not work. Coaches with real experience have one and can explain why their approach was wrong for that context. Anyone with only successes is describing a marketing case study.
How do I judge whether they change behaviour?
Ask what a team does differently now. Real answers describe behaviour, not ceremonies. Anyone whose answer is a list of meetings has installed a process rather than coached anyone.
























