Agile Coach Resume: Complete 2026 Guide

From the author

Emmanuel Gendre, ex-Google recruiter

My experience with Agile Coach resumes

Twelve years in tech recruiting, including a long stretch at Google, and the Agile Coach resume has a recognizable failure mode: it reads as a Senior Scrum Master with extra certifications listed. Directors of Engineering and Heads of Transformation spot it instantly. What they want is the transformation outcomes: the 6-ART program you coached at a Fortune 500 healthtech that moved the agile-maturity index from 2.1 to 3.8, the CTO you coached through the platform-vs-features bet, the Lean Portfolio you stood up that redirected $14M of WSJF-prioritized investment, the Scrum Master cohort you certified and graduated from your dojo. None of that lands when the resume reads as "coached teams, ran trainings, facilitated retros."

What hiring teams actually want in 2026 is the transformation outcome story behind the coaching engagements. An Agile Coach resume reading as "coached agile teams, ran transformations, taught Scrum" without a maturity-index trend, an executive sponsor you partnered with, or a multi-train scope gets dropped before any conversation happens.

That gap is exactly what this guide closes. Five sections decide whether the Agile Coach screen even starts, and the rest of this guide goes through them one at a time. The single goal: interviews back on the calendar, regardless of how soft the market feels right now.

Want the rewrite done for you? My Tech Resume Writing Service rebuilds the page from a blank file. Already have a draft and just want trained recruiter eyes on it? Drop it into the free review; every one passes through me directly and the notes come back from me.

Time to get your Agile Coach resume opening calls instead of getting filtered. Let's start.

What the Agile Coach resume guide covers

How I rewrite an Agile Coach resume

A Agile Coach resume crosses my desk regularly, through both the resume writing service and the free reviews. The pattern holds: roughly nine-tenths of the page contributes nothing, and the decision rides on five sections only. Going solo? Concentrate effort on those five, leave everything else alone.

Each step has a self-contained section below. Move through them sequentially, apply the edits as you go, and the resume you end up with reads as a different document entirely. The structure:

Want the method behind it? Here's how I rewrite resumes, laid out in full.

Step 1 · Agile Coach Resume Format

The format to use for an
Agile Coach resume

Knock this one out first: the ATS has to be able to ingest the page.

Most online advice on layouts is noise. The work boils down to one thing: a text parser has to pick up your content and structure exactly as you wrote them, with nothing dropped along the way.

