40 questions for IT Business Analyst interviews — 37 medium, 3 hard.
About the IT Business Analyst role
An IT business analyst works on software projects, translating business needs into functional specifications that developers and testers can build and verify. The role covers BRDs and FRDs, use cases, process models, data mapping, UAT support and change control, often in Agile teams. Interviews test requirement documentation, Scrum ceremonies, handling scope changes, working with technical teams and basic SQL for data validation and migration checks.
BRD and FRD writing Process modelling (BPMN) UAT coordination Agile and Scrum Basic SQL
Solved for this roleStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
✓ 3 questions free • Unlock the rest in seconds
01
What is the difference between ROW_NUMBER, RANK and DENSE_RANK?
All three number rows within a window ordered by a column. ROW_NUMBER gives a unique sequence 1, 2, 3 even for ties. RANK gives ties the same number and then skips, so 1, 1, 3. DENSE_RANK gives ties the same number without gaps, so 1, 1, 2. Use ROW_NUMBER to pick exactly one row per group, such as the latest order, and DENSE_RANK for 'top 3 distinct salary levels' type questions.
02
Stakeholders give conflicting requirements. What do you do?
Clarify the goal behind each request, map them to business objectives, prioritise with MoSCoW, run a joint session, then document the decision and get sign-off.
03
How would you build a simple financial model in Excel?
Structure it: households × car-owning share ÷ replacement cycle + first-time buyers + commercial fleet. State each assumption clearly and sanity-check the final number.
A use case describes the full interaction between an actor and the system (main and alternate flows). A user story is a short statement of need from the user's point of view, refined with acceptance criteria.
06
Tell me about a time you challenged how a metric was defined.
Situation: our team reported 'conversion' as orders divided by sessions, and it looked healthy while revenue was flat. Task: understand the gap. Action: I showed that repeated sessions from bots and app refreshes inflated the denominator inconsistently, and proposed user-level conversion excluding internal and bot traffic. I presented both definitions with a month of data to the product head. Result: the new definition was adopted, and it exposed a checkout drop that the team then fixed.
07
Write Excel formulas for IRR with yearly cash flows and XIRR with irregular dates.
# Yearly cash flows in B2:B7, year 0 investment negative
=IRR(B2:B7)
# Irregular dates: cash flows in B2:B7, dates in C2:C7
=XIRR(B2:B7, C2:C7)
# XIRR returns an annualised rate based on actual dates,
# which suits SIP returns or projects with uneven payments.
08
Tell me about a time you misunderstood a requirement. What did you learn?
Situation: I was asked for 'monthly active customers' and built it on login data. Task: deliver the report for a review. Action: in the demo, the stakeholder said active meant customers who purchased, not logged in. I owned the mistake, rebuilt the measure in two days and wrote down the definition for sign-off. Result: the report was accepted, and now I always confirm definitions and sample outputs with stakeholders before building anything.
Log the change, assess impact on scope, cost and timeline, get approval through change control or backlog grooming, and update documents and stakeholders.
10
Write a SQL query to get each customer's first order date and first order amount.
WITH ordered AS (
SELECT customer_id, order_date, amount,
ROW_NUMBER() OVER (PARTITION BY customer_id
ORDER BY order_date, order_id) AS rn
FROM orders
)
SELECT customer_id, order_date AS first_order_date,
amount AS first_order_amount
FROM ordered
WHERE rn = 1;
11
What is User Acceptance Testing (UAT) and what is the BA's role in it?
UAT is the final testing phase where real business users check that the system supports their work and meets requirements before go-live. The BA helps plan UAT, prepares business scenarios and test cases from requirements, arranges test data, supports users during testing, triages defects versus change requests and tracks sign-off. UAT is not about finding code bugs, which earlier testing should have caught.
12
Tell me about a time you said no to a stakeholder.
Situation: a regional manager wanted a custom report changed daily, which would have taken half my week. Task: support him without blocking other priorities. Action: I asked which decisions the report fed and found he needed only four numbers. I said no to the custom version, explained the impact on other work, and added those four metrics with a filter to the existing dashboard. Result: he got his numbers the same day and the team kept its capacity.
Stakeholders and the sponsor review the Business Requirements Document for completeness and accuracy, and the business owner gives formal sign-off before design begins.
15
Two analysts report different monthly active user numbers from the same database. How do you resolve it?
Put both queries side by side and compare definitions: which events count as active, time zone, calendar versus rolling month, test and internal accounts, deleted users, and DISTINCT on user ID versus device ID. Run both on a single day to find where they diverge. Agree on one definition with the metric owner, document it, and publish it as a shared view or metric so everyone queries the same logic.
16
Tell me about a time you handled a difficult stakeholder.
Use STAR: Situation, Task, Action, Result. Show that you listened, found the underlying goal, used data to align people and reached a documented decision.
17
Write a SQL query to show cumulative revenue by month.
WITH monthly AS (
SELECT DATE_TRUNC('month', order_date) AS month,
SUM(amount) AS revenue
FROM orders
GROUP BY 1
)
SELECT month, revenue,
SUM(revenue) OVER (ORDER BY month) AS cumulative_revenue
FROM monthly
ORDER BY month;
-- add PARTITION BY EXTRACT(YEAR FROM month) to reset each year
Define the scope: where the process starts, such as a refund request, and where it ends, such as money credited. Identify the roles involved and draw swimlanes. Interview and observe each role, capturing steps, decisions, systems used, handoffs and time taken. Draw the flow in BPMN, mark pain points like rework loops and waiting time, and add measures such as average refund time. Validate the map with the people who do the work.
20
What is the answer-first or pyramid principle approach to presenting analysis?
Start with the main conclusion or recommendation, then give the two or three supporting reasons, and only then the detailed data. Senior stakeholders have little time, so a summary like 'Churn rose because of payment failures; fixing retries can save 4 lakh a month' should come first. Detail goes in the appendix. It is the opposite of a chronological walk through every step of the analysis.
21
How would you prioritise 10 features with a limited budget?
Score them with RICE or value-vs-effort, align with goals, consider dependencies and risks, validate with stakeholders, then use MoSCoW for the release plan.
WITH daily AS (
SELECT event_date, COUNT(DISTINCT user_id) AS dau
FROM events
WHERE event_date >= '2026-10-01' AND event_date < '2026-11-01'
GROUP BY event_date
),
monthly AS (
SELECT COUNT(DISTINCT user_id) AS mau
FROM events
WHERE event_date >= '2026-10-01' AND event_date < '2026-11-01'
)
SELECT ROUND(AVG(d.dau) * 1.0 / MAX(m.mau), 3) AS stickiness
FROM daily d CROSS JOIN monthly m;
25
Write a DAX measure that shows each category's percent share of total sales.
It means making sure stakeholders know realistically what will be delivered, when, and with what limits, before they form their own assumptions. A BA confirms scope in writing, states assumptions and dependencies, shares estimates with ranges, and flags risks early. When something changes, they update stakeholders immediately with options. Most stakeholder conflict comes from surprises, not from bad news itself.
SELECT region,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 1 THEN amount ELSE 0 END) AS q1,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 2 THEN amount ELSE 0 END) AS q2,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 3 THEN amount ELSE 0 END) AS q3,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 4 THEN amount ELSE 0 END) AS q4
FROM orders
WHERE EXTRACT(YEAR FROM order_date) = 2026
GROUP BY region;
Get to the underlying business goal behind the requirement, because the goal is often achievable in another way. Ask developers to explain the constraint and the cost of alternatives. Bring both sides together with options: a simpler version, a phased delivery, a manual workaround or a different design. Show effort, risk and value for each, and let the product owner or sponsor decide. Document the decision.
31
How do you handle NULL values when calculating averages?
Story points measure relative effort, complexity and uncertainty compared with a reference story, using a scale like 1, 2, 3, 5, 8. People are better at comparing sizes than predicting exact hours, and points do not depend on who does the work. Over a few sprints the team's velocity, points completed per sprint, makes forecasting reliable. Points should never be used to compare productivity across teams.
WITH m AS (SELECT month, SUM(amount) AS rev FROM orders GROUP BY month)
SELECT month, rev,
ROUND(100.0 * (rev - LAG(rev) OVER (ORDER BY month))
/ LAG(rev) OVER (ORDER BY month), 1) AS mom_pct
FROM m;
WITH ranked AS (
SELECT category, product_id, SUM(amount) AS revenue,
DENSE_RANK() OVER (PARTITION BY category
ORDER BY SUM(amount) DESC) AS rk
FROM sales
GROUP BY category, product_id
)
SELECT category, product_id, revenue
FROM ranked
WHERE rk <= 3
ORDER BY category, rk;
36
What are window functions in SQL and how are they different from GROUP BY?
A window function calculates across a set of related rows using OVER(), but it keeps every original row instead of collapsing them. GROUP BY returns one row per group. For example, SUM(amount) OVER (PARTITION BY region) shows each order next to its region total, which helps compute share of total, rankings, running totals and month-over-month change. Common window functions are ROW_NUMBER, RANK, LAG, LEAD and SUM.
37
A stakeholder's only requirement is 'make the app faster'. How do you turn this into clear requirements?
Ask which screens or actions feel slow, for which users, on which devices and networks, and how it affects the business, such as checkout drop-off. Gather current timings from monitoring data. Then write measurable non-functional requirements, for example 'the search results page loads within 2 seconds for 95 percent of requests on a 4G connection'. Confirm targets with the stakeholder and agree how they will be tested.
38
After joining orders to a payments table, your total revenue doubled. What went wrong?
The join created a fan-out: some orders have more than one payment row, such as split payments or retries, so each order amount is repeated. Check the grain by counting rows per order_id on both sides. Fix it by aggregating payments to one row per order in a CTE before joining, joining on the full key, or summing from the table whose grain matches the metric. Always compare row counts before and after a join.
39
A stakeholder asks for a detailed report by tomorrow, but it realistically needs a week. What do you do?
Understand the real need first: what decision is it for and what is the minimum that helps tomorrow? Offer a phased answer, such as a quick directional view with the top three numbers tomorrow, clearly labelled with caveats, and the full validated report in a week. Explain the trade-off between speed and accuracy. Confirm the agreed plan in writing so expectations are clear.
40
A business head wants 25 charts on one dashboard page. How do you respond?
Ask what decisions they make weekly and which three to five KPIs drive them. Propose a summary page with those KPIs, trends and one breakdown, then drill-through or separate pages for detail. Show a quick mock-up of both versions so they see the clutter and the load time. Use bookmarks or a field parameter to let them switch views without adding charts. Agree on the layout before building.
Frequently asked questions
What does a IT Business Analyst do?
An IT business analyst works on software projects, translating business needs into functional specifications that developers and testers can build and verify. The role covers BRDs and FRDs, use cases, process models, data mapping, UAT support and change control, often in Agile teams. Interviews test requirement documentation, Scrum ceremonies, handling scope changes, working with technical teams and basic SQL for data validation and migration checks.
Which skills are tested in a IT Business Analyst interview?
Expect questions on BRD and FRD writing, Process modelling (BPMN), UAT coordination, Agile and Scrum, Basic SQL. Most rounds also ask you to explain a project and solve one practical problem live.
How do I prepare for a IT Business Analyst interview?
Revise Requirements and Agile, Stakeholder Communication, SQL for Business Analysis first using the topic sheets, practise the questions on this page aloud, then do one full mock interview to practise timing.