Business Analytics Interview Questions for Associate Roles (₹6–8 LPA)
40 questions with answers for associate roles — 15 easy, 24 medium, 1 hard.
What ₹6–8 LPA interviews expect
Hands-on problem solving Debugging simple real-world issues Clear communication of results Working knowledge of core tools
About ₹6–8 LPA Business Analytics roles
Roles in the ₹6–8 LPA band are typically for associate roles. Interviewers check whether you can already do the work expected at this level, so questions here are weighted towards Requirements and Agile (9), SQL for Business Analysis (5), UAT and BA Documentation (5), Case Studies and Guesstimates (4).
Salary bands are indicative only. The same skills can pay differently across cities, company types and negotiation.
Solved in this bandStart 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 techniques do you use to elicit requirements?
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.
Both measure short-term liquidity. The current ratio is current assets divided by current liabilities; around 1.5 to 2 is often comfortable, though it varies by industry. The quick ratio excludes inventory and prepaid items: (cash plus marketable securities plus receivables) divided by current liabilities. It is stricter because inventory may not sell quickly. A retailer with a current ratio of 1.8 but a quick ratio of 0.4 depends heavily on selling its stock to pay bills.
04
What is the hierarchy of epic, feature and user story in Agile?
An epic is a large body of work that delivers a major business goal and spans several sprints, such as 'Online loan application'. It is broken into features or capabilities, such as 'Document upload'. Each feature is split into user stories small enough to finish in one sprint, such as 'As an applicant, I want to upload my PAN card photo so that I do not need to visit a branch'.
05
After many sprints, project documentation is out of date and new team members are confused. What do you do?
Identify which documents are actually used: usually a product overview, process maps, business rules, data dictionary and integration details. Update those first rather than everything. Make documentation part of the Definition of Done, so a story is not complete until related docs are updated. Keep living documents in a shared wiki with owners and last-reviewed dates, and archive outdated files clearly. Test the result by having a new joiner use it during onboarding.
06
Write a SQL query for a 7-day rolling average of daily revenue.
WITH daily AS (
SELECT order_date, SUM(amount) AS revenue
FROM orders
GROUP BY order_date
)
SELECT order_date, revenue,
AVG(revenue) OVER (ORDER BY order_date
ROWS BETWEEN 6 PRECEDING AND CURRENT ROW) AS rolling_7d
FROM daily
ORDER BY order_date;
-- fill missing dates from a calendar table first, or gaps skew the average
EBITDA is earnings before interest, taxes, depreciation and amortisation. It approximates operating profit generated by the core business before financing choices, tax rules and non-cash accounting charges. It is useful for comparing companies with different debt levels or asset ages and is used in valuation multiples such as EV/EBITDA. Its weakness is that it ignores capital expenditure and working capital needs, so a company can show strong EBITDA and still burn cash.
08
What steps do you follow to plan and run a UAT cycle?
Plan: agree scope, entry and exit criteria, testers and schedule with the business owner. Prepare: write scenarios and test cases from requirements, set up the environment and test data, and brief testers. Execute: run test cases in daily sessions, log defects with evidence and hold a daily triage. Monitor: report progress, pass rate and open defects by severity. Close: check exit criteria, get the business sign-off with known issues documented, and hold a short lessons-learned review.
Situation: a new claims system passed QA, but in UAT a claims officer tried a real scenario with two policies on one claim. Task: as BA I had to assess and resolve it quickly. Action: I confirmed the requirement never covered multi-policy claims, quantified that 8 percent of claims were affected, and agreed a manual workaround while the change was built. Result: we went live on time, delivered the fix in the next release, and I added real case samples to future test design.
MECE means Mutually Exclusive and Collectively Exhaustive. When you break a problem into parts, the parts should not overlap and together should cover every possibility. For example, profit splits into revenue and cost, and revenue into price times volume. A breakdown of customers into 'young' and 'students' is not MECE because they overlap. MECE structures prevent double counting and missed causes, which is what interviewers check.
12
What is user story mapping and how does it help plan releases?
User story mapping arranges stories in two dimensions. Across the top is the user journey as a sequence of activities, for example search, compare, buy and track. Below each activity, stories are stacked by priority. Drawing horizontal lines across the map creates release slices, where the first slice is a thin end-to-end MVP that covers every step at a basic level. It prevents a flat backlog where teams build one area deeply while the journey stays incomplete.
Cohort analysis groups users by a shared starting point, usually their sign-up or first purchase month, and tracks their behaviour over time, such as the percentage still active in month 1, 2 and 3. It separates the effect of growth from the effect of retention, so you can see whether newer cohorts retain better after a product change. It is typically shown as a triangle table or retention curves.
14
What is a data dictionary and why does a business analyst maintain one?
A data dictionary is a catalogue of data elements used in a system or report: field name, business definition, data type, length, allowed values, mandatory or optional, source system, owner and example values. A BA maintains it so business users, developers and testers use one definition, for example what counts as an active customer. It prevents mapping errors in integrations and migrations, speeds up testing and reduces disputes about why reports do not match.
A balanced scorecard is a strategic performance framework that tracks objectives and KPIs across four perspectives: financial (revenue growth, margin), customer (NPS, retention), internal processes (cycle time, defect rate) and learning and growth (training hours, employee engagement). The idea is that financial results are lagging, so leaders also need leading measures of what drives future performance. A strategy map links the objectives with cause-and-effect arrows from people to processes to customers to financial outcomes.
PESTEL scans the external environment across Political, Economic, Social, Technological, Environmental and Legal factors. For an electric vehicle maker in India it would cover subsidies and policy, fuel prices and interest rates, consumer attitudes, battery technology, emission targets and safety regulations. It is useful in market entry and strategy cases to spot opportunities and risks beyond the company's control, and pairs well with SWOT.
17
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.
Scrum works in fixed sprints with defined roles such as product owner and scrum master, planned sprint goals and ceremonies like planning, review and retrospective. Kanban has no sprints: work flows continuously across a board, and work-in-progress limits on each column prevent overload. Kanban measures cycle time and throughput. Scrum suits product development with planned increments; Kanban suits support, operations and reporting requests that arrive unpredictably.
19
Write an Excel formula for month-to-date sales up to today.
// Dates in Sales[Date], amounts in Sales[Amount]
=SUMIFS(Sales[Amount],
Sales[Date], ">=" & EOMONTH(TODAY(), -1) + 1,
Sales[Date], "<=" & TODAY())
// EOMONTH(TODAY(),-1)+1 gives the first day of the current month
20
You receive two customer lists from sales and billing and must reconcile them. How do you do it?
Standardise both first: trim spaces, fix case, convert IDs to the same type and remove duplicates. Use a unique key like customer ID, or a combined key of phone and email if IDs differ. Then use XLOOKUP or COUNTIFS to mark each record as matched, only in sales or only in billing, or a Power Query merge with anti joins. Summarise mismatches by type and share the exception list with both owners.
21
How do you validate that a report's numbers are correct?
An index is a sorted lookup structure on one or more columns that lets the database find rows without scanning the whole table, much like a book index. It speeds up WHERE filters, joins and ORDER BY on those columns. It hurts when there are too many indexes, because every insert and update must maintain them, and it may not help on low-selectivity columns or when functions are applied to the indexed column.
A language for querying databases. BAs use it to pull data themselves, validate numbers, check reports and answer questions without waiting for engineers.
24
Write an Excel formula for working days between two dates excluding weekends and holidays.
// A2 = start, B2 = end, Holidays = named range of holiday dates
=NETWORKDAYS(A2, B2, Holidays)
// if the weekend is only Sunday (common in India)
=NETWORKDAYS.INTL(A2, B2, 11, Holidays)
SUMIFS is faster and easier for sums with AND conditions on ranges. SUMPRODUCT multiplies arrays and sums the result, so it handles cases SUMIFS cannot: weighted totals like price times quantity, OR logic, conditions on calculated values such as MONTH(date)=4, or comparing two columns row by row. On very large sheets SUMPRODUCT is slower, so prefer SUMIFS or a helper column when possible.
26
A manager says the dashboard total does not match the finance team's Excel sheet. What do you do?
First agree on the definition: date range, gross or net, tax, returns, currency and which date (order or invoice) is used. Then reconcile at a small grain, such as one month and one region, comparing row counts and sums between the source query and the sheet. Common causes are filters on the page, missing relationships, duplicate rows after a join or a late refresh. Document the agreed definition in the report tooltip.
A UAT test plan defines how acceptance testing will be run. It covers scope and out-of-scope items, business processes to be tested, entry and exit criteria, roles such as testers, UAT lead and sign-off authority, test environment and test data, schedule and cycles, defect management process with severity definitions, communication and reporting, and risks. The BA usually drafts it with business owners so testers know exactly what they are accepting and when.
A model classifying features as basic, performance or delight attributes based on how they affect customer satisfaction, helping decide what to build first.
29
What is the difference between a task and a sub-process in BPMN?
A task is an atomic unit of work that you do not break down further in the diagram, such as Verify PAN details. A sub-process is a compound activity that contains its own flow of tasks, events and gateways, shown with a small plus sign when collapsed. Sub-processes keep high-level diagrams readable: the main map shows Credit Check as one box, and a separate detailed view explains its internal steps.
30
Split the epic 'Customers can track their order online' into user stories.
Possible stories: As a customer, I want to see my order status (placed, packed, shipped, delivered) so that I know its progress. As a customer, I want an SMS or email when the status changes so that I do not have to check. As a customer, I want the expected delivery date so that I can plan. As a customer, I want a courier tracking link once shipped. As support staff, I want to see the same timeline so that I can answer queries.
31
What is the Ansoff matrix and how is it used in growth cases?
The Ansoff matrix maps four growth strategies by product and market. Market penetration sells existing products to existing markets, the lowest risk. Product development offers new products to existing customers. Market development takes existing products to new markets, such as new cities. Diversification launches new products in new markets, the highest risk. In a growth case it structures the options before you evaluate each one's size, cost and fit.
32
Which chart would you choose for trend, part-to-whole, comparison and distribution?
For a trend over time use a line chart. For part-to-whole use a stacked bar or a 100 percent bar; a pie or donut only works with two to four slices. For comparing categories use a sorted horizontal bar chart. For distribution use a histogram or box plot. For correlation between two measures use a scatter plot. Choosing by the question being answered, not by looks, keeps dashboards readable.
33
What is backlog refinement and what is the BA's role in it?
Backlog refinement, also called grooming, is a regular session where the team reviews upcoming backlog items to clarify, split, estimate and order them, so the next sprints have ready work. The BA prepares the stories in advance with business context, acceptance criteria, rules and examples, answers questions from developers and testers, and captures follow-ups. It is usually a short weekly session, not a sprint ceremony.
Link your answer to real experience. For example: during my internship I noticed reports were rebuilt manually every week, so I mapped the process and automated it with Power Query, saving the team a day each week. I enjoyed understanding the problem, talking to users and seeing the result used. A BA role combines that problem solving, communication and data work, which is where my strengths are, and I want to build deeper domain knowledge.
35
What is horizontal and vertical analysis of financial statements?
Horizontal analysis compares line items across periods, showing growth, for example revenue up 18 percent year on year while employee costs grew 30 percent. Vertical analysis expresses each item as a percentage of a base within one period, such as each expense as a percentage of revenue, or each asset as a percentage of total assets. Together they show both trends and structure, and vertical analysis also makes companies of different size comparable.
36
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.
37
How do you adapt your communication for executives versus technical teams?
Executives want outcomes, impact, risk and decisions needed, in a one-page summary or a few slides with clear numbers. Technical teams need precise details: data fields, business rules, edge cases, acceptance criteria and dependencies. Operations users need process steps and what changes in their daily work. Same facts, different depth and vocabulary. Ask each group how they prefer to receive updates and adjust.
38
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.
Product, Price, Place and Promotion, the levers a business uses to bring an offering to market.
Frequently asked questions
What do Business Analytics interviews for ₹6–8 LPA roles test?
At ₹6–8 LPA the focus is usually on: hands-on problem solving, debugging simple real-world issues, clear communication of results, working knowledge of core tools. This page's set is weighted towards Requirements and Agile (9), SQL for Business Analysis (5), UAT and BA Documentation (5), Case Studies and Guesstimates (4).
Which companies pay ₹6–8 LPA for Business Analytics roles?
Pay depends on company type, city, skills and negotiation, not only experience. Use the company-wise pages to practise for the specific employers you are targeting, and treat salary bands as a rough guide.
How should I prepare for a ₹6–8 LPA Business Analytics interview?
Solve every question here without looking at the answer first, mark the ones you miss, save them to Last-Minute Revision and revise them the night before. Prepare two project stories that show impact at the level expected for ₹6–8 LPA.