Business analyst interview questions and how to answer them
Questions on the skills open business analyst listings mention and on the core work of the role. For each: what the interviewer is checking, and a STAR answer outline with placeholders for your own example.
Based on 55 open business analyst listings on ROLIVA as of . Each question below is about a term from ROLIVA’s skills vocabulary that appears in at least two of these listings, most-mentioned first.
01 Walk me through a SQL query you wrote that answered a real question. How did you know the result was right?
Why this question: SQL is mentioned in 29 of 55 listings.
What the interviewer is checking. Whether you can turn a question into joins, filters and aggregations, and whether you check your own output instead of trusting the first number the query returns.
Answer outline (STAR)
Situation.[The question someone needed answered and the tables or data sources involved, e.g. orders joined to customers].
Task.[What you had to produce, for whom, and by when].
Action.[How you built the query: the joins, filters and grouping you chose, and how you checked it, e.g. row counts, a hand-checked sample or a comparison with a known total].
Result.[What the answer showed and what was decided because of it]. If there is no number you can support, say what changed as a result or what you learned.
02 Tell me about something you built or automated in Python that other people relied on. What would you do differently now?
Why this question: Python is mentioned in 17 of 55 listings.
What the interviewer is checking. Whether you write Python that works beyond your own laptop: structure, error handling, tests or checks, and whether you can judge your earlier work honestly.
Answer outline (STAR)
Situation.[The task or problem, and who depended on the script, notebook or service].
Task.[What it had to do and any constraint, e.g. data size, run frequency or a deadline].
Action.[The approach and libraries you used, how you handled failures or bad input, and how you tested it].
Result.[What it replaced or made possible, and the one thing you would change today]. If there is no number you can support, say what changed as a result or what you learned.
03 Tell me about a time an Agile way of working was not helping your team. What did you change?
Why this question: Agile is mentioned in 13 of 55 listings.
What the interviewer is checking. Whether you understand the purpose behind Agile practices and adapt them to the team, rather than following ceremonies for their own sake.
Answer outline (STAR)
Situation.[The team and the practice that was not working, e.g. planning that never matched delivery].
Task.[What you were responsible for or chose to take on].
Action.[What you noticed, what you proposed, and how the team agreed to try it].
Result.[What changed in delivery or in how the team worked]. If there is no number you can support, say what changed as a result or what you learned.
04 Show me how you would explain a Tableau dashboard you built: who it was for and what it changed.
Why this question: Tableau is mentioned in 13 of 55 listings.
What the interviewer is checking. Whether you design dashboards around a question and an audience rather than around the data available, and whether you know if anyone used it.
Answer outline (STAR)
Situation.[The audience and the question they kept asking, e.g. weekly performance by region].
Task.[What the dashboard had to answer and the data source behind it].
Action.[The views, filters and calculated fields you chose, what you left out, and how you validated the numbers against the source].
Result.[How it was used, e.g. replaced a manual report or changed a weekly meeting]. If there is no number you can support, say what changed as a result or what you learned.
05 How have you used Jira to keep a piece of work visible and on track? Tell me about a time the board did not match reality.
Why this question: Jira is mentioned in 10 of 55 listings.
What the interviewer is checking. Whether you use the tool to support delivery rather than for its own sake, and whether you notice and fix it when tickets drift from the real state of the work.
Answer outline (STAR)
Situation.[The team, the work and how it was tracked in Jira].
Task.[What went wrong or what you were responsible for, e.g. a board everyone had stopped trusting].
Action.[What you changed, e.g. clearer ticket definitions, a workflow fix or a regular review, and how you got the team to adopt it].
Result.[Whether status became reliable and what decisions it supported]. If there is no number you can support, say what changed as a result or what you learned.
06 Tell me about a time you used or changed Salesforce to improve how a team worked. How did you make sure people used it correctly?
Why this question: Salesforce is mentioned in 10 of 55 listings.
What the interviewer is checking. Whether you understand the CRM as a shared record that others depend on, and whether you think about data quality and adoption, not just configuration.
Answer outline (STAR)
Situation.[The team and the process in Salesforce, e.g. opportunity stages or case handling].
Task.[The problem, e.g. inconsistent data or a step people skipped].
Action.[What you changed or how you used it, e.g. a field, a report or a validation rule, and how you trained or persuaded people].
Result.[What became more accurate or visible, and how you checked]. If there is no number you can support, say what changed as a result or what you learned.
07 Describe a spreadsheet you built that people used to make a decision. How did you stop it from giving a wrong answer?
Why this question: Excel is mentioned in 8 of 55 listings.
What the interviewer is checking. Whether you can build a model or analysis others can follow, and whether you control errors: clear inputs, consistent formulas and checks against known figures.
Answer outline (STAR)
Situation.[The decision, the people making it and the data the spreadsheet held].
Task.[What the spreadsheet had to calculate or show, and how often it would be updated].
Action.[How you structured it, e.g. separate input and calculation sheets, lookups or pivot tables, and the checks you added].
Result.[The decision it informed and any error you caught before it mattered]. If there is no number you can support, say what changed as a result or what you learned.
08 Tell me about a stakeholder who disagreed with you or your team. How did you handle it?
Why this question: Stakeholder management is mentioned in 8 of 55 listings.
What the interviewer is checking. Whether you can understand another person’s interests, disagree constructively, and reach a decision without damaging the relationship.
Answer outline (STAR)
Situation.[The stakeholder’s role, what they wanted and why it conflicted with the plan].
Task.[What you were responsible for deciding or delivering].
Action.[How you understood their concern, the options you put forward, and how the decision was made].
Result.[The outcome and the state of the relationship afterwards]. If there is no number you can support, say what changed as a result or what you learned.
Questions about the core work of a business analyst
These follow from the work the role title describes, not from a count of listings.
09 Tell me about a time stakeholders gave you conflicting requirements. How did you resolve them?
What the interviewer is checking. Your elicitation skills, how you bring underlying needs to the surface, and whether you can lead people to an agreed requirement rather than writing down both versions.
Answer outline (STAR)
Situation. Describe the project and the two conflicting requirements: [who wanted what, and why].
Task. Say what you had to produce: [e.g. a signed-off requirement or a single process design].
Action. Explain how you got to the real need [the questions you asked, a workshop you ran, a process map or data you used] and how you got agreement [the decision maker and the record of the decision].
Result. Give a result you can support [what was built and whether it met both needs]. If one side was not satisfied, say how you handled that openly.
10 Walk me through how you analysed a current process and recommended changes.
What the interviewer is checking. Whether you can map an as-is process accurately, find the real cause of problems, and back your recommendations with evidence.
Answer outline (STAR)
Situation. Describe the process and the problem: [e.g. delays, errors or rework, and who reported it].
Task. State your task: [e.g. recommend changes and a to-be process].
Action. Explain your analysis [how you gathered information, such as interviews, observation or system data; how you mapped the process; the causes you found] and your recommendation [the main changes and their trade-offs].
Result. Share a result you can support [e.g. a measured reduction in handling time or errors]. If the change was not implemented, say what decision it informed.
11 Describe a time a requirement you wrote was misunderstood by the delivery team.
What the interviewer is checking. Honesty about your own part in the misunderstanding and how you improved the clarity of your requirements afterwards.
Answer outline (STAR)
Situation. Describe the requirement and the misunderstanding: [what you wrote, and what was built or tested instead].
Task. Say what you were responsible for: [the requirement document, acceptance criteria or sign-off].
Action. Explain what you did [how you found the gap, how you corrected it with the team, and what you changed in how you write requirements, e.g. examples, diagrams or walkthroughs].
Result. Give the result you can support [the fix and its cost or delay]. If you cannot measure it, say what changed in later work.
12 How do you decide whether a stakeholder request is a real business need or a solution in disguise?
What the interviewer is checking. Your ability to separate problems from proposed solutions and to challenge politely, which is central to the analyst role.
Answer outline (STAR)
Situation. Describe the request: [who asked and the solution they asked for, e.g. "a new report" or "a new field"].
Task. State what you needed to find out: [the problem behind the request and its business value].
Action. Explain how you questioned it [the questions you asked, data you checked, alternatives you considered] and what you recommended [the option and why].
Result. Share the result you can support [what was delivered and whether it solved the underlying problem]. If the stakeholder kept their original request, say how you documented the risk.
Using the outlines
One real example per answer. Replace every [bracketed] part with something you did and can talk about in detail.
Keep the situation short. Spend most of the answer on what you did and why.
Say “I” for your part. Name the team’s work as the team’s, and your own decisions as yours.
Results you can support. If there is no number, say what changed or what you learned. Never estimate a figure you cannot back up.
How these questions are chosen
Each open business analyst listing’s description and stated skills are checked, on whole words, against the fixed skills vocabulary ROLIVA uses on its job pages, resume examples and monthly skills reports. A listing counts once per term. A mention is not a requirement, and the counts change as employers open and close roles. The questions and outlines are preparation prompts written for this role. They are not a record of what any employer has asked, and no employer’s process is described here.
Interview Studio prepares questions and STAR outlines for a real job from its description and the experience you have confirmed. No generative AI: when a detail is missing, it asks you instead of inventing one.