Walmart Business Analytics Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Walmart hiring for Business Analytics roles
Walmart is a global retailer operating stores and e-commerce, and it owns Flipkart and PhonePe in India. Walmart Global Tech India in Bengaluru and Chennai builds software, data and analytics solutions for Walmart's global businesses. It hires for software engineers, SDETs, data engineers, data scientists and analysts working on supply chain, pricing and customer platforms.
For Business Analytics roles, this Walmart practice set focuses most on SQL for Business Analysis (7), UAT and BA Documentation (6), Product Analytics (5), Case Studies and Guesstimates (5). It has 4 easy, 28 medium, 8 hard questions, so you can start easy and work up to the harder ones.
Company type
E-commerce & consumer tech
Headquarters
Bentonville, Arkansas, USA
Main India offices
Bengaluru, Chennai, Gurugram
Walmart Business Analytics interview process
Online coding assessment
Technical round 1 (DSA)
Technical round 2 (design or domain)
Hiring manager round
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for WalmartStart 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
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
02
Prepare a simple cost-benefit analysis for automating invoice processing.
Costs: software 12 lakh in year 1 plus 3 lakh per year support, and 4 lakh for implementation and training. Benefits: 60,000 invoices a year at 10 minutes saved each is 10,000 hours; at 400 rupees per hour that is 40 lakh, plus around 5 lakh from fewer late-payment penalties. Year-1 net benefit is 45 - 16 = 29 lakh and payback is under six months. Then test sensitivity, for example if only half the time saving is realised.
03
UAT starts tomorrow, but the business has not nominated any testers. What do you do?
Escalate immediately to the business sponsor with the impact: each day without testers delays sign-off and go-live. Ask for named testers with protected time, even part-time. Meanwhile, prepare so no time is lost: finalise test cases, check the environment and data, and plan a short tester briefing. If testers cannot be released, propose re-planning UAT dates rather than letting IT or the BA test on the business's behalf, because acceptance must come from the users.
04
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.
UAT sign-off is the formal acceptance by the business that the solution meets agreed requirements and is fit to go live, often with a list of known open defects and agreed workarounds. It should be given by the accountable business owner or product owner, not by the IT team or the BA. The BA prepares the evidence: test execution summary, defect status and traceability to requirements. Sign-off is recorded in writing, usually by email or in the test management tool.
06
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.
07
What is the profit equation and how do you use it in cases?
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;
09
Write a SQL query that shows revenue per region with one column per quarter.
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;
10
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.
11
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.
12
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
13
Write a SQL query to find requirements that have no linked UAT test case.
SELECT r.req_id, r.title, r.priority
FROM requirements r
LEFT JOIN test_case_links l ON l.req_id = r.req_id
WHERE l.req_id IS NULL
AND r.status = 'APPROVED'
ORDER BY r.priority;
-- Run this before UAT starts: every approved requirement
-- should trace to at least one test case.
14
An order has a value of 600 rupees, product cost 360, delivery 60, payment fee 12 and a discount of 50. What is the contribution margin?
Net revenue after discount is 600 minus 50, which is 550 rupees. Variable costs are 360 plus 60 plus 12, totalling 432. Contribution margin is 550 minus 432, so 118 rupees per order, or about 21 percent of net revenue. This is what each order contributes towards fixed costs such as salaries and rent. If the discount were raised to 150, the order would contribute only 18 rupees.
15
In UAT cycle 2, a feature that passed in cycle 1 is now broken after a defect fix. What does this tell you and what should change?
It is a regression: the fix for one defect broke existing functionality, which usually means changes were not impact-analysed and there is no regression suite. Log it as a new high-priority defect linked to the fix. Agree with the team that every UAT build comes with release notes listing the changes, and that QA runs an automated or core manual regression pack before handing the build to business testers. Also add the broken flow to the UAT regression checklist.
16
What is the difference between Definition of Ready and Definition of Done?
Definition of Ready is a checklist a story must meet before the team pulls it into a sprint: clear description, acceptance criteria, dependencies identified, designs attached and estimated. Definition of Done is the checklist for calling work complete: coded, reviewed, tested, acceptance criteria passed, documented and deployable. The BA mostly drives readiness, while the whole team owns done. Both reduce rework and arguments at sprint end.
17
Control has 10,000 users with 400 purchases and the variant has 10,000 users with 460 purchases. Calculate the lift.
Control conversion is 400 divided by 10,000, which is 4.0 percent. Variant conversion is 460 divided by 10,000, which is 4.6 percent. The absolute lift is 0.6 percentage points and the relative lift is 0.6 divided by 4.0, which is 15 percent. Before calling it a win, run a two-proportion significance test and check the confidence interval and guardrail metrics.
AARRR breaks the customer lifecycle into five stages: Acquisition, how users find you; Activation, their first good experience; Retention, whether they come back; Referral, whether they recommend you; and Revenue, whether they pay. Each stage gets one or two metrics, such as sign-ups by channel, activation rate, Day-30 retention, invite rate and conversion to paid. It helps find which stage is the weakest bottleneck.
19
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.
20
Guesstimate: how many weddings take place in India in a year?
Assume a population of about 144 crore and an average life expectancy of about 70 years, so roughly 2 crore people reach a typical marriage age each year. If about 95 percent of them marry at some point, that is around 1.9 crore people, or about 95 lakh weddings, since each wedding involves two people. A reasonable estimate is around 1 crore weddings per year, concentrated in the winter wedding season.
21
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.
22
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.
23
A stakeholder keeps skipping review meetings and then rejects the deliverable at the end. How do you prevent this?
Talk to them one-to-one to understand why they skip, such as timing, relevance or workload. Offer shorter reviews, asynchronous reviews with a clear deadline, or a delegate with decision rights. Record sign-offs at each stage in writing so late changes become formal change requests. Share early drafts and mock-ups, because people react better to something visible. Escalate to the sponsor if the pattern risks the timeline.
24
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.
Define completion and see where learners drop: first week, a specific module or before assessments. Segment by course, length, learner background, device and acquisition channel. Look at causes in content difficulty, video length, lack of deadlines, mentor support and job relevance. Recommend tests such as shorter modules, cohort-based deadlines, progress nudges and live doubt sessions, and measure completion and referral impact.
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;
29
Guesstimate: how many cups of tea are sold in Delhi per day?
Population about 20 million, adult tea drinkers about 50%, cups bought outside per person around 1 on average. This gives roughly 10 million cups, then adjust for offices and stalls.
30
What does expectation management mean for a business analyst?
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.
31
How do you write an effective executive summary for an analysis report?
Put it first and keep it to one page or five lines on a slide. Start with the answer or recommendation, then the two or three key findings that support it, each with a number, then the impact in rupees or percentage, and finally the decision or action needed and by when. Avoid methodology details, which go in the appendix. Test it by asking whether a busy leader could act after reading only this section.
32
Write a UAT test case for logging in to a banking app with OTP.
Test case ID: UAT-LOGIN-03. Precondition: registered customer with a verified mobile number. Steps: 1. Open the app and enter the registered mobile number. 2. Tap Send OTP. 3. Enter the 6-digit OTP received by SMS within 3 minutes. 4. Tap Verify. Expected result: the customer lands on the account dashboard, and the login is recorded in the activity log. Related negative cases: wrong OTP shows an error, and three wrong attempts lock login for 30 minutes.
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.
35
Tell me about a time UAT revealed a major issue that earlier testing missed.
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.
36
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.
37
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.
38
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.
39
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.
40
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;
Tips to crack the Walmart Business Analytics interview
Think about retail problems like inventory forecasting, store replenishment and pricing, which Walmart data teams commonly work on.
Practise DSA and SQL questions together, since many roles combine coding with data handling.
Read Walmart's values of Respect for the Individual, Act with Integrity, Serve Our Customers and Strive for Excellence.
Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
Practise the hard questions on this page aloud; Walmart interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Walmart Business Analytics interview?
Candidates usually go through 5 stages: Online coding assessment; Technical round 1 (DSA); Technical round 2 (design or domain); Hiring manager round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Walmart Business Analytics interview?
This practice set leans on SQL for Business Analysis (7), UAT and BA Documentation (6), Product Analytics (5), Case Studies and Guesstimates (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Walmart interviewers ask you to walk through real work.
Are these the exact questions asked at Walmart?
No. These are curated practice questions that match the skills and difficulty usually tested in e-commerce & consumer tech interviews like Walmart's. They are not a leaked or verified list of past questions.
Where does Walmart hire Business Analytics professionals in India?
Walmart has large teams in Bengaluru, Chennai, Gurugram. Openings and locations change often, so check the Walmart careers page and filter by city and experience.
Business Analytics questions for similar companies