# Business Analyst Interviews: Questions and Preparation Business analysts sit between stakeholders and delivery teams. Interviews test whether you can uncover real requirements, document them clearly, and use data to support decisions. ## Requirements gathering Expect "How do you gather requirements from stakeholders who disagree?" Talk about interviews and workshops, asking "why" until you reach the underlying need, separating must-haves from nice-to-haves, and getting written sign-off. Mention techniques you have used, such as user stories with acceptance criteria, process maps, or use cases. ## Documentation You may be asked to write a user story on the spot. A good one names the user, the goal, and the reason, followed by testable acceptance criteria. Keep language plain so developers and business users read it the same way. ## Process analysis "Walk me through how you would analyze a slow approval process." Map the current state, measure where time is lost, interview the people involved, propose a future state, and estimate the benefit. ## Data skills Many BA roles expect SQL and spreadsheet fluency. Be ready to write a query with joins and grouping, build a pivot table, and explain a chart to a non-technical audience. If you have used a BI tool, describe a dashboard you built and what decision it changed. ## Stakeholder scenarios - "A senior stakeholder adds scope late in the project." - "Developers say a requirement is unclear." - "Your analysis contradicts what the sponsor expected." Show that you stay neutral, rely on evidence, and communicate trade-offs early. ## Questions to ask - Which methodology does the team use? - Who are the main stakeholders for this role? - How are requirements handed off to development? ## Rehearse your examples BA answers work best as specific stories. Practicing them aloud with an [AI interview practice tool](https://www.linkjob.ai/) helps you keep them concise.