Scrum Master resume example

Also indexed as: agile coach · delivery manager · agile delivery lead

The most common scrum master resume is a list of ceremonies: facilitated standups, ran retrospectives, maintained the board. Every scrum master does those, and reciting them signals process administration rather than delivery. It is also the fastest way to be filtered by a hiring manager who has been burned by exactly that.

What earns interviews is evidence that teams got better on measurable axes. Predictability (did they finish what they committed to), plus cycle time, escaped defects, and team health. And crucially, the impediments you actually removed, which is where the job is either real or theatre.

Lena Márquez
Growth Marketing Manager, B2B SaaS lifecycle & paid
lena@marquez.work
+34 612 555 019
Barcelona, ES
linkedin.com/in/lenamarquez
marquez.work
Summary

Growth marketer who owns the number, not the campaign calendar. Took a self-serve funnel from 1.2% to 3.4% visitor-to-trial over four quarters and rebuilt the lifecycle programme that now drives 31% of new ARR. Equally comfortable in the ad account and the data warehouse.

Experience
Growth Marketing ManagerJan 2022 – Present
Fathom Analytics · Barcelona, ES
Lifted visitor-to-trial conversion from 1.2% to 3.4% in four quarters through 61 shipped experiments, worth €2.4M in incremental ARR.
Rebuilt lifecycle email around product signals rather than send dates; the programme now sources 31% of new ARR at a 4.2% unsubscribe rate.
Cut blended CAC 38% by killing three underperforming channels and reallocating €480K into paid search and partner content.
Built the attribution model in dbt that finance now uses for board reporting.
Demand Generation LeadSep 2019 – Dec 2021
Ориго Software · Remote
Grew organic sessions 214% year over year with a 180-page programmatic content build targeting long-tail comparison intent.
Launched the partner co-marketing programme that produced 1,100 SQLs in its first year.
Education
B.A. Business & MarketingSep 2015 – Jun 2019
Universitat Pompeu Fabra · Barcelona, ES

A complete document in the Meridian family of layouts, rendered live, not a screenshot.

The screen

What a scrum master resume is actually judged on

01

Predictability, before and after

Say-do ratio or sprint commitment met. The most honest single measure of a scrum master's effect.

02

Cycle time and flow

Lead time, work in progress, how you reduced it. Shows you understand the system rather than the ritual.

03

Impediments removed

Specific organisational blockers you cleared. This is what separates coaching from scheduling.

04

Context: teams, scale, framework

How many teams, how large, and whether Scrum, Kanban, SAFe or something local. Plus certification.

Bullets

5 bullets that would survive the screen

Copy the shape, not the words. Each one leads with the result, then names the mechanism, and carries the vocabulary of the field without listing it.

  • Took two teams from a 61% to a 92% sprint commitment rate over four months by fixing story sizing and capping work in progress at four items.

  • Cut average cycle time from 11 days to 4 by making the handover to QA a shared column rather than a queue, which removed the mid-sprint stall.

  • Removed a three-week environment provisioning dependency by negotiating a shared pre-production namespace with the platform team.

  • Reduced escaped defects per release from 9 to 2 by adding a definition of done that included the automated check, agreed by the team rather than imposed.

  • Coached two product owners through backlog refinement; refinement meetings went from 90 minutes to 35 with better-formed stories.

The rewrite that matters most in this role

Before

Facilitated daily standups, sprint planning, retrospectives and sprint reviews for two agile development teams.

After

Took two teams from a 61% to a 92% sprint commitment rate in four months, with story sizing plus a hard WIP limit of four.

Why it works: Facilitating ceremonies is the job description, not an achievement. The rewrite names the metric the role exists to move, the movement, and the two specific interventions that caused it.

Skills

Skills worth listing as a scrum master

Only what you would be comfortable being interviewed on. A long list dilutes every real match.

Technical & role-specific

ScrumKanbanJiraAzure DevOpsConfluenceFlow metricsStory mappingSAFeRelease planningDependency management

Worth proving, not claiming

FacilitationCoachingConflict resolutionInfluence without authorityStakeholder management

These belong inside a bullet that demonstrates them, not in a list. A line that says “communication” is worth nothing; a bullet showing you ran the workshop is worth a lot.

Keywords

What the tracking system is indexing

These are the terms a requisition for this title typically matches on. Use the ones that are true of you, inside the sentences where you did the work.

scrum masteragileScrumKanbansprint planningJirabacklog refinementvelocitycontinuous improvementCSMPSMSAFe

Paste the actual posting into the builder and you get this list generated from that requisition instead of the general case, including which terms you are already carrying and which bullet is the right home for the rest.

How keyword targeting works

Mistakes

Errors specific to scrum master resumes

Not the generic advice. These are the ones that cost people interviews in this particular field.

Listing ceremonies as accomplishments

It reads as administration. Lead with what the team's numbers did.

Velocity as a headline metric

Velocity is not comparable across teams and is trivially gamed. Predictability and cycle time are the credible ones.

No mention of impediments

Removing organisational blockers is the substance of the role. Without an example, seniority is unprovable.

Certification as the whole story

CSM or PSM clears filters; it never carries the resume. Put it in a line and move on.

Questions

Scrum Master resume questions

Scrum master or delivery manager?

Match the posting. Delivery manager usually implies budget, vendors and reporting, so reweight toward those bullets when you use it.

Which certification should I get?

PSM or CSM for filters; anything beyond that matters less than a demonstrated improvement in a real team's delivery.

How do I show coaching without sounding vague?

Tie it to an outcome: refinement time halved, a product owner who stopped writing solution-shaped stories, a team that started raising risks before the review.

Start from this example instead of a blank page

Free plan, no card. Import what you already have, or write it from scratch with the bullets above as the target.