The advice you will find is a loop. Employers want experience. Experience requires a job. The job requires experience.
Most articles answer this with “volunteer for a non-profit” or “shadow a scrum master at your current company”, which is fine if you happen to work somewhere with a scrum master and terrible if you are a nurse.
Here is what actually moves you, in the order it is worth doing.
First, understand what they are really asking for
When a job advert says two years of scrum master experience, the hiring manager is not counting years. They are trying to avoid hiring somebody who has read about it and never had to do it under pressure.
What they want to know is whether you have ever:
- Had something blocked and got it unblocked by talking to people who did not report to you
- Delivered bad news early, with a number attached, instead of late with an apology
- Watched a plan fail and changed how the team worked afterwards
You can have done all three without ever having held the title. Most career changers have. They just describe it in the vocabulary of their old job, so nobody recognises it.
Second, build something you can be questioned on
This is the part the loop-breaking advice usually skips.
The interview is going to ask about a blocker, a sprint that missed, a retrospective that changed something. You need a specific situation to answer from. Not a hypothetical, not a definition. A project, with dates, with a cost you can name.
So build one. A small delivery project: four epics, twelve stories, three sprints, one thing that went wrong. Run the sprints in Jira so you have a velocity chart and a burndown, because those are artefacts an interviewer recognises on sight.
Then be able to talk about the one that went wrong for five minutes without running out. That story is most of your interview.
Say it is a practice project, every time, in one sentence. It costs you nothing and it protects everything else you say.
Third, get real facilitation reps, which is the bit you cannot fake
A board proves you understand the mechanics. It does not prove you can run a room, and that is what a scrum master is hired for.
Places to get actual reps without a job title:
- Whatever you already run. If you chair anything, a handover, a shift briefing, a committee, a parents group, start running it deliberately. Timebox it. Open with the purpose. Close with who owns what. You are practising the same skill on a different subject.
- Volunteer delivery work, but pick carefully. A charity that needs a website rebuilt has a real backlog, real stakeholders and a real deadline. A charity that needs a volunteer rota does not need a scrum master.
- Run the ceremonies on your own board, out loud, alone. This sounds ridiculous for about four minutes. Then you discover you do not actually know how to open the meeting, which is exactly the thing that would have gone wrong in front of people.
Fourth, fix the vocabulary on your CV
You almost certainly have relevant experience described in words nobody in delivery recognises.
- A ward handover is a standup with higher stakes and worse tooling
- Triage is prioritisation under time pressure with incomplete information
- An incident review with agreed actions is a retrospective
- Coordinating four staff who do not report to you is influence without authority
Translate the verb. Never touch the evidence. You do not invent a percentage, you do not promote yourself to a title you never held, and you do not call a handover a scrum. You describe the same true thing in the words the reader speaks.
What about certification
A CSM or PSM gets your CV past a filter and tells an interviewer you have learned the vocabulary. It does not substitute for experience and no hiring manager thinks it does.
Get one, but get it in the right order. Certification with nothing to talk about is a candidate who has read the book. A project plus a certification is a candidate who has read the book and then done something with it.
If you can only do one first, do the project.
The order that works
- Pick one role and stop applying to all four
- Build one delivery project and run the sprints properly
- Rehearse the blocker story until it survives a week without rehearsal
- Rewrite the CV in delivery vocabulary, with the project above employment
- Sit the certification
- Apply in volume, because twelve applications is not a sample and sixty is
The loop does not break because you found the magic phrase. It breaks because you turn up with something concrete and answer questions like somebody who has thought about the work.
If you would rather not build the board from scratch
The Portfolio Project Kit is a complete agile delivery project you import into your own Jira in one click. Four epics, twelve user stories, one impediment, three sprints, 56 story points, with full Given, When, Then acceptance criteria already written. Every story is labelled by the role it demonstrates, so one board gives you four different interviews.
It is a practice project and you say so every time you present it. See the Portfolio Project Kit, $49
Not sure which of the four you are aiming at?
The Role Fit Diagnostic is sixteen statements. You tick the ones that are true of you now, count your ticks by letter, and read the page for whichever role you already work like. Ten pages, printable, free, about six minutes.