The skills a scrum master needs, in the order worth learning them: what employers expect first, what to add next, and the tools you will work in.
Essential skills are the ones most employers look for before they look at anything else.
A sensible order for someone starting out. Skip ahead where you already have a skill.
Get comfortable with agile and scrum practices, facilitation of meetings and workshops and backlog and flow metrics. Nearly every employer looks for these before anything else.
Add coaching and conflict resolution, work tracking tools and scaling frameworks. These turn a capable beginner into someone who can work with little supervision.
Choose a direction such as team-level coaching or agile coaching at scale, and add its skills: facilitation, coaching and team health.
Use each skill on a small, real project or task as soon as you can. Evidence of use is worth more than a list of courses.
These decide how well the technical skills get used.
Names change with fashion and employer; what matters is understanding what each kind of tool is for.
Adding these opens the more specialised versions of the role.
Speed and accuracy with data underpins nearly every role in this group.
Understanding revenue, costs and cash in the organisation makes your recommendations credible.
Case-style and judgement questions reward a clear framework and calm reasoning.
Skills stick when you use them. Each of these gives you something real to show or talk about.
Plan a mock sprint for a small project with a goal, a backlog, a daily routine and a retrospective format.
Run a retrospective with friends on a shared project and record three actions.
Draw a flow board for a personal project and track where work gets stuck for two weeks.
List a skill next to the work that proves it. These are the ones a reader scanning for this role will look for first.
Agile and scrum practices is one of the first things most employers look for, alongside facilitation of meetings and workshops and backlog and flow metrics. Show each with real work rather than only naming it.
servant leadership and listening, patience and persuasion and neutral, calm facilitation come up most often. They decide how well the technical skills get used, and they are what interviewers test with questions about past situations.
Start with the essentials: agile and scrum practices, facilitation of meetings and workshops and backlog and flow metrics. Once you are comfortable, add coaching and conflict resolution, work tracking tools and scaling frameworks. The specialist tracks, such as team-level coaching, come after that.
A work-tracking tool, Online whiteboards, Team dashboards and Retrospective formats are typical for the role. Pick one in each category and learn it well; the ideas carry over when an employer uses a different product.
List a skill next to the work that proves it: what you did, at what scale and with what result. Put the most relevant skills near the top, using the words the job description uses, but only for skills you really have.
Upload your resume and the job description, and the AI interviewer builds its questions from both. Every answer is scored against the bar for the role, with notes on what to fix.