Business Analyst interview question
How do you run stakeholder interviews?
Prepare hypotheses and open questions, interview stakeholders separately when power dynamics matter, probe goals, decisions, exceptions and evidence, play back your understanding, and validate contradictions with artifacts or data.
Direct answer
What a strong answer covers
How it works
An interview is prepared with a hypothesis about the stakeholder’s goals and the decisions they make, and a short list of open questions that start with how and what rather than yes-or-no. People are interviewed separately when a manager’s presence would shape answers. The conversation probes for real examples, exceptions, and the evidence behind claims, and the interviewer plays back what they heard to catch misunderstandings on the spot. Afterward, statements are compared across interviews and against data and artefacts; contradictions are not resolved by seniority but taken back to the people involved with the evidence.
Example
Interviews about a reporting tool found that the finance director wanted real-time numbers while the analysts said that the data changed too often to be trusted before month-end close. Reviewing actual query logs showed the director opened the report once a month, so the real need was a reliable closed figure with a clear as-of date, not real-time data, which reframed the whole project.
Common mistakes
- Asking leading questions that confirm the solution already chosen.
- Interviewing only managers and never the people who do the work.
- Taking every statement as fact without checking it against artefacts or data.
A useful answer structure
Answer from your own work.
Do not memorise a script: use only examples you can explain honestly in follow-up questions.
Open the desktop workspace and rehearse a clear answer in your own words.