Product company
Walmart Global Tech
Retail platform testing: inventory, pricing, and omni-channel flows.
These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.
What they tend to probe
- API and contract testing
- Java automation
- Data and pricing correctness
- CI/CD
- Test strategy
Question 1 · Domain · Medium
A store shelf shows an item in stock but the app says unavailable. What could be wrong and how do you test for it?
Answer guide
Inventory sync delay, reservation holds, rounding of stock counts, store vs warehouse source, caching, and event ordering. Test with controlled stock changes and compare each system.
Question 2 · Contract testing · Hard
Two teams change an inventory API independently. How do you stop breakage?
Answer guide
Consumer-driven contract tests in each pipeline, versioning rules, backward-compatible changes only, and a deprecation window with usage telemetry.
Question 3 · Java · Medium
Write a Java method to group a list of orders by store and return the total per store. What would you test?
Answer guide
Streams with groupingBy and summingDouble or BigDecimal for money. Tests: empty list, one store, null store, negative amounts, rounding.
Question 4 · Pricing · Medium
How do you test a price change that must apply at exactly midnight in many time zones?
Answer guide
Control the clock, test just before and after in each zone, daylight-saving shifts, cached prices, in-flight carts, and receipts.
Question 5 · Strategy · Hard
Design regression for pick-up-in-store orders across app, web, store systems and payments.
Answer guide
Map the journey and the systems, contract tests at boundaries, a thin set of end-to-end flows, failure cases (late pick, partial stock), and monitoring in production.
Question 6 · CI/CD · Medium
Your pipeline takes 90 minutes and developers skip it. What do you change?
Answer guide
Split by speed, parallelise, run only affected tests on pull requests, move slow checks to merge or nightly, fix flaky tests, and publish time per stage.