Business analyst interviews are structured around four things: requirements writing, stakeholder communication, analytical thinking, and domain knowledge. Hiring managers test them roughly in that order of importance. The good news for career changers is that domain knowledge — the area most people worry about — is actually the easiest one to leverage from a previous career.
How career changers should frame their experience
Your previous industry is an asset, not a gap. A former nurse who moves into BA work for a healthcare software company brings clinical knowledge that a career BA would take years to acquire. A former logistics coordinator who joins a supply chain tech firm understands the domain better than any recent graduate. Lead with that domain knowledge in your interview, then show that you can translate it into requirements. The translation skill is what the interview is really testing — the domain knowledge is what makes you worth hiring over everyone else.
Three exercises to practice before any BA interview
First, write a use case for a feature you already know well. Pick any software you have used in a previous job and write a formal use case for one of its core workflows. This shows you understand requirements structure. Second, create a process flow for something from your previous job. Map a business process you lived in — approvals, patient intake, order fulfillment — as a swimlane diagram. This demonstrates process thinking. Third, prepare a specific, detailed answer to the question: "How would you elicit requirements from a stubborn stakeholder?" This comes up in almost every BA interview. Your answer should include the specific technique you would use (active listening, structured workshops, shadowing) and a real example of dealing with resistance — even if that example is from a non-tech context.
The most common BA interview mistake
Being too vague about how you have done things. Candidates say "I worked with stakeholders to gather requirements" and stop there. Hiring managers want specifics: which stakeholders, what method, what happened when they disagreed, how you resolved it. Specifics win interviews. Generalities lose them. Every answer should have a concrete "how" inside it.
On the certification question
If asked about certifications, CBAP (Certified Business Analysis Professional) is the gold standard, but it requires documented work experience and is not accessible to entry-level candidates. ECBA (Entry Certificate in Business Analysis) is the right starting point — it has no experience prerequisite and signals commitment to the profession. If asked, say you plan to sit the ECBA within six months of your first role. That answer is credible, forward-looking, and shows you know the certification landscape.