Companies / Walmart Global Tech

Walmart Global Tech practice pack

Product company. 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.

Skills this role is usually tested on

  • API and contract testing
  • Java automation
  • Data and pricing correctness
  • CI/CD
  • Test strategy

Business areas used for scenarios

  • retail
  • e-commerce
  • supply chain

6 questions

Answer out loud first, then open the guide. Most people read the guide too early.

  1. 1

    A store shelf shows an item in stock but the app says unavailable. What could be wrong and how do you test for it?

    mediumDomain

    A strong answer covers

    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.

  2. 2

    Two teams change an inventory API independently. How do you stop breakage?

    hardContract testing

    A strong answer covers

    Consumer-driven contract tests in each pipeline, versioning rules, backward-compatible changes only, and a deprecation window with usage telemetry.

  3. 3

    Write a Java method to group a list of orders by store and return the total per store. What would you test?

    mediumJava

    A strong answer covers

    Streams with groupingBy and summingDouble or BigDecimal for money. Tests: empty list, one store, null store, negative amounts, rounding.

  4. 4

    How do you test a price change that must apply at exactly midnight in many time zones?

    mediumPricing

    A strong answer covers

    Control the clock, test just before and after in each zone, daylight-saving shifts, cached prices, in-flight carts, and receipts.

  5. 5

    Design regression for pick-up-in-store orders across app, web, store systems and payments.

    hardStrategy

    A strong answer covers

    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.

  6. 6

    Your pipeline takes 90 minutes and developers skip it. What do you change?

    mediumCI/CD

    A strong answer covers

    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.

Now say it to an interviewer

Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.

Start a mock interview Build a plan from a job description