
Walmart Software Engineer interviews typically pair a recruiter screen with a timed technical assessment (often Karat, Glider, or an online OA), one or more DSA-focused coding rounds, a system design conversation, and behavioral questions, though the exact number and order of rounds varies by team and hiring event.
$125K
Avg. Base Comp
$203K
Avg. Total Comp
2-6 rounds
Typical Rounds
Not reported
Process Length
Walmart's Software Engineer interviews are notably inconsistent in format, and the clearest theme across candidate reports is how heavily the company relies on third-party assessment platforms — Karat and Glider both appear repeatedly, sometimes alongside more traditional recruiter-and-hiring-manager loops. Several candidates describe a Karat round as the first real technical gate, staffed by an interviewer unaffiliated with the hiring team, where a medium-difficulty HashMap or LeetCode-style problem is common; more than one report specifically flags vague instructions in these rounds, so restating requirements before coding is worth doing deliberately.
Beyond the assessment stage, technical rounds most often center on core data structures and algorithms — HashMaps and collision handling, LRU caches, BSTs, graph/cycle detection, and sliding-window string problems recur across many accounts — typically paired with a system design conversation on topics like a real-time inventory/stock-status service, a contact-tracing app, or an Uber-style ride-hailing design. Java fundamentals (OOP, concurrency, Spring Boot, and the Stream API) come up often enough that candidates without a strong Java background report being caught off guard, even when the job posting didn't emphasize the language. Behavioral questions are a near-constant presence, usually framed around teamwork, conflict resolution, and customer-facing scenarios rather than pure culture-fit chat, and for full-stack postings, recruiters may ask directly about comfort with frontend-heavy work.
Because the process clearly varies by team, hiring event, and whether the role is full-stack, backend, or contractor, treat any single candidate's round-by-round description as one data point among several rather than a fixed script. Practicing a couple of medium DSA problems, rehearsing a system design walkthrough, and preparing concrete stories about past project trade-offs covers most of what's actually been reported.
Synthesized from 46 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Walmart process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Walmart
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Subscription Overlap | |
| Customer Orders | |
| Top 3 Users | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Last Transaction | |
| P-value to a Layman | |
| Triplet Counting | |
| Groups of Anagrams | |
| Longest Increasing Subsequence | |
| Cumulative Sales Since Last Restocking | |
| Valid Anagram | |
| Hurdles In Data Projects | |
| Order Addresses | |
| Highest Average | |
| Black Friday Shopping Spree | |
| Rider Discount | |
| Seasonal Product Performance Analysis | |
| Type I and II Errors | |
| Check Matching Parentheses | |
| Moving Window | |
| Employee Benefits Outreach | |
| Deciding Between Solutions | |
| Scalable Data Pipelines | |
| Testing Constraints | |
| Marketing Workflow Optimization | |
| Client Solution Pushback |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates report an initial recruiter or HR phone screen covering background, project experience, compensation expectations, location preferences, sponsorship status, and availability. For intern and some full-time roles, recruiters may also discuss team matching and which teams a candidate could join before scheduling technical rounds.
A large share of candidates go through a timed technical assessment before speaking with the hiring team directly, often via a third-party platform such as Karat or Glider, or a self-scheduled online assessment with two algorithmic problems in roughly 80 minutes. These rounds typically include a medium-difficulty coding problem (HashMap, string, or array-based), and candidates report that some prompts are worded vaguely, so clarifying requirements before coding matters.
Live coding rounds most commonly test core data structures and algorithms — HashMaps with collision handling, LRU caches (including thread-safety variants), BSTs, graph or cycle-detection problems, and sliding-window string or array manipulation. Interviewers typically care as much about communicating an approach and discussing time/space trade-offs as about reaching a fully working solution.
Many loops include a separate system design round, with reported prompts ranging from a real-time inventory and stock-status service to a contact-tracing app and Uber-style ride-hailing designs. Candidates describe this stage as open-ended, often touching caching, regional outages, and write conflicts, and it may be combined with stack-specific questions on Java Spring Boot or concurrency rather than kept purely architectural.
Nearly every account includes a behavioral component, whether as a standalone round or folded into a manager conversation. Common topics are past project ownership, handling disagreement or difficult customers, and why Walmart; full-stack candidates report being asked directly about comfort with frontend-heavy work. A few candidates note this round unexpectedly shifting into more system design or stack-specific questioning.
Later-stage loops often include a hiring manager or panel round that revisits resume projects and prior work, sometimes split across multiple 20-40 minute segments covering different parts of the stack, such as Java/OOD, SQL with indexing, and React/JavaScript. Candidates report team- and manager-dependent variation in tone and depth, so the exact mix is not uniform across postings.