Keywords matter for filtering further down the funnel (that's Technical Skills, Step 5), but parsing failures are what eliminate 95% of resumes before anyone reads a word.

Three short rules cover most of it:

Use a text editor (Word, Google Docs)

An ATS pulls text and nothing else. If the file isn't actually text on the page, the parser comes back empty-handed. Lay the resume out in Canva or Illustrator and every line becomes a flat raster image, so the automation frameworks and CI tools you spent hours listing simply vanish. From the parser's view, you submitted a blank document.

Single column, plain layout

Pull every column, sidebar, table, and image out of the layout. ATS engines in 2026 still chew them up, and this is the single most common parsing failure I catch in reviews (about three drafts in ten land here). Switch to a clean single-column layout and most of the parsing damage corrects itself.

Simple section titles

Use Profile Summary, Technical Skills, Work Experience, Education. Not "Bugs I've Caught", not "What I Bring to Quality". ATS and recruiters both look for standard headings, and a clever label just drops you out of the bucket. Avoid fuzzy ones too: "Core Competencies" lives inside Profile Summary or Technical Skills; "Career Highlights" lives inside Profile Summary or Work Experience.

Unsure how your current PDF holds up under parsing? Run it through the ATS resume checker and look at the extracted output side by side with the page. When the extracted version comes out broken, the bullets aren't the problem, the layout is, and layout is most of how an ATS scores you.

Want a clean slate that parses correctly out of the box? Grab the Agile Coach resume template, designed for exactly that.

Step 2 · Agile Coach Profile Summary

Writing a profile summary
for an Agile Coach

Whatever you've read elsewhere, no resume should skip the Profile Summary. Juniors included.

If yours is missing, or it's there but weak, fixing it is the biggest single win on the table today.

All the mechanics sit inside how recruiters screen resumes. Quick version: a recruiter runs your resume twice. Pass one prunes the pile to anyone who looks credible for the role. Pass two distills that group into the actual shortlist for interviews.

Pass one is the punishing one: a recruiter cycles through file after file at a sprint, spending only seconds on each. That is where the well-known "10-second screen" stat comes from.

The Profile Summary is your only opportunity to land every cue a recruiter looks for inside that tight window. Stick it and the rest of the page gets opened; whiff it and nothing else carries weight.

Every bullet has a defined role. Below is the playbook I use when rewriting an Agile Coach profile summary: what each line is on the hook for, plus a worked example tied to a real product.

Target job title, overall experience & product scope

Bullet 1 sets the marker: the role you're aiming at, your seniority, plus the engagement scope and company size (single-ART vs multi-train vs enterprise; engineer count, ART count, Fortune 500 / Series C). Add a regulated industry (healthtech, fintech, e-commerce) and a recognized employer if either lifts weight. Read this sentence as the page's top headline: a Director clocks it before anything else, and on rushed days it is sometimes the only line they reach.

Info for recruiters Target job title Years of experience Engagement scope & company size Domain & employer

Example Senior Agile Coach 12 years 6 ARTs, 200 engineers, Fortune 500 enterprise SAFe SPC + ICF PCC, healthtech

Domain expertise

Bullet 2 covers your domain expertise: the slots that make up the Agile Coach role profile (laid out in Step 3, Agile Coach Work Experience). For this role those slots are org-wide agile strategy and transformation, executive coaching of CTOs and VPs, multi-train coaching, agile maturity assessment and roadmapping, and coaching dojos and capability building. A transformation hiring director walks that scorecard line by line and ticks off your entries. Treat this bullet as your own scorecard and leave no row empty.

Info for recruiters Org-wide strategy & transformation Executive coaching (CTO, VP) Multi-train coaching Maturity assessment & roadmapping Coaching dojos & capability building

Example 3-year transformation roadmap for 200 engineers Coached 4 VPs and the CTO on Lean Portfolio 6 ARTs aligned on shared cadence and metrics Maturity index 2.1 → 3.8 across 6 ARTs Certified 18 Scrum Masters through quarterly dojos

Your tech stack

Bullet 3 names your daily toolset: the agile framework, the facilitation tool, the delivery system, the certification, and the metrics dashboard. The full inventory lands further down under "Technical Skills" (covered in Step 5, Agile Coach Technical Skills); up here you only call out the daily drivers. For an Agile Coach that means: framework, facilitation, delivery, certifications, and metrics.

Info for recruiters Transformation framework Executive coaching model Multi-train facilitation Lean Portfolio Capability building

Example Agile Fluency, SAFe Implementation Roadmap ICF PCC, GROW, Marshall Goldsmith Miro / Mural / Liberating Structures Lean Portfolio canvas, WSJF, OKR cascade Coaching dojos, CoPs, ICAgile ICP-LEA

Collaboration

Bullet 4 covers your cross-functional partnership. A Scrum Master serves between the Product Owner (who owns backlog priority), Engineering and QA (who build and ship), the Engineering Manager (who owns people-leadership and budget), peer Agile Coachs (who share the train and Scrum of Scrums), the Release Train Engineer (at SAFe scale), and business stakeholders (who need predictability from the team). A hiring manager checks whether you carry those relationships cleanly, so name the partner roles and the touchpoints you owned.

Info for recruiters Executive sponsors Transformation roadmap ownership Lean Portfolio facilitation

Example Product Owner Engineering & QA Engineering Manager Peer Agile Coachs / RTE Business Stakeholders

Leadership

Bullet 5 surfaces your facilitation leadership. Leadership for an Agile Coach shows up in the standards you set: the Liberating Structures retro format your peers reuse, the impediment-tracking flywheel you built, the transformation engagement you led, the coaching dojo you facilitated for junior Agile Coachs, and the agile-maturity assessment you authored for engineering leadership.

Info for recruiters Facilitation patterns you authored Coaching dojos you run Junior Agile Coachs you mentor

Example Liberating Structures retro library author Quarterly coaching dojo facilitator Mentored 4 Agile Coachs, 2 promoted to Senior

Agile Coach Profile Summary Example

Senior, 6 ARTs across a 200-engineer Fortune 500 healthtech (SAFe 6.0 enterprise transformation)

Profile Summary

Senior Agile Coach with 9 years serving a 3-squad Agile Release Train of 24 engineers and 3 POs at a B2B SaaS healthtech under SAFe 6.0, biweekly PI cadence.
Strong on Servant-Leadership Facilitation, Agile Ceremonies & Cadence Mastery, Team Health & Engagement, Impediment Removal & Flow Optimization, and Metrics & Continuous Improvement.
Day-to-day across Framework (SAFe 6.0, Scrum, Kanban, Scrum@Scale), Facilitation (Miro, Mural, Parabol, Retrium), Delivery (Jira, Azure DevOps, Confluence), Certifications (CSM, PSM II, A-CSM, SAFe SPC), and Metrics (EazyBI, ActionableAgile, LinearB).
Cross-functional partner across Product Owners, Engineering and QA, Engineering Managers, peer Agile Coachs and RTE, and business stakeholders, owning the impediment-removal flywheel that lifted PI predictability from 60% to 92% and cut lead time from 14 days to 4 over 4 PIs.
Authored the Liberating Structures retro library reused across the train, facilitates the quarterly coaching dojo, mentored 4 Agile Coachs (2 promoted to Senior), and authored the agile-maturity assessment for engineering leadership.

Want to go deeper on this one? I cover it end to end in my guide on how to write a killer profile summary.

Want a recruiter's read on your Agile Coach resume?

Weeks of applying and no interviews, no feedback.
No company owes you the reason, so you're stuck guessing what's off in the draft. Keep guessing, or hand it to someone who screened thousands of Agile Coach resumes at Google.

Let me pull it apart for you.

I'll run a simulated recruiter screen on your Agile Coach resume and send back a tight list of what to fix. Free, within 12 hours.

Want to read more first? See how the resume review works →

Step 3 · Agile Coach Work Experience

Work experience on an
Agile Coach resume

Now back into round two. This is the section that determines whether you get the call at all, and a recruiter actually slows down here. Even so, 95% of the decision still comes from your most recent role.

The logic is simple. Your current job is the truest signal of how you operate today, what you actually run hands-on, and where your seniority genuinely sits. To turn the screen toward an interview, that role has to cover every line in the full Agile Coach role profile, one bullet per area you already named in the Profile Summary's Domain Expertise block.

Org-Wide Agile Strategy & Transformation

You lead an agile transformation across the whole org. A transformation without a plan stalls at the team level, so hiring managers want an operating model you rolled out, not a framework you named. Talk about how you used a multi-year roadmap and operating-model design, against the Agile Fluency Model, to move the org maturity index and ship transformation milestones.

Techniques Multi-year transformation roadmap Operating-model design Agile Fluency Model (Shore / Larsen) SAFe Implementation Roadmap

Tools Confluence / Notion transformation wikis Miro / FigJam roadmap canvases Pitch decks for executive sponsors

Metrics Maturity index trend Transformation milestones shipped Executive-sponsor NPS

Executive Coaching (CTO, VPs, Directors)

You coach CTOs and VPs through the calls they can't take back. Coaching executives is a different craft than coaching a team, so hiring managers want engagements you held, with real trust. Show them how you used executive 1:1s and decision-coaching, with ICF-based frameworks, to hold exec-sponsor NPS and support big bets.

Techniques CTO / VP / Director 1:1 coaching Marshall Goldsmith stakeholder centered GROW, CLEAR, Solution-Focused Decision-coaching for irreversible bets

Tools ICF PCC / MCC coaching templates Notion / Confluence coaching journals Loom for async coaching nudges

Metrics Executive-sponsor NPS Coaching engagements held per quarter Decisions taken with coach support

Multi-Train & Multi-Team Coaching

You sync many teams and trains at once, keeping them aligned. Hiring managers look here to see whether you can scale coaching across ARTs, or only fix one team at a time. Point out how you used cross-ART synchronization and pattern replication, in Jira Plans, to coach ARTs concurrently and resolve cross-ART dependencies.

Techniques Cross-ART synchronization cadences Pattern replication & standardization Inspect & Adapt at solution train level Solution-train coaching (Large Solution SAFe)

Tools Jira Plans / Portfolio for Jira Miro multi-ART program boards Confluence shared cadence wiki

Metrics ARTs coached concurrently Cross-ART dependencies resolved Solution-train predictability

Agile Maturity Assessment & Roadmapping

You diagnose where the org's agility actually stands. A gut feeling won't fund a transformation, so hiring managers want a maturity assessment with a real improvement delta. Mention how you used a maturity assessment and diagnostic interviewing, with the Agile Fluency assessment, to map maturity per dimension and drive an improvement delta.

Techniques Maturity assessment instrument design Diagnostic interviewing (Edgar Schein) Roadmap sequencing from findings Quarterly health re-assessment

Tools Agile Fluency assessment, AgendaShift Officevibe / CultureAmp pulse Mentimeter for survey rollouts

Metrics Maturity index per dimension Re-assessment improvement delta Roadmap initiative completion

Coaching Dojos & Capability Building

You build the next generation of coaches and Scrum Masters. One coach doesn't scale, so building coaching capability tells a hiring manager you multiply the whole practice. Walk them through how you designed coaching dojos and train-the-trainer programs, in Confluence, to certify Scrum Masters and retain the cohort.

Techniques Coaching dojo design (Joshua Kerievsky) Train-the-trainer programs PO coaching circles Pair-coaching with junior coaches

Tools Confluence / Notion dojo curricula Coursera / O'Reilly Learning paths Mentorship platforms (Together, MentorcliQ)

Metrics Scrum Masters certified per cohort Retention of coached cohort Internal coaching NPS

Lean Portfolio Management

You move the money to the work that matters most. Two things ride on it for a hiring manager: investment redirected to strategic themes, and a portfolio that flows faster. Lay out how you used Lean Portfolio Management and WSJF facilitation, in Jira Align, to redirect investment and cut portfolio cycle time.

Techniques Lean Portfolio Management (SAFe LPM) WSJF prioritization facilitation Strategic theme funding redesign Beyond Budgeting (Bjarte Bogsnes)

Tools Jira Align, Atlassian Compass Productboard, ProductPlan Pitch decks for portfolio review

Metrics Investment redirected ($) Portfolio cycle time Strategic theme attainment

Change Management & Organizational Design

You get an org to actually adopt a new way of working. A reorg on paper changes nothing, so hiring managers read tracked adoption as change that stuck. Spell out how you used ADKAR and Team Topologies, with Prosci templates, to raise change-adoption and manage real re-org transitions.

Techniques Kotter 8-step framework ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) Team Topologies (Skelton & Pais) Communication strategy & sequencing

