GhostpilotHome · Interview questions · Business Analyst
Business Analyst interview questions
Business analyst interviews look for someone who can find the real need behind a request, and write it down so a team can build it.
What interviewers look for
- Requirements. Getting from a vague ask to clear, testable needs.
- Stakeholders. Handling people who want different things.
- Analysis. Using data and process maps to support decisions.
How the interview usually runs
- Recruiter call.
- Hiring manager interview.
- Case or requirements exercise.
- Stakeholder interview.
Stages vary by company, so ask the recruiter what to expect before you start preparing.
8 Business Analyst interview questions, and how to answer them
1. How do you gather requirements?
What they want to see: Method.
How to answer: Use interviews, observation and workshops, then confirm in writing.
2. A stakeholder keeps changing requirements.
What they want to see: Handling change.
How to answer: Understand why, record changes and show the impact.
3. What makes a good user story?
What they want to see: Practical skill.
How to answer: A clear user, need and benefit, with testable acceptance criteria.
4. Functional or non-functional requirements?
What they want to see: Fundamentals.
How to answer: What it does against how well it does it, with examples.
5. How do you map a process?
What they want to see: Tools.
How to answer: Use BPMN or a simple flow, and find delays and handoffs.
6. How do you prioritise requirements?
What they want to see: Decision making.
How to answer: Use MoSCoW or value against effort, agreed with the business.
7. Describe a time you found the real problem.
What they want to see: Insight.
How to answer: Show the request, what you uncovered and the better solution.
8. How do you use data in your work?
What they want to see: Analytical skill.
How to answer: Give an example using SQL or Excel to test an assumption.
A sample answer
Describe a time you found the real problem.
Sales asked for a new report because deals were slow. Shadowing two reps showed the delay was in approvals, not visibility. Discounts waited days for sign-off. I mapped the process and proposed automatic approval under a set limit. That cut approval time from three days to under a day, and the report was no longer needed.
A made-up example to show the structure. Use your own experience and real numbers.Common mistakes
- Writing down requests without asking why.
- Being vague about your own contribution.
- No example of handling conflict.
- Forgetting acceptance criteria.
Practise this out loud
Run a mock interview for a Business Analyst role. Questions change every time, you answer by voice or typing, and each answer gets a score with feedback.
Frequently asked questions
Do business analysts need SQL?
It's increasingly common and a real advantage, though not always required. Basic querying is worth learning.
How is a business analyst different from a product manager?
A BA usually defines how to solve a known need. A PM owns what to build and why.