Interview Experience - 103 -Walmart | Software Development Engineer 2 | L2
Summary
📌 Job Role: Software Development Engineer
🔢 Number of Rounds: 5
📜 Offer Status: Offer
📍 Location: Bangalore
👤 Candidate Name: Not disclosing due to signed NDA
Interview Process
The interview process at Walmart consisted of 5 rounds:
Coding and Problem Solving
System Design, Database, and Technical Questions
Low-Level Design and Technical Questions
Hiring Manager Round
HR Round
After submitting the necessary documents on April 18th, 2025, there was a delay in the offer release. I followed up with a competing offer from Paytm on May 2, 2025, which helped expedite the process. Eventually, the offer was rolled out.
Preparation Guide
There wasn’t a single consolidated source I relied on, but the preparation was aligned to the following key areas:
Practiced DSA questions regularly (mainly from LeetCode and custom problem sets).
Read up on design patterns, Spring framework annotations, and LLD concepts using real-world system examples.
Studied system design through online videos and blogs, covering database choices, scalability, and resilience.
Refreshed knowledge on tools like Kibana, Grafana, and Kubernetes.
Stayed updated with recent vulnerabilities like Log4j and deployment best practices.
Interview Rounds
🟢 Round 1: Coding and Problem Solving
Duration: 60 minutes
Difficulty Level: Medium
Experience:
This was a problem-solving round focused purely on coding skills. The questions were:
Find max and min in a bitonic sequence
A bitonic sequence is one which first increases and then decreases. I was expected to return both max and min efficiently.Playlist implementation
I had to design a playlist that selects a random song from a list of 50 songs, ensuring that the song is not one of the last 10 played. If a randomly selected song is in the last 10, the system should pick another.
Both problems tested my ability to think under constraints and implement clean, logical solutions.
Key Learnings:
Always clarify edge cases with the interviewer.
For such problems, thinking about the time complexity and space constraints upfront helps in narrowing down the optimal approach.
🟡 Round 2: System Design and Technical Questions
Duration: 60–75 minutes
Difficulty Level: Difficult
Experience:
This round was broader in scope and covered various aspects of system design, scalability, resilience, security, and infrastructure. Questions included:
Design a data structure supporting insert, delete, search, and getRandom in constant time.
When to use SQL vs NoSQL, along with pros/cons.
How to scale an application?—horizontal vs vertical scaling.
How to build application resilience? Techniques like circuit breaking, rate limiting, etc.
Discussion around the Log4j vulnerability and how it affected the ecosystem.
Use of Kibana/Grafana for metrics visualization and alerting.
Additional questions on Kubernetes deployments and DevOps concepts.
The interviewer (from IN4) seemed distracted during the session, which disrupted the flow. This impacted the depth of discussion, and I came out of the round feeling it didn’t go well.
Key Learnings:
In system design rounds, having a structured approach helps: define the problem, list constraints, discuss components, and scale.
Keep answers focused even if the interviewer gets distracted.
Prepare to adapt quickly to a less interactive environment.
🟡 Round 3: Low-Level Design and Technical Questions
Duration: 60 minutes
Difficulty Level: Medium
Experience:
After the previous round didn’t go well, HR informed me that the Hiring Manager wanted to give me another opportunity. This round was a mix of low-level design and technical Spring framework-related questions.
Topics covered:
Design a Library Management System
I implemented it using the Command Design Pattern, which I had recently used in one of my projects.Discussion on database choices, based on consistency, read/write patterns.
Asked about design patterns used in my recent work.
Differences between
@Componentand@Serviceannotations in Spring.Whether Beans can be instantiated in a static method and related implications.
Key Learnings:
Using real project examples when discussing design patterns or architecture makes a strong impact.
Knowledge of Spring internals and annotations is often tested in backend-focused roles.
🟡 Round 4: Hiring Manager Round
Duration: 60 minutes
Difficulty Level: Medium
Experience:
This round was a mix of project-level discussions and behavioral aspects, with some technical follow-ups.
Detailed questions about my current project, stack used, challenges faced, and architecture decisions.
Follow-up questions on:
Docker Compose
Spring Cache mechanisms
Aspects in Spring
Discussion around career motivations and why I was looking for a switch.
Key Learnings:
Be ready to deep dive into your current work. The Hiring Manager is often trying to assess not just your tech stack familiarity, but also how you approach real-world problems.
Motivation questions are common—be authentic and aligned with the company's vision.
🟢 Round 5: HR Round
Duration: 45 minutes
Difficulty Level: Easy
Experience:
The final round was a typical HR discussion with some thought-provoking questions.
How do you see yourself contributing to Walmart's growth over the next 5 years?
General behavioral questions to understand team fit, adaptability, and work ethics.
Detailed compensation discussion and negotiation.
Key Learnings:
Be prepared to articulate your long-term goals and how they align with the company.
HR may also validate your understanding of the company’s culture and expectations.
Final Thoughts
Here are a few key takeaways from my Walmart interview journey:
Consistency across rounds is important, but even if one round doesn't go well, there might still be opportunities if you're proactive and prepared.
System design rounds are broad—focus on clarity, structure, and practical trade-offs.
Preparation around backend frameworks (especially Spring in Java-based roles) pays off in technical deep-dives.
Stay up-to-date with real-world incidents like Log4j or Docker-related vulnerabilities. These can pop up in interviews.
Don't underestimate HR rounds—they are often the final gatekeeper and can impact the final offer and role expectations.