Tools Prosci ADKAR templates Confluence change wikis Loom / town-hall video for org comms

Metrics Change-adoption % Resistance signals tracked Re-org transitions managed

Community of Practice & Knowledge Sharing

You spread what works through a community of practice. Companies keep the coaches who leave a durable practice behind, not the ones whose impact leaves with them, so this stands out. Tell them how you built a community of practice and open spaces, in Confluence and Slack, to grow membership and share what works.

Techniques CoP design & facilitation Internal conferences & open spaces Public writeups & case studies External conference speaking

Tools Confluence / Notion CoP wikis Slack CoP channels, Loom share-outs SessionLab for open-space design

Metrics CoP members & engagement Open-space attendance / NPS External talks delivered per year

Once you address all of the above, the most recent role lands at roughly eight to ten bullets. That depth is on target, not bloat, no matter what the single-page rhetoric on LinkedIn keeps repeating. Recruiters do not grade pages; two dense pages of real content win against a thin single page every time. The thing killing the screen is padding: lines that take up room without saying anything, and cutting padding is what the next section is entirely about.

Step 4 · Agile Coach Bullet Points

Bullet points for an
Agile Coach resume

On any rewrite, the bullet section consumes the largest share of my hours. The disciplined method I built to handle it, the Level System, came out of that work and now runs across every guide on the site.

