The skills, tools and soft skills scrum master job descriptions keep asking for, grouped and ranked, with before/after bullets to show you how to use them.
Scrum master postings test whether you run Scrum or only attended it. They name the events (sprint planning, daily stand-up, sprint review, retrospective), the practices (backlog refinement, impediment removal, Agile coaching), the scaled frameworks (SAFe, LeSS) and the tools (Jira, Confluence). Applicant tracking systems match those terms, and hiring managers then look for how many teams you served and what changed in their delivery. The lists below cover the vocabulary of US and Canadian Scrum master and Agile delivery lead postings.
Most mid-size and large employers in the US and Canada receive applications through an applicant tracking system such as Workday, Greenhouse, Lever, iCIMS or Taleo. The system parses your resume into fields (titles, dates, skills) and lets recruiters search and rank candidates by the terms in the job description. Some systems only match exact words; others recognize close variants. Either way, the safest approach is to use the same wording as the posting for every skill you genuinely have — inside a bullet that explains what you did with it.
Methods, domain knowledge and techniques that describe what you can do as a scrum master.
Facilitating the events is assumed. Say what you improved in them: shorter planning, actionable retros, a clear Definition of Done.
Scaled frameworks are common in enterprise postings. Mention your role in PI planning or a release train if you had one.
Use metrics as a way to help teams, not to judge them. Mention the ones your teams tracked.
Named software and platforms. Spell them exactly as the posting does — "Jira", not a generic description.
Jira dominates; Azure DevOps and Rally appear in enterprise postings. List the ones you configured or administered.
Postings name them, but a single word proves little: pair each one with an action in a bullet.
Soft skills are hard to prove with a single word. Show each one through an action: who you worked with, what you explained, what you resolved. An ATS may still match the phrase, and the recruiter gets evidence instead of a claim.
Scrum certifications are commonly listed as preferred: the CSM (Certified ScrumMaster) and A-CSM from Scrum Alliance, the PSM I and PSM II from Scrum.org, and SAFe Scrum Master (SSM) or SAFe Advanced Scrum Master from Scaled Agile. The PMI-ACP from PMI is also recognized. They carry the same meaning in the US and Canada.
The vocabulary and certifications are identical in both countries. Canadian public-sector and bank postings often ask for "Agile delivery lead" or "Scrum master" with bilingual English/French in Ottawa or Quebec; US federal contractor roles sometimes require a clearance. Title wording varies: "Agile coach", "delivery lead", "Scrum master". Mirror the posting in your summary while keeping your real title.
In both countries, leave out your photo, date of birth and marital status, keep the resume to one or two pages, and list experience in reverse chronological order.
Vague lines hide your keywords. Name the skill, the tool and what it was for. Keywords are highlighted in each rewrite.
Ran the Scrum meetings.
Served as Scrum master for two cross-functional teams, facilitating sprint planning, sprint retrospective and backlog refinement in Jira.
Helped the product owner.
Coached a new product owner on backlog ordering and introduced a shared Definition of Done, improving sprint predictability over two quarters.
Joined planning with other teams.
Took part in quarterly PI planning in a SAFe release train, tracking dependency management across five teams in Jira Align.
Agile enthusiast who loves helping teams.
Scrum Master (PSM I) supporting cross-functional teams with Scrum and Kanban, Agile coaching and impediment removal, experienced with SAFe PI planning and Jira.
These are examples to adapt, not real employer results: change the tools, scope and outcome to what you actually did. To see the keywords inside complete resumes, look at our scrum master resume examples (entry level, mid level and senior). Browse all tech resume examples too.
Four places carry keywords. Use each for what it does best.
Two or three lines that repeat the job title from the posting and the three or four skills it stresses most. The first text the parser and the recruiter read.
They carry the most weight because they show the keyword in use. Start with an action verb, name the tool or skill, say what it was for.
A short list grouped by type, in the posting's exact spelling. No stars or percentage bars: parsers cannot read them.
Keep your real job titles and use standard section names (Experience, Education, Skills, Certifications) so keywords land in the right field.
Keyword lists are a starting point. The job you are applying to is the real test.
Read the posting once for meaning, then a second time with a highlighter: mark every tool, method, certification and responsibility it names, and note which ones appear under "required" versus "nice to have". Compare that list with your resume. For each required term you genuinely have, make sure it appears at least once in a bullet; for each one you lack, do not add it — prepare to address it in the interview instead.
The free ATS resume checker does this comparison for you: paste the job description and your resume and it lists the matched and missing keywords. If you want a version of your resume rewritten for that posting, the AutoApplyMax AI resume builder can generate a tailored resume from your own experience (the free plan includes 1 AI credit per month) — it reorders and rephrases what is already true rather than inventing experience.
Short answers to the questions people ask before tailoring their resume.
The most important keywords are the ones in the job description you are applying to. This page groups the terms that scrum master postings in the US and Canada use again and again — for example Scrum, sprint planning, sprint retrospective, backlog refinement — but each employer weights them differently. Copy the required skills from the posting, then check which of them you can honestly show.
Both are recognized. Postings often write "CSM or PSM". List the one you hold exactly as named by the issuer.
Yes. Show facilitation and team-coaching work, and use Scrum vocabulary for the parts of your projects that were Agile.
Be careful: velocity is a planning tool, not a performance score. Predictability, cycle time or fewer carry-over items are better ways to show change.
Not deep ones, but naming the kind of product (cloud platform, mobile app, data pipeline) helps the ATS match you to the right teams.
No. Repeating a word many times, or hiding keywords in white text, does not help with modern ATS ranking and is obvious to the recruiter who reads the resume next. Each keyword should appear where you actually used the skill.
Many of these skills transfer. Compare lists if you are switching roles.