Business Analytics Interview Questions for Managers (₹30–40 LPA)
40 questions with answers for managers — 19 medium, 21 hard.
What ₹30–40 LPA interviews expect
People management and hiring Delivery and risk management Budget and stakeholder alignment Vision and long-term planning
About ₹30–40 LPA Business Analytics roles
Roles in the ₹30–40 LPA band are typically for managers. Interviewers check whether you can already do the work expected at this level, so questions here are weighted towards Case Studies and Guesstimates (8), SQL for Business Analysis (7), Product Analytics (6), Requirements and Agile (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
How would you analyse the declining sales of a retail store?
Growth came from more value per customer, not more customers. Break revenue into customers times orders per customer times average order value to see which moved. It could be price increases, larger baskets, a shift to premium products or a few large accounts. Then check risks: is new customer acquisition stalling, is churn being masked, and is growth concentrated in a small segment that could leave?
03
What do statistical significance and p-value mean in an A/B test?
The p-value is the probability of seeing a difference at least as large as observed if the change truly had no effect. If it is below the chosen threshold, often 0.05, the result is called statistically significant. It does not mean there is a 95 percent chance the variant is better, and significance is not the same as business importance. Always report the confidence interval of the lift as well.
04
Describe a time you had to present disappointing numbers to leadership.
Situation: a new city launch was 30 percent below its order target after two months. Task: present the review to the leadership team. Action: I opened with the number directly, then broke the gap into traffic, conversion and repeat rate, showing repeat rate was the main problem. I came with three options with estimated impact and cost. Result: leadership approved a focused retention campaign instead of more ad spend, and repeat rate rose over the next quarter.
05
Leadership wants to automate an invoice approval process with RPA. What do you check in the process model before agreeing?
Check that the process is stable, rule-based and high volume, with structured digital inputs. Look at the variant rate: if half the cases are exceptions handled by judgement, a bot will fail often. Verify that the underlying systems and screens will not change soon. Fix the process first, because automating a broken flow only makes errors faster. Finally estimate hours saved against bot build and maintenance cost, and define how exceptions get routed to people.
06
How do you estimate the annual revenue of a coffee shop chain?
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.
Send an agenda with the goal and the decisions needed beforehand, along with any pre-read. Invite only people who contribute or decide. Start by restating the goal, keep to time, park off-topic issues and confirm decisions aloud. End by summarising actions with owners and dates. Send minutes within a day. A meeting without a clear decision or output usually could have been an email.
09
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.
10
Write Excel formulas to find the second-highest sales value and the name of the rep who achieved it.
// second highest value
=LARGE(C2:C100, 2)
// rep name for that value
=INDEX(B2:B100, MATCH(LARGE(C2:C100, 2), C2:C100, 0))
// with ties, SORTBY gives a clean list:
=TAKE(SORTBY(B2:C100, C2:C100, -1), 2)
11
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.
12
How do you calculate cycle time, touch time and process efficiency? Give an example.
Cycle time (lead time) is the total elapsed time from the start to the end of a case. Touch time is the time someone actually works on it. Process cycle efficiency is touch time divided by cycle time. Example: a refund takes 5 working days (40 working hours) end to end, but the agents spend only 2 hours in total working on it. Efficiency is 2 / 40 = 5 percent, so 95 percent of the time is waiting, and queues are the main target.
13
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.
14
Tell me about a time you discovered a missed requirement late in a project.
Situation: two weeks before go-live of a billing system, a finance user asked how GST credit notes would work, which we had not covered. Task: assess and recover. Action: I analysed the impact with developers, found a simple configuration path for most cases plus a manual step for rare ones, and presented both options with dates to the sponsor. Result: we went live on time with a documented workaround and delivered the full fix next sprint.
15
Guesstimate: how many cars are sold in India every year?
Structure it: households × car-owning share ÷ replacement cycle + first-time buyers + commercial fleet. State each assumption clearly and sanity-check the final number.
16
Write a DAX measure that shows each category's percent share of total sales.
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.
18
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.
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;
20
Write a SQL query for the top 3 products by revenue in each category.
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;
21
Because of a tight deadline, the business sponsor wants to skip UAT and go live directly. How do you respond?
Explain the risks in business terms: without UAT, there is no evidence that real processes work, and production defects cost far more to fix and can affect customers and compliance. Offer alternatives: a shortened UAT covering only critical business flows, parallel running with the old system, a phased rollout to one branch or user group, or extended hypercare. If the sponsor still decides to skip it, record the decision and accepted risks formally.
22
Write a SQL query for Day-7 retention by weekly sign-up cohort.
WITH cohort AS (
SELECT user_id, signup_date,
DATE_TRUNC('week', signup_date) AS cohort_week
FROM users
),
ret AS (
SELECT DISTINCT c.user_id
FROM cohort c
JOIN events e ON e.user_id = c.user_id
AND e.event_date = c.signup_date + INTERVAL '7 day'
)
SELECT c.cohort_week, COUNT(*) AS users,
ROUND(100.0 * COUNT(r.user_id) / COUNT(*), 1) AS d7_retention_pct
FROM cohort c
LEFT JOIN ret r ON r.user_id = c.user_id
GROUP BY c.cohort_week
ORDER BY c.cohort_week;
23
Your LEFT JOIN report should list all customers, but customers without orders are missing. Why?
A condition on the right table was probably placed in the WHERE clause, for example WHERE o.order_date >= '2026-01-01'. For customers with no orders, o.order_date is NULL, so WHERE removes them and the query behaves like an INNER JOIN. Move the condition into the ON clause, as in LEFT JOIN orders o ON o.customer_id = c.id AND o.order_date >= '2026-01-01', or explicitly allow NULLs.
24
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.
25
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.
26
Tell me about a time a SQL query you wrote gave wrong results. How did you catch it?
Situation: my weekly sales report showed a 12 percent jump that no one could explain. Task: verify the number before it reached leadership. Action: I compared row counts before and after each join and found a new promotions table had multiple rows per order, duplicating revenue. I aggregated promotions per order first and added a test comparing totals with the source. Result: the corrected report went out the same day, and I now check grain on every new join.
27
Write a SQL query to calculate the repeat purchase rate.
WITH per_customer AS (
SELECT customer_id, COUNT(DISTINCT order_id) AS orders
FROM orders
GROUP BY customer_id
)
SELECT
ROUND(100.0 * SUM(CASE WHEN orders >= 2 THEN 1 ELSE 0 END)
/ COUNT(*), 2) AS repeat_rate_pct
FROM per_customer;
28
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.
29
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.
30
A bank wants to reduce customer churn. What would you do?
Define churn, analyse who leaves and why, segment customers, find drivers through data and surveys, design retention offers and measure uplift with a control group.
31
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.
32
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.
33
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.
34
What techniques do you use to elicit requirements?
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.
36
A mid-size manufacturer must choose between building and buying a warehouse management system. How do you advise?
Compare options on fit, cost, time and risk. Buying a proven product is faster with lower risk and includes upgrades, but may need process changes and has recurring licence fees. Building fits unique processes exactly but needs a strong tech team, longer time and ongoing maintenance. Estimate five-year total cost of ownership, check whether processes are truly unique, and usually recommend buying and configuring unless warehousing is a core differentiator.
37
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.
38
How do you write a query to find users active in consecutive months?
Understand the urgency and the business impact of waiting until the next sprint. Bring it to the product owner, who decides. If it truly cannot wait, the team agrees to swap out work of similar size so the sprint goal stays realistic, and the trade-off is made visible to the stakeholder. If it can wait, add it to the top of the backlog for the next sprint. Avoid silently adding scope.
Frequently asked questions
What do Business Analytics interviews for ₹30–40 LPA roles test?
At ₹30–40 LPA the focus is usually on: people management and hiring, delivery and risk management, budget and stakeholder alignment, vision and long-term planning. This page's set is weighted towards Case Studies and Guesstimates (8), SQL for Business Analysis (7), Product Analytics (6), Requirements and Agile (4).
Which companies pay ₹30–40 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 ₹30–40 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 ₹30–40 LPA.