Business Analytics Interview Questions for Top Product Companies (₹50+ LPA)
40 questions with answers for top product companies — 11 medium, 29 hard.
What ₹50+ LPA interviews expect
Very deep expertise and original thinking Large-scale trade-offs and failure modes Track record of measurable impact Leadership principles and culture fit
About ₹50+ LPA Business Analytics roles
Roles in the ₹50+ LPA band are typically for top product companies. Interviewers check whether you can already do the work expected at this level, so questions here are weighted towards Stakeholder Communication (9), Business Metrics and KPIs (6), Product Analytics (6), 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 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.
02
A bank's mobile app logins increased, but digital transactions fell. What could explain this?
Users are coming but not completing transactions, so look at the gap. Possible causes: a release that broke a payment flow, new security steps like extra OTPs adding friction, logins driven by balance checks or offers, or transactions shifting to another channel. Compare the funnel from login to transaction by app version and device, check failure and error rates, and review support complaints before recommending fixes.
03
What does the LTV to CAC ratio tell you and what is a healthy value?
LTV to CAC compares the lifetime gross profit from a customer with the cost of acquiring them. A ratio around 3 to 1 is commonly treated as healthy. Below 1 means you lose money on every customer. Far above 5 may mean you are underinvesting in growth. Always compute LTV on gross margin, not revenue, and check it by channel, because blended averages hide loss-making channels.
04
Marketing and product teams define 'active user' differently and report conflicting numbers. How do you fix this?
Bring both teams together and list each definition, its purpose and its numbers. Agree on one company-wide definition tied to real value, such as a user who completed a core action in the last 7 days, and allow clearly named secondary metrics like 'visitors' for marketing. Assign an owner, document it in a metric glossary, implement it once in the warehouse or semantic model, and retire the duplicate dashboards.
05
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.
06
What is Excel Solver and give a business example of using it.
Solver is an optimisation add-in that finds the best value of a target cell by changing decision cells within constraints. Unlike Goal Seek, it handles many variables and constraints. Example: choose how many units of three products to make to maximise profit, subject to machine hours, raw material and minimum order limits. You set the objective, the variable cells, constraints and a method such as Simplex LP for linear problems.
07
Tell me about a time you led or mentored a team of analysts.
Situation: I led three junior analysts on a pricing review with a six-week deadline. Task: deliver quality work while developing them. Action: I split the work by workstream, set up short daily check-ins and a shared query library, reviewed their logic rather than rewriting it, and let each present their section to the client. Result: we delivered a week early, two juniors later handled client calls alone, and the review practice became standard in our team.
08
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.
09
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.
10
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.
11
How do sample size and minimum detectable effect affect an A/B test design?
The minimum detectable effect is the smallest lift worth detecting, such as a 2 percent relative increase in conversion. Smaller effects, lower baseline rates and higher required power need much larger samples, roughly four times the users to detect half the effect. Calculate sample size before starting using the baseline rate, MDE, significance level and power, usually 80 percent, then fix the test duration and avoid stopping early.
12
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.
13
What is the difference between bookings, billings and revenue?
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.
14
Developers say a requirement is not technically feasible, but the business insists on it. How do you mediate?
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.
15
Write a SQL query to calculate monthly customer churn rate for a subscription business.
WITH monthly AS (
SELECT DISTINCT customer_id,
DATE_TRUNC('month', billing_date) AS month
FROM subscriptions_billed
)
SELECT
prev.month AS month,
COUNT(prev.customer_id) AS customers_at_start,
COUNT(prev.customer_id) - COUNT(nxt.customer_id) AS churned,
ROUND(100.0 * (COUNT(prev.customer_id) - COUNT(nxt.customer_id))
/ COUNT(prev.customer_id), 2) AS churn_pct
FROM monthly prev
LEFT JOIN monthly nxt
ON nxt.customer_id = prev.customer_id
AND nxt.month = prev.month + INTERVAL '1 month'
GROUP BY prev.month
ORDER BY prev.month;
16
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
17
An A/B test shows a 5 percent higher conversion rate, but revenue per user is lower. Should you ship it?
Not automatically. Find out why: the variant may push cheaper products, bigger discounts or smaller orders, so more people buy but each spends less. Check average order value, margin and long-term metrics like repeat purchase. Decide based on the metric tied to the business goal, usually revenue or contribution per user, which should have been the primary metric or a guardrail. Consider iterating to keep the conversion gain without lowering order value.
18
A lender is launching a new personal loan product. What KPIs would you set up?
Cover the full funnel and risk. Acquisition: applications, approval rate, cost per disbursed loan and time to disbursal. Value: disbursed amount, average ticket size and net interest margin. Risk: delinquency rates at 30 and 90 days past due by cohort, and early default rate. Customer: drop-off by application step, complaint rate and repeat borrowing. Track risk by monthly disbursal cohort, because defaults show up months later.
19
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.
20
A feature was launched to all users at once without an A/B test. How would you measure its impact?
Use quasi-experimental methods. Compare before and after with enough history to account for trend and seasonality. If it rolled out at different times in regions or platforms, use difference-in-differences between early and late groups. Compare users who adopted with similar non-adopters using matching, while being careful about self-selection. For future launches, recommend keeping a small holdout group so impact can be measured cleanly.
21
What is user activation and what is an 'aha moment'?
Activation is the point at which a new user first experiences the product's core value, such as completing a first lesson, sending a first payment or creating a first project. The aha moment is the specific early action that strongly predicts long-term retention, found by comparing retained and churned users. Teams then design onboarding to get more new users to that action quickly and track the activation rate.
22
What is operational acceptance testing and how is it different from UAT?
Operational acceptance testing (OAT) checks whether the operations and support teams can run the system in production: backup and restore, failover, monitoring and alerts, batch job scheduling, performance under expected load, security patching and support procedures. UAT checks whether business users can do their work. Both are needed before go-live. A system can pass UAT and still fail in production if nobody tested that the nightly batch finishes before the business opens.
23
Your analysis contradicts a strongly held belief of the vice president. How do you handle it?
Double-check the data and method first, and ask a peer to review it. Then share it privately with the VP before any group meeting, so they are not surprised in public. Present it neutrally: what we expected, what the data shows, and possible reasons. Invite their context, as they may know factors you missed. Suggest a small test to settle it. Focus on the decision, not on being right.
24
What is incremental refresh and when do you need it?
Incremental refresh partitions a large table by date so each refresh reloads only recent data, such as the last 10 days, while older partitions stay stored. You define RangeStart and RangeEnd parameters in Power Query, filter the date column with them, and set the policy for how much history to keep. It is needed when full refreshes of millions of rows take too long or fail, and it reduces load on the source system.
25
What is root cause analysis and which techniques do you know?
Active Customers 30D =
CALCULATE(
DISTINCTCOUNT(Sales[CustomerID]),
DATESINPERIOD('Date'[Date], MAX('Date'[Date]), -30, DAY)
)
-- MAX('Date'[Date]) makes it relative to the date in the current filter
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.
29
Your process diagram has grown to 80 shapes on one page and stakeholders say they cannot read it. What do you do?
Restructure it into levels. Create a high-level map with 7 to 10 main steps, then collapse detailed parts into sub-processes with their own diagrams. Move complex decision logic into a decision table rather than chains of gateways. Show the happy path first and handle exceptions in separate views. Use consistent naming in verb-noun form and remove duplicated steps. Finally, test readability by asking a stakeholder to explain the diagram back to you.
30
What is the difference between zero-based budgeting and incremental budgeting?
Incremental budgeting takes last year's budget and adjusts it by a percentage, which is quick but carries forward old inefficiencies. Zero-based budgeting starts every cost line from zero, and each activity must be justified by its value each cycle. ZBB uncovers waste and suits cost-reduction programmes, but takes much more effort and can create friction. Many companies apply ZBB to discretionary costs such as marketing and travel and use incremental methods elsewhere.
Check market size (population, online ordering share), competition, restaurant supply, unit economics per order, CAC and payback period. Propose a pilot with clear success metrics.
32
A report query on a 200 million row table takes 15 minutes. How do you optimise it?
Read the execution plan to find full scans and expensive joins. Filter early on partitioned or indexed columns such as date, select only needed columns instead of SELECT *, and avoid functions on filter columns. Pre-aggregate in a CTE before joining, replace correlated subqueries with joins or window functions, and check join keys have matching types. For repeated use, build a summary table or materialised view refreshed daily.
33
A Tableau dashboard on a 50 million row data source responds slowly to filters. How do you fix it?
Use an extract with only the needed columns and rows, aggregated to the visible grain where possible. Replace quick filters showing all values with fewer filters, use context filters wisely and avoid 'only relevant values' on large fields. Move complex calculations into the data source, reduce marks per view and the number of sheets per dashboard. Use the Performance Recorder to find the slowest queries and fix those first.
34
Your TO-BE process cuts the account-opening cycle time by half, but the compliance team rejects it. How do you handle it?
Ask compliance which specific controls they believe are weakened, and map each regulatory requirement to steps in the old and new flows. Often the control can be kept in a different form, such as automated checks, risk-based sampling or a post-approval audit instead of a manual pre-check. Bring compliance into the redesign rather than presenting a finished model. Document the agreed controls in the TO-BE diagram so audit can trace them. Speed never overrides a mandatory control.
Start from the test cases and list the data each needs: customer types, product variants, edge values and historical records. Decide whether to use masked copies of production data, synthetic data or both, because real personal data must be anonymised under data protection rules such as the DPDP Act. Prepare data for negative and boundary cases, keep a refresh plan for repeated cycles, and assign owners. Poor test data is one of the most common causes of blocked UAT days.
36
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.
37
What is the novelty effect, and why should A/B tests run for full weeks?
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.
IRR (internal rate of return) is the discount rate at which a project's NPV becomes zero, so it expresses the return as a percentage. NPV gives the value created in rupees at a chosen discount rate. Accept a project if IRR exceeds the cost of capital or NPV is positive. When comparing projects of different size or timing, NPV is more reliable, because IRR ignores scale and can give multiple answers when cash flows change sign more than once.
39
A feature launched two months ago is used by only 4 percent of users. What would you do?
Find out whether it is a discovery problem or a value problem. Check how many users saw the entry point, how many tried it and how many returned. If few saw it, test better placement or onboarding prompts. If many tried and few returned, interview users and review session recordings to understand why. Also check if the 4 percent are high-value users. Then decide to improve, reposition or remove it.
40
What is a process flow and which tools do you use?
A diagram of steps, decisions and owners in a process, made using BPMN or flowcharts in tools like Visio, Lucidchart or draw.io.
Frequently asked questions
What do Business Analytics interviews for ₹50+ LPA roles test?
At ₹50+ LPA the focus is usually on: very deep expertise and original thinking, large-scale trade-offs and failure modes, track record of measurable impact, leadership principles and culture fit. This page's set is weighted towards Stakeholder Communication (9), Business Metrics and KPIs (6), Product Analytics (6), Case Studies and Guesstimates (4).
Which companies pay ₹50+ 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 ₹50+ 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 ₹50+ LPA.