This guide is for Scrum Masters at every level, Agile Coaches, and people moving into the role from QA, development or project management. You'll learn which keywords to include, how to write a summary for your level, and how to turn "facilitated ceremonies" into bullets that prove your team improved.
Keyword match
Scrum Master, Payments Platform
6/9must-have skills
Found on your resume
Missing
JORDAN ALVAREZ
Denver, CO · (720) 555-0148 · jordan.alvarez@email.com · LinkedIn
Summary
5 years as a Scrum Master for distributed product teams across Scrum, Kanban and SAFe. Turns missed sprint goals into predictable delivery with flow data.
1Skills
Scrum · Kanban · SAFe PI Planning · Jira · Confluence · Azure DevOps · Flow Metrics · Backlog Refinement · Dependency Management · Facilitation
2Experience
Scrum Master Bramblecrest Health Software · Mar 2022 – Present
Years plus team context up front tell a hiring manager your level in seconds.
Summary examplesFrameworks and tools match job-ad wording, so the ATS and a skimming recruiter both find them.
Keywords and skillsThree teams and 22 engineers place your level before the metric shows what changed.
Bullet pointsCoaching appears as a result (a Product Owner who now keeps a refined backlog), not as a claimed soft skill.
Naming the issuing body separates a real credential from a training-vendor certificate and lets recruiters verify it.
CertificationsEvery candidate facilitated sprint planning. Hiring managers screen for what changed because of you: less carryover, faster cycle time, steadier sprint goals.
Velocity is a team's own planning aid, so bragging about raising it is a warning sign to experienced agile leaders. Predictability, flow metrics (cycle time, throughput, work item age) and sprint goal attainment show you know what the numbers are for.
Say how many teams and people, which framework, whether teams were distributed, and which tools you ran. Mid-level postings often describe two or three teams; senior postings add mentoring Scrum Masters and working across an Agile Release Train.
O*NET lists Scrum Master as a job title under Information Technology Project Managers (15-1299.09), and some employers combine the two jobs. Under the Scrum Guide, the Product Owner manages the backlog and the Scrum Master is accountable for the team's effectiveness, so a team-focused role rarely owns scope or budget; a hybrid role may. Match your bullets to the version the posting describes.
You don't need to code, but you should be credible on CI/CD, Definition of Done, technical debt and release readiness.
O*NET flags Jira and Confluence as in-demand technologies for this occupation.
For Agile Coach roles, these should carry most of the resume.
Soft skills
Leave "servant leader" off the skills line and prove it in bullets: a conflict resolved, a stakeholder won over, a team that now runs its own retros.
Certified ScrumMaster (CSM) moving into the role after two years as a QA analyst on a Scrum team building a mobile banking app. Ran reviews and retrospectives for six sprints while the team's Scrum Master was on leave and built the Jira carryover dashboard the team still uses. Brings defect-triage experience to Definition of Done discussions.
Why it works: It turns adjacent experience into direct Scrum Master evidence.
Scrum Master with six years supporting B2B SaaS teams in Scrum and Kanban, currently serving two teams totaling 14 engineers. Rebuilt refinement so sprint carryover fell from roughly a third of committed items to under 10%, and introduced cycle-time forecasting that gave Product a delivery range it could share with customers. PSM II.
Why it works: It pairs current scope with two outcomes product leaders value: finishing planned work and forecasting honestly.
Senior Scrum Master and Agile Coach with 11 years in financial services, most recently on a nine-team SAFe Agile Release Train of about 85 people. Facilitates PI Planning, coaches the train's Scrum Masters, and led the shift from velocity reporting to flow metrics, shortening average feature lead time by about a third. CSP-SM and SAFe Advanced Scrum Master.
Why it works: Train-level scope and a change in how the organization measures work are what separate senior from mid level.
WeakFacilitated daily standups, sprint planning and retrospectives.
StrongRestructured a 25-minute daily scrum around the sprint board, bringing it to 12 minutes and returning about 2 engineer-hours a day to a 9-person team.
What changed: A routine duty became a measurable time saving.
WeakResponsible for maintaining Jira boards.
StrongArchived 340 stale Jira tickets and added a "Ready" column with entry criteria, so every story brought to sprint planning met the team's Definition of Ready.
What changed: "Responsible for" became a cleanup plus a lasting process change.
WeakIncreased team velocity by 40%.
StrongRaised sprint goal attainment from 46% to 81% over two quarters by coaching the team to split any story estimated above 5 points during refinement.
What changed: An easily inflated number became an outcome metric, with the coaching move named.
WeakRemoved impediments for the team.
StrongSet up a weekly blocker review with platform and security leads that cut average time to clear cross-team impediments from 8 days to 2.5.
What changed: It shows a system for impediments, not a promise.
WeakWorked with stakeholders to improve communication.
StrongReplaced a 14-slide weekly status deck with a live Confluence page fed by Jira, saving the Product Owner about 3 hours a week and giving stakeholders same-day sprint risk visibility.
What changed: "Improve communication" became a concrete artifact with time saved.
WeakHelped the team adopt DevOps practices.
StrongPartnered with the engineering manager on WIP limits and a daily deploy target; median lead time for changes fell from 11 days to 4 and deploys rose from twice a month to 3–4 a week.
What changed: It credits the partnership and uses metrics engineering leaders already track.
WeakCoached other Scrum Masters.
StrongBuilt a 6-week onboarding path for new Scrum Masters on a 7-team Agile Release Train; 5 of the 6 hired since 2023 ran their own PI Planning breakouts by their second PI, and one moved into the RTE role.
What changed: Mentoring is measured by what the people you developed can now do.
WeakLed agile transformation.
StrongCoached three VP-level leaders through a waterfall-to-Scrum shift for a 120-person division, standing up 11 teams in 9 months and replacing annual project gates with quarterly planning.
What changed: "Transformation" now has a size, a timeline and a structural change.
Certification isn't required for the job, but many employers ask for one. The baseline credentials are Certified ScrumMaster (CSM) from Scrum Alliance and Professional Scrum Master I (PSM I) from Scrum.org. CSM requires a 16-hour course with a Scrum Alliance Certified Scrum Trainer plus a 50-question test (37 correct to pass), and it renews every two years with continuing-education units and a fee. PSM I has no course requirement, an 85% passing score, and doesn't expire.
If you're entry level or the posting names a certification, put the acronym in your summary and the Certifications section near the top; otherwise, place it after Experience. Format each as credential, issuing body, year: "Certified ScrumMaster (CSM), Scrum Alliance, 2024." Drop expired credentials, since recruiters can check.
Listing one in progress
Show status and a date: SAFe Scrum Master (SSM), Scaled Agile — exam scheduled [Month Year].
O*NET places this occupation in Job Zone Four, where most occupations require a four-year bachelor's degree, though some don't. Computer science, information systems and business are all common. List degree, school and year.
"Facilitated all Scrum events" describes the job, not your performance.
FixMention the events once in your summary, then make every bullet about what changed.
Velocity is relative to each team's estimates, so "increased velocity 50%" suggests inflated points or a misunderstanding of the metric.
FixUse sprint goal attainment, predictability, cycle time, throughput or carryover instead.
"Assigned tasks to developers" conflicts with self-managing teams and makes Scrum-literate interviewers wary.
FixUse "supported," "coached" or "partnered with," unless the posting is a hybrid role that includes direct management.
"Delivered 14 features" hides your contribution.
FixName the change you introduced and link it to the team's result.
Without team count, framework and tools, the reader can't place your level.
FixOpen each role with a one-line scope statement, such as "2 Scrum teams, 16 engineers, Jira and GitLab."
One page if you have under about five years of experience or are changing careers. Two pages suit senior Scrum Masters and Agile Coaches with multi-team work. Keep roles older than 10–12 years to a line or two.
Both are widely recognized. CSM includes a live course and renews every two years; PSM I is a standalone assessment with a higher passing score (85% versus 74%) and no renewal. If a posting names one, feature that one.
Keep your real title and lead with the Scrum Master work you did. A parenthetical such as "QA Analyst (acting Scrum Master, 6 sprints)" is fine if it's accurate and a reference would confirm it.
List the end date honestly; "Position eliminated in restructuring" is enough explanation. Add any new certification, contract coaching or volunteer facilitation to show your skills are current.
Only if you held the title or documented coaching beyond one team. Otherwise keep "Scrum Master" and show coaching scope in bullets: leaders coached, teams launched, Scrum Masters mentored.
Paste a job ad and get a fit score, the keywords you're missing and the one thing to fix first.
Start for free