The underlying base isn't fictional: it builds on Google's XYZ formula, then pushes further for power-electronics specificity. The mechanics in full live at how to write resume bullet points.

Best way in: pick any ordinary QA bullet and rebuild it one layer at a time. The framework runs 5 questions, and each answer adds the next layer of engineering depth onto the line.

Walking them in sequence drives the bullet out of generic description and into the framework, CI, and coverage specifics that hiring managers actually evaluate when picking the QA interview shortlist.

1 Task “What did I work on?” What you did
2 + Techniques “How did I do it?” How you did it
3 + Tools “What tools did I use?” Frameworks, data stores, infra
4 + Method “What method did I follow?” Named methodology
5 + Metric “What was the result?” Quantified impact

Level 1, Just the task. Pick one specific thing you actually built or owned. This is the base layer, not the final line. Plenty of Agile Coach resumes never move past it, and that's a big reason so many get filtered before a screening call.

Level 1
Just the task

Coached 6 ARTs at a Fortune 500 healthtech.
Level 2, Add the techniques. Name the specific engineering practices the work used: the testing types, rendering modes, scaling tactics, design patterns. This is where the bullet starts proving you understand how the work was done, not just that it shipped.

Level 2
+ Techniques

Coached 6 ARTs at a Fortune 500 healthtech using executive coaching and agile-maturity assessment.
Level 3, Add the tools. Drop in the named products and versions you used: the framework, the database, the build tool. Recruiters search resumes with technology queries, so the bullet stays invisible without the named stack.

