Business Intelligence Developer
Tell me about a time stakeholders kept changing what they wanted mid-project. How did you keep it on track?
What the interviewer is looking for
- This question tests requirements gathering. Asks about decisions, audiences and definitions before building, and manages scope changes openly.
- What to bring out: Shows early prototypes, agrees scope and priorities, explains trade-offs on time, and delivers in increments.
- Expect a follow-up like: How do you say no to a change without damaging the relationship?
Another way it may be asked: Halfway through building a dashboard, the requirements change for the third time. What do you do?
A structure to follow: STAR, with the weight on Action and Result
- Step 1
Situation
One or two sentences: where, when and what was at stake. Pick a real example you were close to.
- Step 2
Task
What you personally were responsible for. Say "I", not only "we", so the requirements gathering you showed is visible.
- Step 3
Action
The two or three things you did and why you chose them over the alternatives. This should be about half your answer.
- Step 4
Result
What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.
This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.
Common slips
- Describing what the team did without saying what you did.
- Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
- Ending on the action and skipping the result and what you learned.
How to practise it
Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.
Related questions
- A manager asks for a dashboard showing sales performance. What questions would you ask before building anything?
- What is a star schema, and why do BI tools tend to work well with it?
- How would you write a query to find each customer's most recent order?
- Tell me about a report you built in Power BI, Tableau or a similar tool that you're proud of. What made it work for its users?
- Two dashboards show different revenue numbers for the same month. How do you track down why and fix it for good?