Interview questions
Business analyst interview questions for freshers
The business analyst interview checks whether you can sit between two groups who don't speak each other's language — business stakeholders and technical teams — and translate accurately in both directions. Every question below is some version of that test.
Freshers rarely have BA work experience, and interviewers know it. What they're listening for is structured thinking out loud: can you take a fuzzy situation and give it edges? That's a speaking skill, and it improves fastest with spoken practice.
Question 1
What does a business analyst actually do?
Surprisingly effective filter. A crisp version: a BA figures out what a business actually needs, translates it into requirements a technical team can build, and makes sure what ships solves the original problem. If your answer is a list of tools, you've missed it.
Question 2
How would you gather requirements for a new feature?
Name methods — stakeholder interviews, watching current workflows, data analysis, workshops — but lead with intent: understanding the problem before anyone proposes a solution. "I'd ask what they want" is the junior version; "I'd find out what problem they're trying to solve" is the hired version.
Question 3
What's the difference between functional and non-functional requirements?
Functional: what the system does (a user can reset their password). Non-functional: how well it does it (the reset email arrives within a minute). Give paired examples from one feature and the distinction lands instantly.
Question 4
Two stakeholders want contradictory things. What do you do?
The classic BA scenario. Don't pick a side — go up a level: what business outcome is each trying to reach? Often the conflict is between solutions, not goals. Say you'd get the actual decision-maker to prioritize with data, not volume.
Question 5
Estimate the number of food delivery orders in your city per day.
A guesstimate — the answer is your structure, not the number. Population, smartphone share, ordering frequency, stated assumptions, clean arithmetic out loud. Interviewers fail silence and hand-waving, not wrong numbers.
Question 6
What is a user story? Write one for a feature you know.
"As a [user], I want [action], so that [benefit]" — plus acceptance criteria, which is the part that shows real understanding. Pick an app you use daily so the follow-ups are easy ground.
Question 7
How much SQL do you know?
Be precise rather than modest or inflated: "I can join tables, aggregate with GROUP BY, and filter with subqueries — I haven't used window functions in real work yet." Precision about your own skill level is itself a BA skill being tested.
Question 8
Tell me about a time you explained something complex to someone.
Direct evidence for the core job skill. Teaching a concept to a junior, presenting a project to a non-technical panel — walk through how you adapted the explanation to the listener, because that adaptation is the skill.
Question 9
A project you analyzed is failing. The data says one thing, the manager insists on another. What do you do?
Integrity plus diplomacy. Check your own analysis first — genuinely — then present findings with evidence, privately, framed around the shared goal. "I'd just do what the manager says" and "I'd insist I'm right" both fail, for different reasons.
Question 10
Why business analysis and not a purely technical role?
They're checking you chose this, rather than failing into it. A real moment where you enjoyed the translation work — organizing a fest, being the bridge in a group project — is the convincing answer.
Common questions
Do business analysts need to code?
Usually not beyond SQL, which most BA interviews now touch. Excel and a BI tool (Power BI or Tableau) plus solid SQL covers the technical bar for most fresher BA roles.
Which certifications help fresher BAs?
None are required, and none substitute for interviewing well. An ECBA or a good Coursera specialization can help your resume pass screening, but the interview itself is won with structured thinking and communication.
How do I practice guesstimate questions?
Out loud, with a timer — the structure that feels obvious in your head falls apart when spoken under pressure, and that's exactly what the interviewer is watching for. Practice five of them and the format becomes routine.