Level 3
+ Tools

Coached 6 ARTs at a Fortune 500 healthtech using executive coaching and agile-maturity assessment in Confluence with quarterly Inspect & Adapt workshops.
Level 4, Add the method. Name the methodology, framework, or design pattern that guided the work: TDD, DDD, BDD, GitOps, MVVM, CQRS, progressive enhancement, and so on. The hiring manager is usually the one enforcing the methodology on the team, so naming yours shows you fit how they actually operate.

Level 4
+ Method

Adopted the Agile Fluency Model to coach 6 ARTs at a Fortune 500 healthtech using executive coaching and agile-maturity assessment in Confluence with quarterly Inspect & Adapt workshops.
Level 5, Add the metric. A number is what lifts a bullet into the top 1%. It pulls double weight: it shows the impact was real, and it shows you measured it on purpose. Skip the number and the line reads identical to every other candidate's.

Level 5
+ Metric

Adopted the Agile Fluency Model to coach 6 ARTs at a Fortune 500 healthtech using executive coaching and agile-maturity assessment in Confluence with quarterly Inspect & Adapt workshops, lifting org agile-maturity index from 2.1 to 3.8 across 200 engineers.

For the full walkthrough, including the trick I use to extract numbers from work that looked unmeasured, see writing resume bullet points. Most Agile Coachs already have the data: PI predictability, sprint goal hit rate, lead time, cycle time, retro action close rate, team eNPS, attrition, impediments resolved per sprint. It just never made it onto the page.

