What does a business analyst do?
A business analyst studies how an organization works, finds what needs to change, and writes requirements a team can deliver. The International Institute of Business Analysis says business analysis "is the practice of enabling change in an organizational context," by defining needs and recommending solutions "that deliver value to stakeholders."
IIBA's page on what business analysis is says analysts help "identify and articulate the need for change in how organizations work." It calls its BABOK Guide "the standard for the practice of business analysis," covering six core knowledge areas.
O*NET OnLine lists "Business Analyst" as a reported job title in two profiles. Under Management Analysts (13-1111.00), tasks include gathering and organizing "information on problems or procedures" and interviewing personnel and observing work on site. Under Business Intelligence Analysts (15-2051.01), the tasks lean toward reports, dashboards and data. Read the posting to see which kind of analyst the employer wants.
The Bureau of Labor Statistics page for management analysts gives a median annual wage of $101,860 in May 2025 and projects employment to grow 10 percent from 2025 to 2035. In Canada, Job Bank lists business data analyst under NOC 21221, with a national median of $45.13 an hour, updated November 19, 2025.
How were these business analyst questions chosen?
They come from the duties in the BLS and O*NET profiles, matched to the question each duty tends to produce. They are drawn from the job's published duties, not from a survey of real interviews. Nothing here claims to be the most asked list, or to show what a named employer asks.
| Duty (BLS and O*NET) | Question it tends to produce | What the interviewer is checking |
|---|---|---|
| Gather and organize information on problems or procedures | "How do you gather requirements?" | A mix of methods, and checking what you heard |
| Interview personnel and observe work on site | "Tell me about a stakeholder who was hard to get time with" | Patience, preparation and other ways to learn |
| Analyze data and develop solutions or alternatives | "Walk me through how you compared options" | Clear criteria and evidence for the choice |
| Document findings and prepare recommendations | "Show me how you'd write this requirement" | Plain, testable wording |
| Make recommendations through presentations or reports | "How would you present this to executives?" | One main point and a clear decision to ask for |
| Confer with managers to ensure changes are working | "How do you know a change succeeded?" | A measure set before the change, then checked after |
Which behavioral questions should you expect?
Behavioral questions ask for real stories, told in STAR order: situation, task, action, result. Interviewers listen for how you found the real need behind a request, how you handled people who disagreed, and whether the change worked. Keep the focus on your part, and name the measure you used to judge the result.
The STAR method guide covers the structure. The page on influence without authority fits many analyst stories, because you usually guide people who do not report to you.
1. Tell me about a time the stated requirement was not the real need.
What they listen for: the questions you asked, what you found, and how you brought the requester along.
Made-up example answer. Situation: a finance team asked for a new report that copied an old spreadsheet with 30 columns. Task: I was the analyst asked to write the requirements. Action: I sat with two people from the team for an afternoon and watched how they used the spreadsheet, and found they only used six columns to decide which invoices to chase. Result: we built a short list of overdue invoices instead of the full report, and after the first month the team lead asked us to retire the old spreadsheet.
2. Describe a time two stakeholders wanted different things.
What they listen for: getting both views written down, tying them to the project's goal, and bringing the choice to the person who owns it. The page on competing priorities covers a related question.
3. Tell me about a requirement you got wrong.
What they listen for: how it was found, what it cost, and what you changed in how you write or check requirements.
4. Tell me about a process you improved.
What they listen for: how you mapped the current process, what you measured before, and what changed after.
What role-specific business analyst questions come up?
Role-specific questions test the tools of the job: gathering requirements, writing them, modelling processes and checking that a change worked. Interviewers want to hear you pick a technique for a reason and explain it in plain words. Naming many techniques without saying when you would use each tends to fall flat.
5. How do you gather requirements?
What they listen for: more than one method, such as interviews, workshops, observation and reading existing documents, and a way to confirm what you heard. BLS lists interviewing personnel and onsite observation among the duties of management analysts.
6. Write a user story for this feature.
What they listen for: a user, a need and a reason, plus acceptance criteria that can be tested. The Agile Alliance user stories glossary says teams divide work into "functional increments called 'user stories,'" and that "a user story is not a document; the term encompasses all of the knowledge required."
Made-up example answer: "As a store manager, I want to see which items are below their reorder level each morning, so that I can place orders before we run out. Acceptance criteria: the list shows only items below their reorder level, it updates by 7 a.m., and each line shows the item, the stock on hand and the reorder level. I'd confirm the reorder levels with the inventory team before we start."
7. What is the difference between a functional and a non-functional requirement?
What they listen for: functional requirements describe what the system does, such as calculating a refund. Non-functional ones describe how well it does it, such as speed, security or availability. Give one example of each.
8. How would you map a current process?
What they listen for: who does each step, what triggers it, what goes in and out, and where delays or rework happen. Mention checking the map with the people who do the work.
9. How do you decide which requirements come first?
What they listen for: a rule tied to business value, risk and dependencies, agreed with the product owner or sponsor.
Which situational questions test judgment?
Situational questions describe a problem and ask what you would do first. Interviewers look for an order: learn the facts, talk to the people affected, lay out options, then get a decision from the right person. Asking what problem the business is trying to solve is often the strongest first move.
The guide to situational interview questions explains the format.
10. Halfway through a project, a sponsor asks for a large new feature.
What they listen for: writing the request down, estimating its effect on scope, time and cost, and bringing it through the agreed change process.
Made-up example answer: "I'd thank the sponsor and ask what problem the new feature solves, because that tells me how urgent it is. Then I'd work with the project manager and the team to estimate what it would add in time and cost. I'd bring the options back in writing: add it now and move the date, swap it for something lower in priority, or plan it for the next release. The sponsor decides, and I'd update the requirements the same day."
11. Developers say a requirement you wrote is unclear.
What they listen for: thanking them, meeting quickly, rewriting it with examples, and checking the new version with the business.
12. Users reject a system that met every written requirement.
What they listen for: going back to users to learn what is missing, and owning any gap in how the requirements were gathered.
What follow-up questions tend to come next?
Follow-ups test whether your story holds up under detail. Expect the interviewer to ask how you confirmed a requirement, who signed off, or what you would do if a stakeholder never replied. Prepare by noting the people, documents and measures in each story so you can answer without guessing.
- "How did you check that you understood the need correctly?"
- "Who signed off on the requirements?"
- "How did you measure whether the change worked?"
- "What would you do differently now?"
How should you prepare for a business analyst interview?
Pick four or five projects and write a STAR story for each, including one where the requirement changed. Practise writing a user story and acceptance criteria for a common task in under five minutes. Read the posting closely to see whether it leans toward process and requirements or toward data and reports, and prepare for that side first.
The free interview question generator lets you paste the job and pick the round, and it returns likely questions, why they come up, and what the interviewer listens for. Analysts often work beside the roles on the data analyst, project manager and product manager pages, and those questions overlap with yours.
If you are moving into analysis from another field, the guide to a career change resume shows how to present related work. Prept's Mock room lets you answer out loud on a clock, scores each answer out of 10 and checks it against your resume, and it is included in the free plan.