Business Analyst interview
Business Analyst interview practice, out loud
A BA screen is really three questions in a trench coat: can you form a hypothesis before you open a query editor, can you structure a messy business question into parts, and will you chase an insight until something actually changes. None of that shows up on a résumé — it shows up when someone asks a follow-up.
This rehearsal is a spoken interview built on a real business-analyst job description. It moves from an analysis that changed a decision, to a flat-revenue mystery, to SQL reasoning you narrate without a keyboard, to defending a number to a sceptic.
The report tells you whether you decomposed before you queried, whether you noticed the rows that quietly drop out of a join, and whether you sized the opportunity in money or in percentage points.
What this interview assesses
Analytical Rigour
Do you decompose a question before querying, join and aggregate correctly, think about the rows that go missing, and sanity-check a result before you present it?
Business Judgement
Do you size opportunities in money rather than percentages, separate activity from output, and chase the largest addressable loss instead of the most visible one?
Stakeholder Communication
Can you explain a derivation to a sceptic, engage the objection instead of restating the number, and change your mind when the objection is right?
Sample Business Analyst interview questions
A feel for the kind of questions you’ll face. The real interview reacts to your answers with live follow-ups — these are examples, not the exact set.
1.Tell me about an analysis you ran that changed a decision. What did you find?
What lands: Anchor on a real question with a decision riding on it. State the finding with actual numbers and name what changed.
2.Revenue is flat this month, but the team is busier than ever. How do you find out what's going on?
What lands: Decompose revenue into volume, price and mix, segment by channel or cohort, and separate activity from output.
3.You've got an orders table and a customers table. How would you find the customers whose spend dropped the most?
What lands: Join on the right key, aggregate by period — and notice that customers with zero orders this quarter fall out of an inner join.
4.Explain a number to me that I don't believe.
What lands: Understand the specific objection first, walk the derivation step by step, and adjust if they turn out to be right.
5.One week to find where we're losing the most money in the funnel. How do you spend it?
What lands: Size each drop-off in rupees, not percentage points. The biggest gap and the biggest loss are rarely the same step.
The job description it’s built around
The free taster rehearses against this realistic Business Analyst posting. In a full rehearsal you can paste the exact job you’re targeting instead.
Read the sample job description
Business Analyst (0–3 yrs) · Fintech · Mumbai About the role We are a lending fintech scaling fast across India. Business Analysts here sit with the growth and operations teams, own the numbers, and turn them into actions: which channel to double down on, which process is leaking money, which cohort is going bad. What you'll do - Build and maintain dashboards for growth, risk and operations metrics - Pull and clean data with SQL and Excel/Google Sheets; automate recurring reports - Analyse funnels, cohorts and unit economics; find and size opportunities - Work with product and ops to design process fixes, then measure whether they worked - Prepare crisp weekly business reviews for leadership - Document requirements for data and product changes and follow them through What we're looking for - 0–3 years in analytics, consulting or operations - Strong SQL and advanced Excel/Sheets (pivots, lookups, basic modelling) - Structured problem-solving — you form hypotheses before opening a query editor - Clear communication with both business and technical teams - Bias for ownership: you chase an insight until something changes Nice to have - Python or a BI tool (Power BI/Tableau/Looker/Metabase) - Exposure to lending, payments or marketplace metrics
Business Analyst interview — FAQs
Do I need to write live SQL?
No — you narrate the logic out loud, the way a real analyst screen tests whether you'd write the right query. It's about the joins, the aggregation and the edge cases, not syntax.
Is this for data analysts too?
Yes. Business analyst, data analyst and operations-analyst screens overlap heavily at the 0–3 year level, and the questions here target that shared core of decomposition, SQL reasoning and stakeholder communication.
How much does industry matter?
The reasoning transfers across fintech, e-commerce and SaaS. The curated posting is a lending fintech; the full rehearsal lets you paste the exact JD you're targeting.
What will the feedback actually tell me?
Where your reasoning was sharp, where you jumped to a query without a hypothesis, and the single habit — often 'size it in money' — most likely to change your next interview.
Related interviews
Ready to rehearse for real?
Start a free five-minute Business Analyst interview now. You’ll get a spoken interview with live follow-ups and a feedback report that quotes your own answers back.