Business Analytics Interview Questions for 7 Years Experience
40 questions with answers for candidates with 7 years of experience — 1 easy, 13 medium, 26 hard.
What interviewers expect: 7 years experience
Seven-year candidates are evaluated for lead BA, analytics lead or product analytics manager roles. Expect questions on building and governing a single source of truth, prioritising a portfolio of requests, running experiments at scale, managing a small team and partnering with business heads on strategy. Answers should show trade-offs, outcomes and lessons learned.
This set is weighted towards Case Studies and Guesstimates (7), Product Analytics (6), Process Modelling and BPMN (6), Requirements and Agile (4).
Analytics and BA team leadership Data and metric governance Portfolio prioritisation Strategic partnership with leaders
Solved at this levelStart 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
A ride-hailing app's ride cancellation rate rose from 8 to 14 percent. How would you structure the problem?
First split by who cancels: riders or drivers. For rider cancellations, check wait times, pickup accuracy, price surges and changes in ETA. For driver cancellations, check trip distance, payment mode, low fares, destination visibility and incentive changes. Then segment by city, time of day and area. Link to recent changes like a new pricing rule. Recommend fixes for the largest driver, such as better matching or adjusted incentives.
02
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.
03
A quick-commerce company wants to expand into Tier-2 cities. What would you analyse before recommending it?
Demand: population density, smartphone and digital payment penetration, average basket size and how often people buy groceries. Supply: dark store rent, rider availability and local sourcing. Unit economics: orders per store per day needed to break even, given lower average order values. Competition: local kirana delivery and other apps. Then propose a pilot in two or three cities with clear success metrics such as orders per day, contribution margin per order and repeat rate before scaling.
04
You must gather requirements to replace a 15-year-old legacy system with no documentation. How do you approach it?
Combine several sources. Interview and observe users doing real tasks, and review screens, reports and outputs to infer business rules. Analyse the database and logs to see which data and functions are actually used. Work with long-serving staff and IT support for hidden rules and workarounds. Build AS-IS process maps, decide what to keep, drop or improve, and validate the findings with users. Plan data migration requirements early.
05
The sales team keeps hitting its revenue target, but company margins are falling. What would you recommend?
The incentive rewards revenue regardless of profitability, so reps are likely discounting heavily or pushing low-margin products. Analyse deal-level discount, product mix and margin by rep and region to confirm. Then recommend changing the target to gross margin or contribution, or adding discount approval limits and a margin floor to commission. Pilot the new plan with one region and track revenue, margin and win rate together.
06
How would you forecast next quarter's sales in Excel?
The novelty effect is a temporary lift because users are curious about something new, which fades after a few days; the opposite, change aversion, causes a temporary drop. Running tests for at least one or two full weeks covers weekday and weekend behaviour and lets these effects settle. You can also check whether the lift is stable over time and among new users who never saw the old version.
08
How would you estimate the market size for an electric scooter in India?
Normalisation splits data into related tables to remove redundancy and update anomalies, which suits transactional systems that write often. Analytics workloads read far more than they write, so warehouses often denormalise into wide fact and dimension tables or star schemas. That reduces joins, makes queries simpler for analysts and speeds up aggregation, at the cost of extra storage and the need for controlled loading pipelines.
10
How would you measure the success of a new feature?
Define a goal metric, a baseline and guardrail metrics, run an experiment or before-after comparison and review adoption, retention and revenue impact.
11
What is a cutover plan and a go-live readiness checklist?
A cutover plan is an hour-by-hour runbook for moving from the old system to the new one: freezing old transactions, final data migration, validation checks, configuration, smoke testing, switch-over and a rollback plan with clear decision points. A go-live readiness checklist confirms that UAT is signed off, users are trained, support and hypercare are staffed, data is reconciled, and communications are sent. The go or no-go meeting reviews this checklist before the cutover starts.
12
Should a supermarket chain launch its own private-label products?
Evaluate attractiveness and ability. Attractiveness: private labels usually earn higher margins, so check category size, how price-sensitive customers are, and whether brand loyalty is weak in categories like staples and cleaning. Ability: supplier availability, quality control, shelf space and brand trust. Estimate the margin gain against cannibalisation of branded sales and supplier relationships. Recommend starting with a few high-volume, low-loyalty categories and measuring repeat purchase.
13
Why should you avoid bidirectional relationships in a Power BI model?
Relationships normally filter one way, from the dimension (one side) to the fact (many side). Bidirectional filtering lets facts filter dimensions too, which can create ambiguous filter paths, unexpected totals and slower queries, especially with multiple fact tables. Prefer a clean star schema with single-direction filters, and when you need a reverse filter for one measure, use CROSSFILTER or TREATAS inside CALCULATE instead of changing the model globally.
14
Five departments each build their own Power BI reports with different revenue numbers. How would you design a better BI setup?
Create a shared, certified semantic model with one definition per KPI, built on a governed warehouse layer. Departments build thin reports on top of it through live connection instead of copying data. Set up workspaces by environment (dev, test, prod), deployment pipelines, naming standards, a KPI glossary and owners for each measure. Keep a small central team for the core model and let departments self-serve on top, which balances control and speed.
15
What is root cause analysis and which techniques do you know?
Bookings are the value of contracts signed in a period, showing future commitment. Billings are the amounts invoiced to customers in the period. Revenue is what is earned and recognised under accounting rules as the service is delivered. Example: a 3-year contract worth 36 lakh signed in April is 36 lakh in bookings, 12 lakh in billings if invoiced annually, and only 1 lakh in revenue for April. Confusing them is common when reporting sales performance.
18
What steps would you follow to run a process discovery workshop?
Before: agree scope and process boundaries, invite people who actually do the work, not only managers, and collect existing documents and sample cases. During: state the goal, map the happy path first on a wall or digital board, then add exceptions, pain points, handoffs and volumes, and park off-topic issues. Keep timing visible. After: convert the output to a clean BPMN diagram within two days, circulate it for validation, and record open questions with owners and dates.
DMN (Decision Model and Notation) is an OMG standard for modelling business decisions, mainly through decision tables that list input conditions, outputs and a hit policy. BPMN shows the flow of work, while DMN holds the decision logic. Instead of drawing ten nested gateways for loan eligibility, you place one business rule task in BPMN that calls a DMN table. This keeps diagrams clean and lets business users change rules without redrawing the process.
20
Describe a time when stakeholders resisted a process change you proposed. How did you handle it?
Situation: I proposed removing a manual second approval for low-value expense claims, and team leads resisted, fearing fraud. Task: get agreement without weakening control. Action: I analysed six months of claims and showed the second approver rejected less than 0.5 percent below 5,000 rupees. I suggested a pilot with random audits of 10 percent of claims and agreed a reversal trigger. Result: the pilot ran for two months with no extra fraud, approval time fell by 3 days and the change was adopted.
21
A project's business case promised 30 percent cost savings, but after go-live only 10 percent is realised. What do you do?
Run a benefits review against the original baseline and assumptions. Check whether savings depended on actions that did not happen, such as reducing manual roles, retiring the old system or full user adoption. Check whether the baseline or volumes changed. Separate delayed benefits from lost ones. Then produce a recovery plan with owners, for example decommissioning the legacy licence or driving adoption. Also feed the lessons into how future business cases estimate benefits.
22
How do you manage conflicting requirements from two senior stakeholders?
Clarify the underlying goals, present data and trade-offs, facilitate a joint session, escalate to the sponsor if needed and document the agreed decision.
23
What are process levels such as L0 to L4 in a process architecture?
Process levels organise models from broad to detailed. L0 shows the value chain or main process areas, such as Order to Cash. L1 and L2 break these into process groups and end-to-end processes, such as Credit Management. L3 shows the detailed BPMN flow with roles and decisions. L4 covers work instructions or system steps. A level structure keeps hundreds of diagrams consistent, avoids duplicates and lets executives and operators each read the right depth.
24
Tell me about an experiment that failed and what you learned.
Situation: we tested a simplified pricing page expecting higher paid conversion. Task: I owned the experiment design and analysis. Action: after two weeks the variant showed no significant change, and segment checks revealed that heavy users missed the plan comparison table. I documented the result and shared it openly rather than searching for a winning segment. Result: the next version kept the simple layout with an optional comparison, and we learned to interview users before testing.
25
Write an Excel formula for the NPV of a project with an initial investment today and five yearly cash inflows.
# B1 = discount rate (for example 12%)
# B2 = initial investment entered as a negative number
# B3:B7 = cash inflows for years 1 to 5
=NPV(B1, B3:B7) + B2
# NPV() assumes the first value comes at the end of year 1,
# so the year-0 investment is added outside the function.
26
What are unit economics and why do investors and leaders focus on them?
Unit economics measure revenue and cost for one unit of business, such as one order, one customer or one subscription. For an order you compute average order value minus product cost, delivery, payment fees, discounts and support cost to get contribution margin. If each unit loses money, scale only increases losses. Leaders use unit economics to decide pricing, which cities or channels to grow and where to cut cost.
27
Your project is going to miss its deadline by two weeks. How do you communicate this?
Tell the sponsor and key stakeholders as soon as you are confident, not on the deadline. Be direct about the delay, the cause and the impact. Come with options, such as reducing scope to hit the date, adding resources, or moving the date with a phased release, plus your recommendation. Agree on the new plan, update the communication plan and track the recovery visibly.
28
Finance and sales blame each other for wrong numbers in a monthly report. How do you resolve it as the analyst?
Stay neutral and move the discussion from blame to facts. Trace the number end to end: source system, extraction, transformation and report logic, and find exactly where the values diverge. Share the findings with both teams together, agree on the fix and on a single owner for the definition. Then add automated reconciliation checks and a data dictionary, so the process, not people, prevents the next issue.
29
Overall conversion fell this month, yet conversion improved for both mobile and desktop users. How is that possible?
This is Simpson's paradox caused by a change in mix. If mobile converts lower than desktop and the share of mobile traffic grew sharply, the overall average can fall even though each segment improved. Show conversion by segment along with the traffic mix. The insight is not that conversion got worse but that traffic shifted, so the question becomes how to raise mobile conversion further.
30
Guesstimate: what is the annual revenue of one multiplex screen in a large Indian city?
Assume 5 shows a day and 200 seats with 30 percent average occupancy, giving 300 tickets a day. At an average ticket of 250 rupees, ticket revenue is 75,000 rupees a day. Food and beverage adds about 40 percent of ticket revenue, around 30,000, and screen ads maybe 5,000. That is about 1.1 lakh a day, or around 4 crore a year. Weekends and blockbuster releases push occupancy higher.
31
Describe a BPMN model for a purchase order process where credit check and stock check happen at the same time.
Start event: purchase order received. Task: validate order details. A parallel gateway then splits into two paths: Finance lane runs Check customer credit, Warehouse lane runs Check stock. A second parallel gateway joins them, waiting for both to complete. An exclusive gateway then decides: credit OK and stock available goes to Confirm order and Schedule dispatch; otherwise go to Notify customer with reason. Using a parallel join here is correct because both results are always needed.
32
Describe a time you led the requirements phase of a large project.
Situation: our company was replacing its loan origination system across five business units. Task: lead requirements with two other BAs in three months. Action: I set up a stakeholder map, ran structured workshops per unit, used shared templates and a traceability matrix, and held weekly review checkpoints with the sponsor to resolve conflicts quickly. Result: requirements were signed off on time, change requests in build stayed low, and the template was reused for later projects.
33
What is a North Star metric and how do you choose one?
A North Star metric is the single measure that best captures the value customers get from the product and predicts long-term revenue. Examples are weekly active learners for an ed-tech app or orders delivered on time for a delivery business. Choose one that reflects customer value, can be influenced by teams and leads revenue. Support it with input metrics such as activation, frequency and retention that teams can work on directly.
34
What is a process flow and which tools do you use?
Usually the values only look the same. Common causes are trailing or leading spaces, numbers stored as text in one sheet and as numbers in the other, non-breaking spaces from web exports, or different spellings. Check with =LEN() and =ISNUMBER(), clean with TRIM, CLEAN or VALUE, and confirm the lookup range covers all rows and uses exact match. Wrap the final formula in IFNA to label true misses.
36
Your A/B test was meant to split traffic 50/50, but the actual split is 52/48 on 200,000 users. What do you do?
This is a sample ratio mismatch. With 200,000 users, a 52/48 split is far outside random chance, which a chi-square test will confirm. It means the assignment or logging is broken, for example the variant page crashing before the tracking event fires, bots filtered unevenly or a redirect losing users. Do not trust the results. Investigate by segment, platform and day to find the cause, fix it and rerun the test.
37
How do you influence stakeholders when you have no direct authority?
Build credibility with accurate work and by understanding each stakeholder's goals and pressures. Frame proposals in terms of their outcomes, such as cost saved or targets met, and back them with data. Involve them early so ideas feel shared, find allies who already support the change, and pilot small to show results. Be transparent about trade-offs. Influence comes from trust built over time, not one meeting.
38
A new TO-BE process went live three months ago. How do you prove that the improvement actually worked?
Compare against the baseline you measured before the change, using the same definitions: cycle time, first-time-right rate, cost per case, backlog and customer complaints. Pull data from system timestamps rather than surveys. Check that the gain is not explained by lower volumes or seasonality, ideally by comparing similar periods. Also check for side effects, such as faster processing but more rework downstream. Present the before-and-after with the business owner, and note where adoption is still incomplete.
39
What is the logical order in which a SQL SELECT query is executed?
Logically the database processes FROM and JOIN first, then WHERE, GROUP BY, HAVING, SELECT, DISTINCT, ORDER BY and finally LIMIT or TOP. This explains common errors: you cannot use a SELECT alias in WHERE because WHERE runs earlier, aggregate conditions must go in HAVING, and window functions cannot be filtered in WHERE, so you wrap them in a CTE or subquery. The optimiser may physically reorder steps, but the result follows this order.
40
Tell me about a time your analysis changed a product decision.
Situation: the team planned to add more filters to the search page to fix low conversion. Task: I was asked to size the opportunity. Action: funnel analysis showed most drop-off happened after users opened a product page with no delivery date shown, not in search. I shared the data with session recordings. Result: the team prioritised showing delivery dates on the product page, conversion rose about 8 percent, and the filter work was deprioritised.
Frequently asked questions
What is asked in Business Analytics interviews for 7 years of experience?
Seven-year candidates are evaluated for lead BA, analytics lead or product analytics manager roles. Expect questions on building and governing a single source of truth, prioritising a portfolio of requests, running experiments at scale, managing a small team and partnering with business heads on strategy. Answers should show trade-offs, outcomes and lessons learned.
How many questions should I practise before a Business Analytics interview?
Work through all 40 questions here, then the company-wise sets for the employers you are targeting. Quality matters more than count: be able to explain why each answer is right.
Which topics matter most for 7 years of experience?
Focus first on Analytics and BA team leadership, Data and metric governance, Portfolio prioritisation, Strategic partnership with leaders.