Four job titles. From outside they look like the same job with four names, and the adverts do not help, because half of them are written by someone who was handed a template.
They are not the same job. An interviewer can tell within two questions which one you have actually thought about, and most career changers apply to all four and sound convincing in none.
Here is the honest version, written for someone coming in from nursing, teaching, law, retail or admin rather than from another tech job.
The one sentence version
The business analyst works out what should be built and writes it down so precisely that somebody else can build it. The product owner decides what gets built first and what waits. The scrum master makes it possible for the team to actually do the work. The agile project manager holds the whole delivery together across teams, dates and dependencies.
Everything below is detail on those four sentences.
Business analyst: a Tuesday
You spend the morning with somebody from the finance team who says they need a report. You spend forty minutes working out that they do not need a report, they need to stop being asked the same question every Thursday, and a report is just the first solution they thought of.
Then you write it down. Not a summary. A specification precise enough that a developer who has never met that finance person can build the right thing, including what happens when the data is missing, when two records match, when somebody enters a date in the wrong format.
The work is turning a vague human problem into something unambiguous.
What transfers: anything where you had to ask careful questions and write the answer down in a way that survived being read by somebody else. Care plans. Case files. Incident reports. Process documentation nobody asked you to write but everybody uses.
What the interview probes: they will ask you to walk through one requirement. Not a project, one requirement. If you describe a feature rather than the reasoning behind a decision, they will know.
Product owner: a Tuesday
Two people want two different things and there is room for one. You decide. Then you explain the decision to the person who did not get their thing, in a way that keeps them willing to talk to you next month.
The rest of the day is protecting the order of the work from whoever shouted most recently.
This is the role people underestimate. It looks like writing a list. It is actually saying no, repeatedly, with reasons, to people who outrank you.
What transfers: triage. Deciding what gets attention when everything is presented to you as urgent. If you have run a ward, a classroom, a shop floor or a caseload, you have done the hard part of this job already.
What the interview probes: they will ask how you prioritise. Naming a framework is not the answer. Describing one decision where the cheap easy thing was not first, and why, is the answer.
Scrum master: a Tuesday
Fifteen minutes in the morning where your only real job is finding out what is in the way. Then most of the day spent removing those things, which mostly means talking to people who do not report to you and do not have to help you.
Somebody is blocked waiting on a decision nobody has made. You find out who can make it, get it in writing, and say out loud what it costs if it does not come by Friday.
The bad version of this role is a person who runs meetings on a schedule and reports problems upwards. The good version removes things.
What transfers: influence without authority. Coordinating people who do not work for you, chasing the thing everybody assumed somebody else was doing, noticing when a quiet person has stopped contributing.
What the interview probes: one blocker, in detail, with dates. What you did on day two, day five and day eight. If your answer is that you escalated it, that is reporting, not removing, and an experienced interviewer will hear the gap.
Agile project manager: a Tuesday
You are holding three teams, a fixed launch date and a dependency on a vendor who has gone quiet. Your day is spent working out which of those is going to break first and telling somebody about it early enough that they can still do something.
More reporting than the other three. More time spent on the seams between teams than inside any one of them.
What transfers: running something with a hard external deadline that could not move. Court dates. Term dates. Peak trading. Inspection visits.
What the interview probes: a dependency you managed, and how you reported bad news. The tell is whether you said it early with a number attached, or late with an apology.
The honest differences nobody writes down
- The scrum master has the least formal authority and the most influence, which is either satisfying or maddening depending on the person.
- The product owner gets blamed for the roadmap by people who were in the room when it was agreed.
- The business analyst does the most writing by a distance. If you do not enjoy writing precisely, this role will grind you down.
- The agile project manager sits in the most meetings and has the clearest view of whether anything is actually going to land.
- None of the four requires you to write code. Several of the job adverts will imply otherwise. They are usually wrong, and where they are not, the advert says so plainly.
How to tell which one is you
Ignore salary comparisons for a moment, because at entry level across these four the gap is smaller than the internet suggests and it closes further after two years.
Ask instead which of these sounds like a good day.
- Sitting with one person until a fuzzy problem becomes a precise one, then writing it down. That is the business analyst.
- Deciding what matters most this month and defending it. That is the product owner.
- Clearing obstacles for a group of people so they can get on with it. That is the scrum master.
- Seeing the whole thing at once and catching what is about to go wrong. That is the agile project manager.
If two of those sound equally good, that is normal and it is not a problem yet. Pick the one closest to what you already do all day, apply for that one, and keep the second in reserve. Applying for all four with the same CV is the single most common mistake career changers make.
What to do next
Pick one. Then get something concrete you can be questioned on, because every interview question for all four of these roles assumes you have a project to answer from, and that is the real gap rather than the knowledge.
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.