Step 5 · Agile Coach Technical Skills

Technical skills for an Agile Coach resume

The ATS parses your Technical Skills section, and some systems use it for keyword filtering. That's why it needs to echo the language on the job description you're targeting.

By now, though, we're down to the fine details. Nailing this section gives you a nudge through filtering and screening, but the real weight is carried by your Profile Summary, Work Experience, and Bullet Points.

Still, the skills and keywords accumulate over the whole resume, so it pays to know what an ATS and a recruiter both watch for. That's why a separate page exists covering every Agile Coach skill that matters, technical and soft, with a built-in keyword parser that tunes it to a specific posting.

Transformation Frameworks

Org agility: Agile Fluency Model (Shore / Larsen), Agendashift Scaled: SAFe Implementation Roadmap, LeSS, Scrum@Scale Disciplined Agile: DA toolkit, choice-based agility Change models: Kotter 8-step, ADKAR, Cynefin Team Topologies: Skelton & Pais (stream-aligned, platform) Systems thinking: Deming, Sociotechnical Systems
Executive Coaching

Coaching credentials: ICF ACC / PCC / MCC, EMCC Coaching models: GROW, CLEAR, Solution-Focused, Co-Active Stakeholder centered: Marshall Goldsmith methodology Powerful questions: Co-Active, Reframe inquiry Executive presence: Sylvia LaFair, Amy Edmondson Conflict navigation: Lencioni, Crucial Conversations
Multi-Train Facilitation

Whiteboards at scale: Miro, Mural, FigJam multi-board Liberating Structures: 33 patterns, 1-2-4-All, Troika Inspect & Adapt: SAFe I&A, retrospectives at scale Open Space Technology: Owen, World Cafe Engagement: Mentimeter, Slido, Polly Solution-train events: Pre-PI, PI planning, Solution Demo
Lean Portfolio Management

LPM frameworks: SAFe LPM, Disciplined Agile Portfolio Prioritization: WSJF, Cost of Delay, MoSCoW Beyond Budgeting: Bjarte Bogsnes 12 principles Portfolio tooling: Jira Align, Atlassian Compass, Productboard OKR cascades: John Doerr, Christina Wodtke, Mooncamp Strategic themes: McKinsey 3-horizon, Wardley mapping
Capability Building & Communities

Train-the-trainer: ICAgile ICP-ATF, Joshua Kerievsky dojo Cert programs: CSM, A-CSM, CSP, PSM I-III, ICAgile SAFe certs: SAFe SPC, SAFe RTE, SAFe SASM CoP design: Etienne Wenger, internal facilitation guilds Internal conferences: Agile Open, SessionLab planning Knowledge platforms: Confluence, Notion, internal wikis

Stop guessing. Ask a recruiter directly.

You now have the format, the profile summary template, the role profile, the bullet system, and the skills categories. All that's left between your draft and the interview is a set of eyes that screened thousands of Agile Coach resumes telling you what to fix.

That's the free review.

Send the draft over. Back comes a simulated recruiter screen, a graded checklist, and a specific action list. Free, within 12 hours.

Want to read more first? How the resume review works →

Frequently asked

Agile Coach resume FAQ

How long should an Agile Coach resume be?

Maps to the trains you have run and the increments you have shipped. Below 5 years, a single page usually fits. At senior or lead PO, with multiple PI cycles you have planned, a 3-team train you have aligned, a stakeholder QBR you have owned, and a SAFe or CSPO credential in hand, two pages is the correct call. The "one-page rule" from generic career advice doesn't apply to agile coachs at scale. Padding hurts, but so does compressing a decade of delivery work into a single sheet. My tech resume length framework grows with seniority instead of locking to a page total.

Should it be one page?

