Every entry level business analyst job advert asks for two to three years of business analysis experience. This is not a mistake, and it is not going to stop. What it actually means is worth understanding, because the gap between what the advert says and what the hiring manager will accept is where your whole route in sits.
What “entry level” actually means in this field
Business analysis is rarely a graduate role. Most people arrive at it sideways, in their late twenties to early forties, from operations, healthcare, finance, legal, teaching or customer facing work. The job is about understanding how an organisation works and translating that into something a delivery team can build. That is hard to do at twenty two and much easier to do at thirty four with a decade of watching processes fail.
So when an advert says entry level, it usually means entry level to business analysis, not entry level to working life. The two to three years it asks for is a proxy for something the writer could not express: can you sit in a room with a stakeholder who does not know what they want, and leave with something specific enough to build.
That is the bar. It is not a number of years.
The four things that actually get people hired without a BA job title
One, a project you can be cross examined on. Not a certificate, not a course completion, a project. Something with requirements you wrote, acceptance criteria you can defend, a decision you got wrong and changed. Interviewers stop testing your knowledge the moment you can describe real work, even practice work, in specific terms. The specificity is what does it.
Two, evidence you have done the job under another name. Most people applying for a first business analyst role have already done parts of it. If you have ever written a process down so someone else could follow it, gathered requirements from people who disagreed with each other, or built a spreadsheet that became the way a team worked, that is business analysis. It was just not called that. The work is in recognising it and describing it in the vocabulary the hiring manager uses.
Three, the ability to ask a good question in the interview. This sounds soft and it is the most reliable signal there is. A business analyst who asks no questions is a business analyst who will write down whatever the loudest stakeholder said. Interviewers notice.
Four, a target that is narrow enough to be credible. Applying to every business analyst role in the country reads as desperation. Applying to business analyst roles in healthcare, when you spent eleven years in a hospital, reads as a plan.
The routes in, ranked honestly
Internal move. Far and away the best odds, and the one people dismiss because it feels slow. If you already work somewhere with a delivery team, you have something no external candidate has, which is domain knowledge and a track record the hiring manager can check. The switch costs are near zero for them. If this route is open to you at all, it is worth six months of positioning.
Adjacent role first. Project coordinator, delivery support, product support, operations analyst. These sit next to the work, and after a year the title change is a conversation rather than a leap. Slower than it sounds on paper and more reliable than applying cold.
Smaller company, broader role. A company of forty people will hire someone who can do most of the job and learn the rest, because they need the work done. A company of four thousand has a competency framework and will not. Your odds are meaningfully better below a hundred employees.
Contract and agency. Worth knowing about, rarely worth starting with. Contractors are hired to be immediately productive, which is the one thing a career changer cannot offer yet.
Cold applications to large companies. This is where almost everyone spends their effort and where almost nobody gets in without one of the four things above. Not impossible. Just the hardest door in the building.
What does not work, said plainly
A certification on its own does not work. It will get your CV past a filter in some organisations and it will not survive the first interview if there is nothing behind it. Certifications are a supplement to evidence, not a substitute for it.
A course completion certificate is not a project. Watching someone else analyse a case study does not put anything on your CV that you can be questioned about.
And describing a practice project as though it were paid work does not work, beyond the short term. It falls apart under two follow up questions, and the interviewer who catches it is the one who would otherwise have hired you. Say it is practice, in one sentence, every time. Delivered calmly it is one of the more credible things you can say, because almost nobody volunteers the limits of their own evidence.
A realistic timeline
For someone working full time and putting in three to four hours a week: about a month to build a project worth talking about, another month to rewrite the CV and profile around it and start applying, and then a hiring process that typically runs six to twelve weeks from first application to offer in this field. Three to six months, in other words, if you are targeting properly.
People who apply widely with an unchanged CV and no project are often still applying a year later. The difference is almost never talent. It is whether there is anything specific to talk about.
Where to start this week
Pick the role before you pick anything else. Business analyst, scrum master, product owner and agile project manager look interchangeable in job adverts and are not, and an interviewer can tell within two questions which one you have actually thought about. The Role Fit Diagnostic takes about six minutes and is free.
Then build the project. The portfolio project guide covers what to build and how to present it honestly.