Interview Insights · Business Analyst
What I Wish Every Business Analyst Candidate Knew Before Walking In
Quick summary — BA interview prep
A BA interview is less a test of what you have memorised and more a test of how you think when things are unclear. If I could tell every BA candidate a few things before they walked in, they would be these. The rounds test different things, so prepare for each. Definitions are only the entry ticket; applying them is what counts. Case questions reward structure and honesty, not a perfect answer. And the manager round is about trust: whether you can handle pushback, scope changes and difficult stakeholders. None of this is secret, but most candidates discover it in the room.
In this guide you will learn:
- What each BA interview round is really testing
- The core concepts you must be able to apply, not just define
- How to approach a case question you have never seen
- Stories to prepare for the manager round
- A day-before checklist and good questions to ask at the end
SECTION 01Know what each round is actually testing
Company processes differ, but most BA hiring follows a similar shape: a screening call, a concepts or technical round, a case or scenario round, and a final conversation with the hiring manager. Candidates often prepare for all of them as if they were the concepts round, memorising definitions and frameworks.
Each round has a different purpose. Screening checks fit and communication. Concepts check whether you can apply BA basics. The case checks judgement under ambiguity. The manager checks whether they would trust you with their stakeholders.
| Round | What it really tests | Typical question | How to prepare |
|---|---|---|---|
| Screening call | Clarity, motivation, basic fit | Why do you want to be a BA? | A 60-second answer linking your background to BA work |
| Concepts / technical | Can you apply BA basics? | Write a user story with acceptance criteria for X | Practise writing, not just defining |
| Case / scenario | Judgement with incomplete information | Why might online returns be rising? | Clarify, assume, structure, recommend |
| Hiring manager | Trust with stakeholders and scope | Tell me about a time you pushed back | Two or three real, specific stories |
"I want to be a Business Analyst because it is a good
career with growth. I have good communication skills and
I like analysing things. BA is a bridge between business
and IT, so I think it suits me."
Problem: every sentence could come from any candidate.
Nothing links to the person's own background."In my final-year internship at a logistics company, I
was asked to track delayed shipments in Excel. I noticed
the delays were mostly caused by one manual hand-off
between the warehouse and dispatch, and I enjoyed
explaining that to the team lead more than building the
sheet itself.
That is when I realised I like understanding why a
process fails and helping people agree on a fix. Since
then I have trained in process mapping, user stories and
SQL, and I want to do that work full time."The strong answer is short, personal and points to real BA activity. It also gives the screener a natural follow-up: 'tell me more about that hand-off'. That is exactly the kind of question you want.
SECTION 02Concepts you must apply, not just define
Knowing that a user story follows 'As a, I want, so that' is the entry ticket. What the concepts round actually asks is whether you can write a good one, split a large one, spot a bad one and write acceptance criteria for it. The same applies to use cases, MoSCoW, UAT and basic SQL.
Before you walk in, take each core concept and practise one applied task with it. The table below lists the ones I see asked most often, with the kind of task that follows the definition.
| Concept | Definition question | Applied follow-up | Common slip |
|---|---|---|---|
| User story | What is a user story? | Split 'As a user I want to manage my account' | Stories too big or with no 'so that' |
| Acceptance criteria | Why do we need them? | Write criteria for a password reset | Criteria that cannot be tested |
| Use case vs user story | What is the difference? | Turn a use case into two stories | Saying they are the same thing |
| SQL basics | What does GROUP BY do? | Count orders per city above 100 | Using WHERE instead of HAVING on counts |
Too big:
As a user, I want to manage my account.
Split by action:
1. As a user, I want to change my phone number,
so that OTPs reach my new number.
2. As a user, I want to change my password,
so that I can secure my account if I suspect misuse.
3. As a user, I want to download my order history,
so that I can keep records for expense claims.
Acceptance criteria for story 1:
- Given I enter a new number, when I submit,
then an OTP is sent to the new number.
- Given the OTP is correct, then the number is updated
and a confirmation is sent to the old number.
- Given the OTP is wrong 3 times, then changes are
blocked for 30 minutes.-- Cities with more than 100 orders in 2025
SELECT city, COUNT(*) AS orders
FROM orders
WHERE order_date >= '2025-01-01'
AND order_date < '2026-01-01' -- filters ROWS
GROUP BY city
HAVING COUNT(*) > 100 -- filters GROUPS
ORDER BY orders DESC;
-- Common slip: WHERE COUNT(*) > 100
-- This fails because WHERE runs before grouping,
-- so the count does not exist yet.Notice that the split stories each have a different 'so that'. That is a quick test of quality: if two stories share exactly the same benefit, they might be one story, or the benefit might be too vague.
SECTION 03Case questions and manager stories: what calm preparation looks like
The case round worries candidates most, because they cannot predict the question. You do not need to. You need a method you can apply to any vague problem: clarify one or two things, state assumptions, break the problem into parts, and recommend a next step. Interviewers are watching the method more than the conclusion.
The manager round is more predictable. It nearly always asks about conflict, pushback, mistakes and changing priorities. Prepare real, specific stories from internships, college projects, part-time jobs or training cases, and practise telling them in under two minutes.
| Situation | Case or story | Structure to use | What to avoid |
|---|---|---|---|
| Vague business problem | Why are online returns rising? | Clarify, split into causes, check data, recommend | Jumping to one cause without evidence |
| Disagreement | A stakeholder rejected your proposal | Situation, what each side wanted, how you resolved it | Making the other person look foolish |
| Your mistake | You missed a requirement | What happened, how you found it, what you changed | Blaming the team or the client |
| Changing priorities | Scope changed late in a sprint | Impact check, options, who decided, outcome | Saying you just worked extra hours |
Q: Online returns for our clothing site are rising.
Why might that be?
1. Clarify
- Rising since when? All categories or some?
Assume: last two months, mostly in one category.
2. Possible causes, grouped
- Product: size charts wrong, quality issue
- Expectation: photos misleading, description unclear
- Process: easier return policy, wrong items shipped
- Customer: a new customer segment, festive gifting
3. Data to check
- Return reasons by category and month
- Returns by size and by supplier
- Any policy or site change two months ago
4. Recommendation
- Start with return reasons in the rising category;
if 'size' dominates, review that category's
size chart first, as it is cheapest to fix."In a training case, I wrote user stories for a clinic
booking system and missed that some patients book for
family members.
During a review, the trainer acting as front desk asked
how a mother would book for her child. My stories had no
answer.
I added a 'book for someone else' story, updated the
acceptance criteria and the data fields, and since then
I always ask 'who else might use this on someone's
behalf?' in the first requirement session."The mistake story is honest about being a training case, admits a real gap and ends with a changed habit. That last line is what the manager remembers, because it tells them how you will behave on their team.
SECTION 04Your day-before kit for a BA interview
Use these three tabs the evening before. The checklist covers logistics and materials, the warm-up gets your thinking moving, and the end-of-interview questions help you finish strongly.
MATERIALS
[ ] Resume printed (2 copies) or PDF ready to share
[ ] One-page project summary you can show
[ ] Pen and a few sheets of paper for case questions
[ ] Notes on the company: product, users, domain
STORIES (say each aloud once)
[ ] Why BA, in 60 seconds
[ ] Project walkthrough, in 3 minutes
[ ] A disagreement and how it was resolved
[ ] A mistake and what you changed
LOGISTICS
[ ] Route or video link tested
[ ] Laptop charged, camera and mic checked
[ ] Water, ID, and arrive or log in 10 minutes early15 minutes before you leave or log in:
1. Write one user story with three acceptance
criteria for any app on your phone. (4 min)
2. Write one SQL query from memory: count orders by
city with HAVING. (3 min)
3. Pick a random problem ('the metro is crowded')
and say aloud: clarify, causes, data, next step.
(5 min)
4. Say your 'why BA' answer once, slowly. (3 min)
Goal: your brain is already in BA mode when the
first question arrives.Pick two. Ask the ones you genuinely want answered.
- What kind of requests reach the BA team most often?
- How do BAs and developers work together here day
to day: stories in Jira, workshops, both?
- What would a new BA be expected to own in the first
few months?
- How are requirements signed off, and who signs?
- What separates a good BA from a great one on this
team?
Avoid asking only about leave, timings and salary in
the technical rounds. Those belong in the HR stage.SECTION 05Small things that make a big difference in the room
These are details candidates often overlook, and interviewers notice.
- Bring paper and use it — Sketching a quick process or listing causes during a case question shows structure and gives you time to think visibly.
- Say when you are assuming — Phrases like 'I will assume this is for first-time customers' keep your answer honest and let the interviewer redirect you.
- Know the company's users — Spend twenty minutes on the product before the interview so you can give examples from their world, not a generic app.
- Keep answers to two minutes — Long answers bury your best point. Make it, give one example and stop, so the interviewer can ask what interests them.
- Thank and summarise at the end — A one-line summary of why you fit the role is a calm, confident way to close the conversation.
SECTION 06Interview Q&A — BA interview prep
Q1What are the rounds in a business analyst interview?
It varies by company, but a common pattern is a screening call, a concepts or technical round on stories, requirements, Agile and basic SQL, a case or scenario round, and a hiring manager round on stakeholders, conflict and scope. Some add an HR discussion at the end.
Q2What is the difference between a use case and a user story?
A use case describes the full interaction between an actor and a system, including main and alternate flows. A user story is a short statement of a need from a user's view, with acceptance criteria, used for planning in Agile. One use case can become several user stories.
Q3How should I answer a case question I have never seen?
Clarify one or two points, state your assumptions, break the problem into possible causes or parts, say what data you would check, and recommend a sensible first step. Think aloud so the interviewer can follow your method.
Q4Why do you want to be a business analyst?
Give a short, personal answer linked to something you actually did. For example, a time you found why a process was failing and helped people agree on a fix, followed by the training you have done since. Avoid generic lines about growth or being a bridge.
Q5What SQL should a fresher BA know for interviews?
SELECT with WHERE, ORDER BY, GROUP BY with COUNT, SUM and AVG, HAVING, simple JOINs and CASE. Be able to explain why you would use each for a business question, such as counting orders by city or comparing periods.
SECTION 07Test yourself — BA interview prep quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
How do I prepare for a business analyst interview as a fresher?
Prepare a personal 'why BA' answer, practise applying core concepts like user stories and acceptance criteria, learn basic SQL, rehearse a case method, and prepare two or three real stories from internships, college or training projects.
What should I bring to a business analyst interview?
Copies of your resume, a one-page summary of your main project, a pen and paper for case questions, and notes on the company's product and users. For video interviews, keep the files ready to share on screen.
What are common business analyst interview questions?
Expect questions on user stories, acceptance criteria, use cases, requirement gathering techniques, Agile ceremonies, UAT, prioritisation methods, basic SQL, a case scenario, and behavioural questions about conflict and mistakes.
Do business analyst interviews include SQL tests?
Many do, especially for data-focused BA roles. Expect simple queries with GROUP BY, HAVING, JOIN and CASE. Even when SQL is not tested formally, being able to describe a query you would use is a strong signal.
What questions should I ask at the end of a BA interview?
Ask about the work: the kinds of requests the BA team handles, how BAs work with developers, what a new BA would own early on, and how requirements are signed off. Save policy questions for the HR discussion.
Does Uncodemy help with Business Analyst interview answers?
Yes. Uncodemy's Business Analyst Training Course in Noida (classroom and online) includes live projects, one-to-one mock interviews and resume reviews, so you practise Business Analyst interview answers with trainer feedback before the real interview. You can book a free demo class from this page to see how the sessions work.
SECTION 09Related reads
Classroom & online · Noida
Walk into your BA interview prepared
Our Business Analyst Training Course covers requirements, user stories, UAT, SQL and case practice, with mock interviews for every round so nothing in the room feels new.
Talk to a counsellor for current fees- Round-by-round mock interviews
- User stories & UAT practice
- SQL for Business Analysts
- Case question drills