Almost never at this level. The real question is content density. First-time Agile Coaches might fit on one page because there is not enough transformation history to fill more. At Senior or Lead Agile Coach with multi-year engagements behind you, multi-train coaching, a maturity-index trend you have moved, and executive sponsors you have coached, forcing it onto one page deletes the exact evidence that would open the conversation with a Director of Engineering or VP.

What is the most important section?

Your most recent role, hands down. Roughly 95% of the screening conversation comes from that one role, because hiring teams open it first to check the scope of the engagement (single ART, multi-train, enterprise), the company size and stage (Fortune 500, Series C, post-IPO), the transformation framework (Agile Fluency, SAFe Implementation Roadmap), and the maturity-index or NPS outcome you moved. The profile summary is second only because it sits above and gets read on the way down.

How do I get my resume past ATS?

Keep it single-column: drop the header icons, sidebars, and images, use plain section titles (Profile Summary, Core Competencies, Work Experience, Education), and export to PDF instead of DOCX. Then run it through my free ATS parser tool and check it is pulling out the transformation vocabulary. If "SAFe SPC" or "agile transformation" or "executive coaching" vanishes from the output, the layout is what is broken, not the content.

What keywords should I include?

For 2026, the ones you can not skip are an agile framework (SAFe, Scrum@Scale, LeSS, Disciplined Agile), a coach certification (SAFe SPC, ICF PCC, A-CSM / CSP, ICAgile ICP-ATF / ICP-LEA), a transformation framework (Agile Fluency, SAFe Implementation Roadmap, Kotter, ADKAR), a Lean Portfolio signal (Lean Portfolio Management, WSJF, Beyond Budgeting), and an executive-coaching signal (executive coaching, stakeholder centered coaching, Marshall Goldsmith). Strong supporting keywords are agile maturity assessment, communities of practice, coaching dojos, multi-train, and organizational change. Senior candidates add terms like enterprise transformation, Fortune 500, M&A integration, and executive sponsor coaching where relevant. The full list of Agile Coach resume skills, ranked by demand, includes a bullet example for each.

Do I need a GitHub or portfolio link?

GitHub is irrelevant. What lands instead is a public coaching trail: a SAFe Summit keynote, an Agile Alliance Agile2026 talk, a writeup of a multi-train transformation, a LinkedIn article on executive coaching. For Senior Agile Coaches, the engagements you closed and the maturity-index or NPS numbers you moved at past employers carry most of the proof, so LinkedIn plus a one-paragraph engagement summary per role covers it. ICF PCC / MCC, SAFe SPC, ICAgile ICP-ATF / ICP-LEA, or executive coaching credentials are gold.

Should I list ICF PCC, SAFe SPC, and ICAgile ICP-LEA if I have all three?

List all three when current and a real reflection of how you operate. ICF PCC signals professional coaching depth, SAFe SPC signals scaled-agile transformation authority, ICAgile ICP-LEA signals enterprise agile-leadership rigor. The combination tells a hiring director you can coach individuals, run multi-train transformations, and consult on enterprise transformation. Where it backfires: an expired ICF accreditation or a SAFe SPC you never put to use reads worse than not listing them. If a cert is current and earned, list it.

How long should my profile summary be?

Target five bullets, treat six as the hard cap. A paragraph asks a hiring director to read carefully inside a window that exists only for scanning, which never happens on a first pass. As bullets, they pattern-match you against the engagement scope, the transformation framework, and the maturity or NPS outcome in under a second and decide whether the page deserves more attention.

Who wrote this

Built by an ex-Google recruiter

Emmanuel Gendre

Former Google recruiter · 12 years · 1,500+ tech resumes rewritten

I screen Agile Coach resumes the same way I did at Google: against the role profile, against the JD, and against the bar real hiring managers set. Everything in this guide is the field manual I use with my own clients.

Read my full story →

More resources

Other Agile Coach Resume Resources

Service

Agile Coach Resume:
The Complete 2026 Guide

My experience with Agile Coach resumes

How I rewrite an Agile Coach resume