Walmart Interviews

First round was two DP problems. The first problem was similar to Combination Sum, but with unique elements instead of duplicates. The second problem was Target Sum.

Second round focused on LLD and HLD, where I was asked to design BookmyShow and draw entities and relationships. I cleared this round.

Third round was about designing a Rate Limiter and its LLD. I wasn't able to implement the LLD for this, which led to rejection.

My interview journey at Walmart started with an in-person DSA round, which was part of a hiring drive. I was presented with two problems. The first was Copy List with Random Pointer. I initially implemented the hashmap-based approach, but the interviewer challenged me to find an O(1) space complexity solution. I couldn't figure it out on the spot and only realized the interleaving solution after the interview. The second problem was Word Search.

The second round was a virtual Low-Level Design interview. The problem given was LFU Cache. I discussed my approach in detail and then wrote the code. This round felt quite similar to a DSA round in its nature.

Following that, I had a virtual System Design round. Here, I was asked to design a dynamic pricing system, which involved discussions around various components and considerations.

The final round was a virtual Hiring Manager discussion. This round primarily focused on standard behavioral and situation-based questions, delving into my experience and how I would handle different scenarios.

Overall, I found the interview process to be good, and my recruiter was incredibly helpful and accommodating throughout. The only slightly annoying part was the company's strong push to complete all rounds very quickly, but then it took them 2.5 weeks to extend the offer after the process had concluded. I ultimately decided to decline the offer.

I recently had an online technical interview for the Software Engineer III role at Walmart Global Tech, located in India. The interview comprised a single round focused on Data Structures and Problem-Solving, where I was given two LeetCode-style coding questions. Unfortunately, my journey ended after this round, as I was rejected.

Today I solved LeetCode 480: Sliding Window Median and wanted to share my learning journey, especially for interview preparation. My first attempt involved a simple brute-force approach using Python’s built-in sorted(). While this worked for small inputs, it unfortunately failed with a Time Limit Exceeded error on larger test cases. The reason was its O(nk log k) time complexity, making it not scalable for real-world interview scenarios.

My breakthrough came when I discovered SortedList from the sortedcontainers Python module. This powerful data structure maintains elements in sorted order automatically, offering efficient O(log n) insertion and deletion, O(1) access by index, and O(log n) search operations. By implementing SortedList, I was able to optimize my solution significantly, reducing the overall time complexity to O(n log k). This makes SortedList an ideal choice for problems requiring dynamic median finding, sliding window min/max, or finding the Kth largest/smallest element in a stream. I also learned that this exact problem, LeetCode 480, was recently asked in a Walmart R1 interview, which truly emphasized the importance of knowing such optimized techniques.

I recently interviewed for a Staff Android Design Engineer role at Walmart. The interview process consisted of two rounds.

My first round was with the Hiring Manager. We discussed my previous experiences and had a deep dive into my current work. We also touched upon my views on GenAI and the future of mobile technology, along with the reasons I was looking for a change.

The second round was focused on Android questions. This round presented a mix of questions covering the basics of Android. I was also given several code snippets and asked to identify possible faults and errors within them. Specific topics we discussed included a deep dive into RecyclerView internals and Layout Managers, the Garbage Collector and its impact on the main thread, concepts around Custom Views and Overdraw, strategies for avoiding Jank and Lags, and the use of Profilers and dealing with Memory Leaks. We also covered Coroutine Concepts, Fragment Transactions, concurrency, and questions related to lifecycleScope and LifecycleOwner. The team I interviewed with primarily used traditional XML views, so the questions were majorly focused in that area.

Ultimately, I was rejected after Round 2.

I recently interviewed at Walmart for a Software Engineer III (Java Backend Developer) role. Here's a breakdown of my experience:

Round 1: DSA

This round was with a Senior Software Engineer. After a quick introduction, we moved straight into problem-solving.

• Coin Change (Dynamic Programming): I discussed recursive with memoization and tabulation approaches, optimizing the solution and answering all follow-ups.
• Course Schedule (Graph / Topological Sort): I solved this using a BFS (Kahn’s Algorithm) approach. We also discussed DFS cycle detection as a follow-up.

I successfully solved both problems within the allotted time and cleared this round.

Round 2: Java + LLD

This round was with a Staff Software Engineer and was split into two parts.

Part 1: Java (20 mins)

We covered OOPS fundamentals, the internal workings of HashMap, multithreading concepts like the volatile keyword and its use cases, and some general Java basics.

Part 2: LLD

I was asked about design patterns I had used recently. We then had a deep dive into the Strategy Design Pattern. The interviewer presented a real-world scenario involving a Payment Gateway (UPI, Bank Transfer, etc.) where the strategy is selected at runtime. I implemented a basic code structure and handled follow-up questions effectively.

This round felt like I performed somewhere between average and above average. I'm currently waiting for HR confirmation; if cleared, the next step will be the Hiring Manager Round.

Overall, the interviewers were friendly and focused on a deep understanding of concepts. The DSA round involved standard LeetCode medium-level problems, and in the LLD round, a clear explanation of design choices was more crucial than just writing code. I'll update once I hear back from HR.

I recently went through an interview process for the Software Engineer III position at Walmart Global Tech in Bangalore. The entire process, which was initiated through a referral, comprised three in-person rounds completed within a single day. With 3 years of experience as an SDE-II, I felt well-prepared for the challenges.

Round 1 – DSA Coding Round
This round focused on medium to medium-hard DSA questions, covering topics such as Trees (traversals, path-based problems), Two Pointers, Sliding Window, and Binary Search variations. The interviewer expected a clear explanation of my approach, starting from brute force to an optimized solution, along with thorough handling of edge cases and detailed time & space complexity analysis. I successfully cleared this round and advanced.

Round 2 – Low-Level + System Design
This was an engaging open discussion covering both system design and core Java concepts. The interviewer assessed my problem-solving approach, thought structuring, and ability to extend solutions. We discussed data modeling, API design for extensibility, and step-by-step system scaling. Specific Java concepts like Multithreading, concurrency handling, and synchronization were also covered, alongside Design Patterns and SOLID principles. Several sample design problems were discussed, including building an In-Memory Cache, an Email Notification System, a UPI-like Payment System, and a Ride Booking System. For this round, I was expected to provide code snippets where necessary, demonstrate how a design could evolve from basic to scalable, and apply appropriate design patterns. I successfully navigated this round as well.

Round 3 – Hiring Manager Round
The final round was a blend of technical and behavioral questions. We delved deep into my previous work experience and the projects listed on my resume. I answered questions about my tech stack (Java, system design, scalability aspects) and discussed decision-making and ownership in past projects. Some general AI/ML concepts were also brought up to gauge my awareness of trending technologies. Additionally, standard behavioral questions on teamwork, conflict resolution, and leadership were posed. The discussion felt conversational, focusing on my potential contribution to the team and growth within the role.

Finally, I was thrilled to receive an offer for the Software Engineer III position at Walmart Global Tech in Bangalore! It was a comprehensive, in-office interview experience that concluded swiftly.

I've meticulously collected and organized these interview questions to offer a detailed overview of what to expect in Walmart's technical rounds. This compilation aggregates problems reported by candidates across a spectrum of roles and experience levels, including SDE III, Senior SWE, and fresher positions. Some of the sources even specify locations like Bengaluru and recent interview dates up to December 2024. Each question is accompanied by its direct LeetCode link, facilitating easy access to the problem statement for focused practice. While the specific outcomes for all individual aggregated experiences are not universally detailed, one notable source explicitly mentions an offer, highlighting the relevance of these problems in successful interview journeys.

I recently interviewed for the SSE role at Walmart. The interview process did not include an online assessment and consisted of four distinct rounds.

My first round was focused on Data Structures & Algorithms, where I was presented with two medium-difficulty LeetCode-style questions. One involved a graph traversal using Depth-First Search (DFS), and the other required a binary search approach, specifically addressing a 'minimum of maximums' problem pattern.

The second round delved into Java and Low-Level Design. I was asked to design the database schema for a ticket booking application. Following this, there were several questions concerning the Java Collections framework, concepts within Spring Boot, and fundamental Java language basics.

The third round was a High-Level System Design interview. The primary task was to design an e-commerce application, with a particular emphasis on handling the purchase and return processes effectively.

Finally, the fourth round was a behavioral and managerial interview. This involved a deep dive into one of my past projects, where I discussed my contributions and challenges. Additionally, I answered several common behavioral questions typical of such interviews.

Round 1: DSA (60 mins)
They schedule this round but noboday joined I kept waiting for an hour. Reached out to recrutier via mail and phone, they didn't respond. But after half and hour she called and appolozied and re scheduled it fro next day.
1. Binary tree problem where two players are playing one starts from Root and another from any random node and root player can go down but other one can go up only at each step. Both are playing together, we have to maximize the score for player playing from root.
2. Course scheduling problem

Round 2: LLD + HLD (60 mins)
Started from going though resume. Then asked which java verion your company is using. Then asked what are new features in Java 17.
- Then gave problem Jukebox. I tried to clarify functionality, but interviewer was not at all engaging. I beleive his expectation was that someone will come with mugged up things and simply implement it and he will just ask few questions here and there. He was not at all ready to work along or atleast acknowledge on my analysis and thinking process with yes or no. He was just staring at your screen while you are trying to explain him that this is the requirement etc.
- He was switching context between HLD + DSA + LLD(OOPs) and all frequently for this problem. He never let me settle down into any direction, like should I go in high level desing or go into low level design. In last 15 mins he started asking random questions like how will you make it highly available, I started explaining, in the meantime he was scrolling his phone.
- Lession learnt from this round: You have to drive the interview and be ready for such situtaion where interviewer is not at all engaged with you, like you ask something still he is staring at your screeen, not even acknowleging by saying ok or something so that you can proceed.
- I knew I messed up this round still I followed up with recruiter next day and received rejection main finally 😃
- I felt so bad for 2 days as I prepared so hard for round 2 and round 1 went so so good. Studied all major concepts in depth so that if interviewer asks anything I can go into depth too, not just vague 1 sentence answers. I was so depressed, no mood to study anymore etc. As I'm continuosly grinding leetcode working on side projects along with HLD and LLD with my full time job since past 4 months and still no success.
- But somehow today I am feeling little bit ok so came here and posting it today.

Round 1 DSA Question 1: Based on searching in a sorted array Question 2: Based on DFS in 2D matrix

Round 2 LLD Question: Design Online Shopping Application

Round 3 HLD Question: Design Ticket Booking System

I applied directly on the career portal. A recruiter called to say that my profile was shortlisted for interviews for Software Engineer III - (Java with DevOps). She said that there will be 3 rounds of interviews, 2 virtual and the last round F2F in Bangalore. The first round was scheduled 2 days after the initial call.

Technical Round 1 (60 minutes)

Began with an introduction and asked why my project used microservices architecture instead of a monolith. Asked me how much I would rate myself in DSA. I said 8/10. He said he would give a medium question, then proceeded to give a variation of LC 295. Find Median from Data Stream.

After conveying my approach, I was instructed to code in Java and explain the time complexities. I fumbled a little while explaining how a heap data structure works internally. Then the last 15 minutes were questions from my resume.

1. Which design pattern would you use to decide the object at runtime?
2. Active-active vs active-passive architecture.
3. How to make sure that Kafka publishes events in the same partition?
4. Redis - Distributed cache working.
5. What are Reentrant Locks? Can they work with different objects?

In the end, I asked about the tools used in his team and for feedback. The feedback provided was to answer questions in more depth rather than just high level. Honestly, I was expecting a rejection, but got a call from HR the next working day saying that I had cleared Round 1.

Technical Round 2 (60 minutes)

This round was scheduled for 3 days later from the latest call. However, I was not provided the competencies despite asking. So I mentioned the same on the day of the interview to the recruiter when she had called, so she provided the competencies for this round and said that we can move the interview to next week. So I had almost another week to prepare.

Below were the competencies provided to me:

1. System Design
2. Architecture & Design Patterns
3. CI CD Adoption
4. Application Security Knowledge
5. NFR - Scalability, HA, DR, Resiliency
6. Code and Design Reviews
7. Virtualization (Docker, Kubernetes)
8. Software Testing & Automation Skills
9. Observability & Monitoring (Grafana, Prometheus, Splunk, etc.)
10. DevOps Skills (Incident Management, Application support, Disaster Recovery & High availability)

I joined the call and waited for 20 minutes, but no one showed up. I emailed as well as called HR, but there was no response initially. Later, the HR called and said due to a prod issue, the interviewer was not available and asked if I was ready to attend in the evening. We agreed, and it was scheduled in the evening, but again the interviewer did not join. The HR apologised so much for the inconvenience, and the interview was moved to next week. After rescheduling 2 times, it finally happened. The round began with the interviewer pasting LC 41. First Missing Positive problem in the chat.

I began with the brute force solution using a HashMap, and before jumping to the optimal solution, the interviewer told me he was okay with the approach and told me to convert to a controller class, which has an endpoint in which you post the array and get the answer in the response. Afterwards, he told me to add some validations and throw an exception.

Seemed like he was fine and then moved on to some resume-based questions based on CI/CD (Jenkins, Build process), Kubernetes (Features of Istio, Service Mesh), SQL vs NoSQL, and then some Spring boot questions (@SpringBootApplication, @EnableAutoConfiguration, @Autowired, @PostContruct) and finally to write 1 SQL query based on GROUP BY and HAVING. The only problem was that I lost internet a couple of times during he call. In the end, I asked the interviewer what work he was doing and asked for feedback, where the interviewer said I had demonstrated strong coding skills, the only thing was to have a stable internet connection.

HM Round (60 minutes)

After 2 days, I got a call from a different HR stating that I had cleared round 2 and she would be handling my candidature now. This time as well, I had asked for the competencies for the HM Round. The hiring manager was from the Chennai location, hence it was a virtual interview.

Below were the competencies provided to me:

1. Accountability
2. Innovation & Problem Solving
3. Planning & Improvement
4. Continuous Learning
5. Initiative
6. Adaptability
7. Teamwork & Collaboration
8. Customer Centred
9. Influence & Communicate
10. Stakeholder Management
11. Mentoring/Developing Team members

The round began with introductions, going through my resume and feedback from previous rounds. Then he proceeded with a few questions.

1. How does your day-to-day activity look?
2. What is the CI/CD process followed in your project?
3. HLD design of Twitter. How to handle read-heavy cases in multiple regions?
4. What is A/B testing? How would you set up its infrastructure?
5. What is canary deployment?
6. Discussion on the current project's functional and technical aspects.
7. How to handle a conflict situation with your manager?
8. A hypothetical situation where there is a mismatch between your architect's design pattern and your design pattern. The architect's design pattern seems to fail in production, and yours seems to work. What is the next step that you would take?
9. How do you find time for learning/upskilling?
10. Have you integrated AI into your day-to-day life? How do you leverage it?

The interview concluded with him asking some of my basic details, and we shared questions for each other. I asked for feedback, and he told me to always keep upskilling in today's world. Honestly, this round went okayish, according to me. However, after 1.5 hours, HR called to say that I had cleared the HM round as well. The HR then asked me to send some documents. Post that, she told me to visit the office the next working day.

Location Manager Connect (Bangalore)

This was the casual talk with the on-site manager of the team I would be joining. He spent some time diving into his experience with the different teams he worked on at Walmart. He also spoke about the team structure, what work I will be doing, and what the potential impact will be. At last, he was open to any questions, and I asked a few questions on the team's work and about how Walmart was structured (dot com, store, Sam's club, etc) on a high level. It was a good conversation.

HR Round (30 minutes)

The recruiter called after 4 days to discuss about the interview experience, offer and standard benefits in detail provided by Walmart. It took another 4 working days to generate the offer letter. The entire process took around 35 days.

Hi everyone, I recently interviewed with Walmart India for a Senior Software Engineer role. I’d like to share my experience and questions if they’re helpful.

Experience: 7+ years Skills: Java (Spring Boot, RxJava), AWS, Kafka, MongoDB

Interview Process

I applied for senior software roles through their careers page. A hiring drive was scheduled for Thursday, and I was contacted the Monday before. The process consisted of three elimination rounds.

Round 1: Data Structures & Algorithms (DSA)

I was asked to solve two DSA problems using any IDE, and I provided working code along with answers to the interviewer’s followup questions. I cleared this round.

• Question 1: Word Wrap
• Question 2: Zigzag Traversal of a Binary Tree

Round 2: Low Level Design (LLD)

This round was tricky as I was asked several Java-specific questions, including implementing the Singleton Design Pattern and thread safety techniques. For LLD, I provided a working solution for a YouTube Ranking System, using design patterns and OOP concepts. The solution was modular, easily extensible, and handled concurrency well. I advanced to the next round.

Round 3: High Level Design (HLD)

I was given 20 minutes to design an Inventory Service capable of handling high concurrency without degrading the user experience. I proposed a scalable and concurrent architecture, focusing on performance and smooth UX. However, the interviewer wasn’t fully satisfied with my initial approach. I pivoted my solution and discussed various trade-offs, but the interviewer did not actively engage in the discussion.

Hi all,

I was reached by a recruiter from Walmart 6 days ago that my profile has been shortlisted for the SWE-III profile and they will schedule the interview for 16th July.

I tried to follow up about the time slot almost daily, and guess what yesterday at 10pm they said they had some misunderstanding and they would schedule for 16th July at 11am.

Point 1 : Why did they assign the slot this late ? Honestly I was a bit dicey if I will be called for an interview or not. And hence, lost interest for prep (which I already started and continued for 2-3 days).

Questions asked : Question 1 : Difference between String, stringBuilder & stringBuilder As a follow-up one output question was about the same. (I was able to do it in a minute or so)

Question 2 : I was given two classes as follows

class Employee{
    private String name;
    private int id;
    private Age age;
}
class Age{
    int day;
    int month;
    int year;
}

The task was to make the class Employee as an immutable class. I was able to solve it within the time.

Question 3: Basic Calculator - III I was able to explain my thought process and started coding. But my code became a bit messy, although I was using Stack, but found the question quite lengthy. Hence, was not able to solve it completely.

Verdict : Rejected !!!

I feel sad because I put a lot of efforts, and I feel I could have done things better. Although my typing speed is quite okay so typing was not an issue, but I underestimated the last problem and didn't expect it to be that complex.

I have some doubts :

1. Does Walmart have cooling off period ?
2. What to do to apply again, as I am currently serving notice and I have seen Walmart hiring immediate joiners. I still have 35 days left for my notice.

July 3rd Onsite Hiring Drive for Bangalore:

YOE: 6years

Round 1: DSA 60min(Onsite round: cleared) 2 Leetcode medium questions

1. Decode ways : link
2. Remove K digits: link

Solved both with optimal approach.

Round 2: HLD 60min(Onsite round: cleared) A) Discussed on how to handle concurrent access of threads in DB for a transaction.

B) Design Twitter:

Design a simplified version of Twitter with the following core features:

1. Users can post tweets.
2. Users can view a feed that shows tweets from the people they follow, ordered by most recent first.

Discussion Highlights:

• The interviewer focused heavily on database design and schema structure.
• We discussed how to make the system scalable, especially with a large user base.
• There was significant emphasis on how to optimize for fast reads, and the trade-offs involved between read and write operations.
• Caching strategies and feed generation approaches were discussed.

Next day: Round 3: Java + LLD 60min(Virtual round: rejected)

The round was supposed to be 30min Java + 30 min LLD.

But we did not discuss anything about Java domain. I taked about one project on a very high level, while I was excited to talk in depth but interviewer immediatly moved to LLD.

LLD: Design a Notification System that can send notifications via email, SMS and WhatsApp.

I designed it using Observer+Strategy pattern. But interviewer was not satisfied, asked me to think of something else to scale the design for 1000s of services.

I attempted to Scale the design, but struggled to discuss the approach.

There were total 4 techical rounds - DSA, Java+LLD, HLD, HM. Each round was elimination round.

The interview process was smooth and feedback was given instantly by the Talent Coordinator.

In the third round, the interviewer felt I was reading from somewhere else, I lost my train of thought right after hearing this during the interview and clarified that I wasn't (my entire screen was shared the whole time, and I was facing only the screen). After this bad experience, I felt the onsite interviews are far better than virtual (ignoring the inconvenience caused by traffic). Atleast the interviewer constantly would not doubt the candidate.

🧭 Interview Process Flow

1. Online Coding Test
2. Technical Interview 1
3. Technical Interview 2
4. HR Interview
5. Final Selection

🖥️ Stage 1: Online Coding Test

• 📆 Date: 11th March 2024
• ⏱️ Duration: 90 minutes
• 👨‍💻 Platform: HackerEarth
• 👥 Candidates Appeared: 114

🧠 Format:

• 10 MCQs (OS, DBMS, CN, DSA)
• 2 Coding Questions

💻 Coding Questions:

Q1. Make Two Strings Equal with Swaps

• You can swap within a string or between the two strings.
• ✅ Logic: If all character frequencies across both strings are even, strings can be made equal.
• Points: 30

Q2. Unreachable Pairs After Edge Removal (Graph)

• Undirected connected graph, remove edges one by one and count (u, v) pairs that become unreachable.
• ✅ Key Idea: Think in reverse using DSU (Disjoint Set Union) to manage connectivity.
• Points: 50 (partial score)

📎 DSA Problem Link (asked in online round)

🟢 My friend solved Q1 fully and Q2 partially → Shortlisted among 36 candidates.

💬 Stage 2: Technical Interview 1

• 🕐 Time: Same day, 11:00 AM
• 🧑‍💼 Platform: Zoom (Breakout Room)

🔍 Questions:

• Intro + Past internship + Projects
• OS in one word: User-Interface
• Types of interrupts (needed a hint)
• Coding:
  • Binary Tree with mirror pointers
  • Find min distance between any 2 nodes → Solved using BFS
• What happens when you type www.google.com?
• ❌ Network Qs: Hub vs Switch, Noise Impairment (struggled)
• SQL vs NoSQL – explained with examples
• Coding (Index Shifting): Right shift subarray in multiple [l, r] queries → Optimized using index transformation

😅 Despite 2 missed answers, selected among 24 candidates for next round.

💬 Stage 3: Technical Interview 2

• 🕓 Time: 4:00 PM (Same day)
• 👨‍💼 New interviewer, same Zoom format

🔍 Questions:

• Summary of CV + Project demo (GitHub video impressed interviewer)
• Coding:
  • Implement Stack using Queues
  • Find time slots where 3 students are free (interval merging + 2 pointers)
• What is Normalization? Explained till BCNF
• OOP Concepts → Live coded example with Shape, Rectangle, Square
• What are Virtual Functions? Explained static/dynamic binding and pure virtuals

✅ Smoother round than before. Unfortunately, my friend left the Zoom meeting, missing the same-day HR round.

💬 Stage 4: HR Round (Next Day)

• 🕚 Time: 11:00 AM (Following day)
• 👩‍💼 Experienced HR (15+ years)

🔍 Topics:

• Intern project motivations, audience, challenges
• Walkthrough of other projects (with GitHub demo)
• HR appreciated the quality of work and impact

💬 Short and impactful (~30 mins). My friend felt confident after this round.

📢 Final Results

• 🗓️ Announced: 13th March 2024, 1:00 PM
• ✅ All 24 candidates were selected!
  • 10 received FTE + 6-Month Internship
  • 14 received Internship only

🥲 My friend was among the 14 — possibly because FTE slots filled early on the day of HR interviews. Leaving the meeting might’ve cost the full-time opportunity.

🎯 Final Verdict

✅ Selected for 6-Month Internship at Walmart India
🏁 FTE offer not received, but a fantastic internship opportunity nonetheless.

Round 1 -

Right view of tree Given input string, create groups of these which are anagram of each other Remove duplictes from linked list Graph , trie basic alogirthms

Round 2 -

tic tac toe lld synchronized vs static synchronized sharding, indexing singleton design pattern basic sql query using group by

Round 3 -

Implement CRUD and write rest controller for customer management in notepad with proper annotation and syntax

Some Common Managerial questions

Walmart Question asked in US sunnyvale location for compliance team

• Design your own Threadpool
• Topological Sort in Graph
• How internally cassandra/cosmos work

In this post I am sharing my interview experience at Walmart for Senior Software Engineer role.

I went in hiring drive where all 4 rounds were on same day.

Diffuculty - Medium - High

Total - 4 rounds

1- DSA

2- HLD + Java + Spring Boot + Project

3- LLD

4- Techno managerial

DSA Questions

Problem asked 5
coded -3
verbally told solution for -2

Few Problems i remembered

• Longest subsequnce without repeating characters
• Cyclic loop in a linked list
• subarry with given sum

HLD + Java + Spring Boot + Project

• Questions on Kafka - kafka key and topic concept
• Http codes 1xx,2xx ,3xx,4xx, 5xx
• Microservices archtecture

explain in detail about my current project.

LLD

Design a system for online grocery delivery. Assume you can provide subscription / non subscription model.

why MQ is required in this architecture
design DB schema.

Techno managerial

• All about project and roles and responsibilities
• some hypothetical questions
• Why u want to join walmart?

Result

Cleared all rounds. Every round is an elimination round.
Accepted the offer.

SDE @ SAP Labs
1.7 YoE
Tier 3 college
FullStack Development, Angular & Java Springboot

Interview was for React + Kotlin SpringBoot Developer
Applied via Instahyre, Recruiter reached out was already in Notice period

Appeared 4 rounds (DSA + Java/React + HM + HR)

DSA Round

Interviewer was very friendly, took the time to establish good environment and make me very comfortable.

• Tell me about yourself, what work you've done, why did you do a masters
• Told will not ask any superficial DSA questions will only ask questions related to DSA we do in our day to day work to understand my approach and problem solving (proceeded to ask superficial DSA questions regardless)
• Q1) 55. Jump Game, told about the question in high level. was supposed to come up with a solution myself & establish test cases + edge cases myself. Solved it completely
• Q2) 22. Generate Parentheses, initial explaination of question was not enough. Had to ask lot of counter questions. Explained the approach and implemented it, had a small bug in recursive base case & was getting more results than expected (also got all the expected results). Due to less time remaining remaining interviewer told they understood my approach and maybe post interview I can have a look at the bug in my own time.
• Had a small discussion related to the job, day to day work & walmart post 2 DSA rounds.
• Feedback - Strong hire
• Tips for others, walmart mostly asks questions from previously repeated questions.

Java & React Round

The interviewer joined late & seemed not very interested in taking the interview, I disliked this round.

• Q1) Introduce yourself, what work have you done so far, tell me about the product you work at. [Worked at new product, still under development]
• Q2) Have you worked on java & react [Yes].
• Q3) Have you worked with authorization in your application, what are the authorization methods [told about JWT, Session, OAuth]
• Q4) How do you handle local & global Exception in your application, write code to catch such exception. [Talked about Controller throwing exception, Controller Advice, Exception Handler, Custom Exceptions]
• Q5) Follow up question on custom exceptions [RuntimeException vs Exception] how to always ensure that you always return a standard error code & message for an excpetion. like 123=User not authenticated exception. [Talked about creating custom exception with a property error code via inheritence like strategy pattern & using a hashmap to always map error codes to specific errors. Interviewer said yes this can be one correct way, another way springboot provides some context holder (ExceptionContext? i forgot name, please comment if you know) & springboot will always map an exception to its correct error code].
• Q6) Which cloud technologies have you used & services [aws services mentioned, lambda discussed, competitors like azure & BTP]
• Q7) what are the benfits of cloud
• Q8) How do you scale an application [vertical & horizontal discussion]
• Q9) If a service has 4 instances, how do you figure out which instance a request should go to [discussed about load balancing, layer 4 vs layer 7]
• Q10) load balancing algorithms you know [told 4-5 basic algorithms, didnt remember all due to anxiety, answer was in the back of my head]
• Q11) How do you scale a database [discussed about sharding, replication, partitions, read heavy / write heavy dbs]
• Q12) explain sharding, how is it different from application horizontal scaling
• Q13) Question about different environments in code, how do you manage different configurations [Spring @Profile, application-dev.properties etc]
• Q14) Which design patterns do you know [listed 8-9 design patterns, common ones like builder, strategy, Factory etc.]
• Q15) Follow up question you say you dont use singleton but you use springboot how is that possible? [told i dont use singleton much, what i meant was i don't write singleton classes myself. had to clarify that's because spring provides beans which are by default singleton but can be made proto, request etc.]
• Q16) Write code for builder pattern [told i usually do this via lombok, interviewer said assume you have all dependencies], wrote the code.
• Q17) Get call vs Put call, how do you do a get call [fetch/axios]
• Q18) Which hooks do you know in react [mentioned state, effect, context]
• Q19) write use state example with use case, [created a counter button]
• Q20) Do you know about UseContext, what does it do [talked about DOM reference, fumbled a little]
• Q21) State managements libraries you know, what are their purpose [redux & recoil]
• Q22) What are the components in redux [listed a few like actions, reducers, selectors. couldn't tell all. Was recently doing angular so told a little about ngrx & effects]
• Q23) How do you optimize frontend [talked about defer loading, lazy imports, lazy loading, pagination, bundling etc.]
• Q24) write pagination URL [GET /testPagination?skip=100&limit=10]
• Q25) what changes you need to do for pagination at frontend [cursor based / limit based in query params and keeping page state]
• Q26) changes for pagination in backend [send skip / limit to the database, partially filled page handling etc]
• Q27) what if user sends skip value very large like 1 million. how to handle [have a default max at backend, or return an error response page size requested too large]
• Interview done, asked if i had any questions & Discussed about technologies used at walmart
• Got feedback doing good, strong in java but weak in react.

HM Round

• Q1) What do you do in your team [E2E software development, development, design, test etc]
• Q2) Tell me about the product
• Q3) In which part of this product your work, what is your day to day responsibility
• Q4) Talked about agile model
• Q5) How many people in the team
• Q6) What is the general development process in your product i.e. from story to definition of done
• Q7) What if you miss the deadline in a sprint / spillover
• Q8) How do you manage spillover and communicate it with the team
• Q9) What is the design process of a backlog [architect usually does it]
• Q10) How do you manage new story coming for development from outside team [outside india]
• Q11) How do you take feedback, have you ever recieved negative feedback
• Q12) If you're starting a new product, how will you decide it's techstack. what parameters you will choose
• Q13) What is 3 most important things for you in a new team
• HM did give little hint that spillover not okay & best try to match the deadline. Also said US timezone calls i.e. late working hours
• Interview over, then she asked what questions I had, discussed about walmart work, about this new product under development
• Discussed about genai
• Feedback - no feedback to give, said you're doing good. keep doing what you're doing

HR Round

• How Are you doing
• How were the interviews
• feedback about interviewers
• By when can i join walmart, Since I was an immidiate candidate HR said they will fastforward the process
• discussed by when can i expect the OL
• discussed about the $$
• asked HR about walmart moving towards 5day WFO from end of year [hr said no, pretty sure she lied lol?]
• said will get back by the end of week with OL

next day i recieved a rejection email, asked for reason HR said debriefing result between interviewers and HM. they will not be proceeding with my candidacy (after giving HR round & discussing numbers lol)

pretty sure they found a cheaper candidate or some other reason.

Overall had a very bad interview experience with walmart (except first interview). I can see why people say it has become more like SBC and culture has become bad. there was no coordination bw HR and interviewers. sometimes they didnt had my resume, sometime my interview was scheduled instead of some other person.

I would think 3 times before joining walmart ever / giving their interviews again.

Round 1 – DSA (Online Coding Interview, 60 mins)
Two medium-level problems:
https://leetcode.com/problems/swap-nodes-in-pairs/description/
https://leetcode.com/problems/subarray-sum-equals-k/description/

Round 2 – System Design(LLD) (60 mins)
Design LRU Cache
Design LFU Cache

Got a call from the recruiter within 30 minutes of Round 2 completion for the Hiring Manager (HM) round on that day itself. I had to defer due to being at the office.

Recruiter reached out two more times, I haven't pick the call. Since I’ve only just started my job search.

Hi guys, on 29th April I had my Walmart SWE3 Round 1 Interview for a Role Based on Java, The Interviewer first went through a basic intro and directly jumped to DSA Algo Discussions

I recently went though multiple rounds of interview at walmart tech. There were around 4 rounds for a position, I could not clear this interview process. Later they pushed my profile for a different team. During this process I have seen both side of interviewers.

Great set of interviewer

• Round 1 : interviewer was very polite and supportive. this was coding round he asked 2 questions. Sliding window and graph traversal.
• Round 2 : System design, same as previous interviewer. It felt as if i was having a discussion with a colleague. Question: to design Auction system.
• Round 3 : HLD LLD, Interviewer was neither polite nor rude, neutral kind of guy, Quesion : design task scheduler.
• Round 4 : Hiring Manager, Interviewer was neither polite nor rude, neutral kind of guy, behavioural interview questions.

Self-conceited interviewer

• Round 1 : HLD LLD, one of the built-in java API class and a system similar to Redis. Everytime i write a single line he would comment saying why are you doing this, he would not let me complete a thing. On top of that he kept repeating this line, Say my name is John, then he would say "John really, you really want to do this?" I felt this was degrading.

Final result was rejection in both interviews, To be honest, I know i am bad at tech right now, with the little time that I have I am studing. If i would have gotten offer from second interviwer, I would have joined out of desperation, But I surly would not like to work him.

Interview Format & Experience

Round 1 – Technical (DSA) – 60 mins

Quick self-introductions
Explain and implement the internal working of HashMap.
Design a browser system where only 10 tabs can stay open. When a new tab opens, the least recently used (LRU) tab should close. I had to explain the data structure, logic, and time complexity.
Discuss time complexities of common sorting algorithms.

Round 2 – Low-Level Design (Java) – 60 mins

Briefed my previous project
Asked to design BookMyShow: define classes, schemas, and explain concurrency handling.
Discussed relevant design patterns, why I’d use them, and gave a short explanation of each.
Some core Java questions:
Difference between Abstract class vs Interface
If abstract class has a constructor, why can't we instantiate it?

Round 3 – Hiring Manager Round – 60 mins

Again, started with project discussion
Behavioral questions like:
What are you most proud of?
What have you learned from experience (non-technical)?
How do you resolve issues?
Why are you looking to leave your current company?
Also covered:
Deployment process
SQL vs NoSQL
SDLC and methodology followed in current org

YOE - 2 Years 3 Months

Round 1 - DSA Round -> Question 1 - Merge Overlapping Intervals - https://leetcode.com/problems/merge-intervals/description/ -> Question 2 - Since the interview got delayed this was only a verbal one - how would you divide two numbers and express the answer upto max 2 decimal places without using Divide/Multiplication/Modulus operation. -> Other than this he also asked about the product that I am currently working on in my current org and some functionalities related to that.

Round 2 - JAVA/LLD Round -> Was asked to code a low level design of an E-Commerce application and the expectation for a working code at the end of the round was set in the beginning only. -> Got praised for my coding skills at the end.

Round 3 - HM Round -> Was taken by a senior manager. This went on for 60 min. -> In the beginning, was asked the details of my current project - the overall architecture and what design patterns that I have used. -> Then some questions related to design patterns. -> Last 20-25 min went in the behavioral questions like what are your goals for next 2 years, how do you present a design to a senior tech lead etc.

Overall Verdict - Cleared all the 3 rounds and currently in salary negotiation phase.

Walmart:

1st Round: DSA
1. Group of anagrams
2. https://leetcode.com/problems/unique-paths/description/

2nd Round: Java + LLD
OOPS - counter questions. Cloning
Multithreading, more on static/non-static synchronised methods
LLD - Payment Service(got last 10-15 mins)
Supposed to be 45 mins round, but took 1 hr 15mins.

Though both rounds went well but got rejected after 2nd round.

Education: BE from State University Work Experience: 2.9 Years (SDE 1)

I had applied to multiple openings via Google Forms shared on LinkedIn. A recruiter reached out to me and asked if I could attend in-office interviews on 21/03 (Friday).

Round 1

This round was DSA-focused, and I was expected to code in Java.

• A variation of the max sum subarray problem.
• Valid Parentheses.

Round 2

This round was a mix of LLD and core Java concepts. It started with an LLD problem, and the discussion went on for ~35 minutes, followed by Java-related questions.

• Design LLD for a digital wallet. Users should be able to create an account, manage personal info, and have different payment methods. Funds can be transferred between wallets and banks as well. Users should be able to see transaction history.
• Garbage collection in Java.
• Multithreading concepts.
• Threadpool, stringpool

Round 3 (HM Round)

This was supposed to be conducted on the same day, but due to unavailability, it happened on Tuesday. It mostly included behavioral and Java-related questions.

• Questions based on my resume, college, etc.
• If your manager has a different approach to solving a problem than yours, what would you do? Similar behavioral questions—don’t exactly remember the others.
• Dynamic dispatch in java
• Null pointer exception. Asked me to create one
• Differences between Java 8 and Java 17.
• Different primitive data types in Java with their sizes.
• How multithreading is achieved in Java.

Got a mail regarding document submission next day. No verbal/official offer from HR.

I have been interviewed onsite at Walmart for the position of Software Engineer III Banglore Location.

Round 1 : DS Algo Round. There were 3 questions in this Round (normally they ask 2 but in my case we had some extra time so interviewer asked me 3rd question as well)

• Q1: https://leetcode.com/problems/3sum/description/
• Q2: Given an array of numbers, return an array with zero based index on first smaller number to right of the curr number. If no smaller number exists, retrun -1 for that number. (Stack implementation) eg: input: 5 7 2 3 1 4 -> output: 2 2 4 4 -1 -1
• Q3: https://leetcode.com/problems/largest-rectangle-in-histogram/description/

Round 2: LLD Round

Design a Social networking site, with functionalities like adding posts, likes, comments, sending and accepting/rejecting friend request, giving 'people you may know' recommendations.

• After design asked questions like how to handle concurrent friend requests.
• how to tackle a situation when a single user is getting lots of friend requests.
• How to handle concurrency for each cases, how to tackle dirty read and race conditions.
• How to design a 'people you may know' feature, algo behind that and other details.
• Where to keep connections data and which database to use for each storage.

Round 3: Hiring Manager Round.

In this round he focused on what type of work I am doing in my currect organization. and what type of work I love to do. and told about the work Walmart does. HM got happy to know my current work and asked some more questions related to same which I answered with ease.

Interviewers were really polite and helpful. and were very active during the interview,

Overall Interviews went well and also all interviews happened in same day as it was a hiring drive.

Verdict: Selected

I applied for the SDE2 position at Walmart through Workday and received a call from the recruiter within 4-5 days.

1st Round: Cleared
This round consisted of two parts. First, I had 30 minutes to solve 25 MCQs covering Java, OOPs, DBMS, OS, and SQL concepts. Following that, I was given 40 minutes to solve two coding questions in Java.

2nd Round: Cleared
The interviewer was very friendly. After a brief introduction, we delved into two coding questions. The first was similar to Surrounded Regions, and the second was akin to Jump Game. I was provided a Google Doc link where I coded my solutions and explained my approach with various test cases.

3rd Round: Cleared
The interviewer in this round was less interactive and directly moved to the coding problems. The questions were similar to Product of Array Except Self and Binary Tree Level Order Traversal. For each problem, I was asked to discuss multiple approaches.

4th Round: Rejection
This was a hiring manager round where I was asked foundational questions, including some basic concepts related to HashMap. Although I felt I performed well and expected to clear this round, I was later informed of my rejection.

I applied for the SDE III role at Walmart in Bangalore through a referral. My profile included a B.Tech from a Tier 1 college and 2.6 years of experience.

Round 1: Data Structures & Algorithms (DSA)

Round 2: Core Java

Round 3: Hiring Manager (HM) Interview

Round 4: HR Interview

Outcome

Round 1: Data Structures & Algorithms

I was asked two medium-level LeetCode problems. The interviewer was flexible, allowing me to use a Word document or an IDE. My approach involved clearly explaining my proposed solution first, and once the interviewer was satisfied, I proceeded to code it and dry-run with a few test cases. Running the code wasn't a mandatory step.

Round 2: Low-Level Design & High-Level Design

This round focused on designing the feeds section of Instagram/Facebook. I started by meticulously gathering requirements and asking numerous questions to define the scope, such as whether posts included only text or images, the information to be stored with each post for data modeling, consistency requirements (I assumed eventual consistency), and various user interaction methods (likes, comments, replies, nested replies, sharing, saving). Next, we discussed database design—what type of database for what kind of data—and I listed out table attributes. Scaling was the next topic, leading to a discussion on caching strategies and eviction policies. The interviewer then asked me to implement the caching logic for an LFU strategy. Fortunately, I had recently studied this, and I was able to write the necessary classes, interfaces, and caching logic. The LLD logic was written on a Word document, but it can vary by interviewer; they are primarily interested in design patterns and adherence to SOLID principles. I'd also recommend using a whiteboard to map out classes, though I knew what I wanted to do and didn't spend much time there.

Round 3: Hiring Manager

This round was heavily concentrated on my resume, with the interviewer asking in-depth questions about every line and technology I had mentioned, lasting for about 1 hour and 40 minutes. A significant portion of the time was spent discussing my projects; I had to explain the problem statement and expect 'why' for every answer I provided. We had extensive discussions about Microservices and monolithic architectures, including suitable systems for each, transition strategies from monolith to microservice, and the rationale behind adopting microservices. Many questions revolved around Kafka and its internals—topics, partitions, consumers, consumer groups, why partitions exist, factors affecting throughput, and the interplay between consumers and partitions. I also faced questions about GraphQL, as I had used it in previous projects, covering why we use it, its advantages, queries, mutations, and resolvers. I was then given a design problem: to create a system that picks tasks from a database and schedules them to run at a specific time. I had to identify all potential bottlenecks, such as queue sizes, partition counts, concurrent database connections, and network issues, to demonstrate my end-to-end debugging capabilities. Lastly, given my performance testing background, the interviewer asked how it was done in my past projects and the various testing types required before a project goes live. This final round was quite challenging, and I couldn't answer all questions, leading to me not being selected after the HM round. Nevertheless, this experience was incredibly valuable for preparing for my next interviews.

I recently completed an interview process with Walmart for a Software Engineer 3 role in Bangalore, which was structured across four distinct rounds.

Round 1: Data Structures and Algorithms

• First, to find the sum of elements in a tree, specifically stating that the sum should be calculated as sum = leftsum + rightsum + currsum. This was a fairly straightforward tree traversal problem.
• Second, I had to implement a function to insert linkedlist2 into linkedlist1 at the nth position, ensuring I handled all possible edge cases carefully.

Round 2: Low-Level Design (LLD)

Functional Requirements:

1. The library should provide clients with methods to invoke both POST and GET calls.
2. It must allow clients to select their preferred underlying HTTP client implementation during invocation, offering choices like Spring RestTemplate, Apache HTTP Client, or OkHttp client.

Non-Functional Requirements:

1. The design needed to strictly adhere to Object-Oriented Programming (OOP) principles and SOLID principles.
2. It should be easy to add new HTTP client implementations in the future.
3. The code produced should be thoroughly unit testable.

During the design discussion, I faced several probing follow-up questions:

• I was asked about which design patterns I would use.
• The interviewer questioned my choice of the Factory pattern, asking why not Strategy, and if the Composite pattern could be applied.
• A classic question on when to use Factory versus Strategy patterns was posed.
• Finally, a tricky scenario: an existing interface has three abstract methods, two concrete implementations are already in production, and a new implementation only needs to implement two of these methods. I had to explain how I would handle this without breaking existing code or introducing unnecessary complexity.

Round 3: Hiring Manager (HM) Round

• I was asked about my five-year career plan.
• How I would handle a situation where a team member isn't cooperating.
• I had to explain the complete architecture of a significant feature I developed in my previous role.
• This was followed by questions specifically about the unit test cases for that feature.
• We discussed how to scale a system from handling 100 requests per second to 1 million requests per second.
• I had to justify my choice of a SQL database for a particular feature.
• The interviewer asked how I would implement rate limiting.
• I was also challenged to design a system for automatic alerts based on error messages.
• My approach to checking and identifying bugs was questioned.
• Finally, we discussed my process for conducting and maintaining effective code reviews.

Round 4: HR Round

I am happy to report that I received an offer from Walmart. My current compensation for 2.5 years of experience is 25.5 CTC (20.5 Base, 2 Variable, 3 Joining Bonus). The offer from Walmart is 25 Base, 5 annual bonus, and 6L RSUs over 3 years.

I recently appeared for the Software Engineer III role at Walmart. I have over 3 years of experience at a product-based MNC. The interview process involved two one-hour rounds.

Coding Round: This round began with introductions and project discussions. The interviewer then asked three easy LeetCode coding questions:

• Maximum Average Subarray I
• Odd Even Linked List
• Binary Tree Right Side View I was able to provide an optimized solution for all of them, starting with a brute-force approach. This round went quite well.

LLD and Java Round: This round also started with introductions and a discussion about my projects. Following that, I was asked one coding question:

• 3Sum I managed to write an optimized solution for this as well, after presenting a brute-force one. After the coding question, the interviewer delved into several Java and technical questions:
• Kafka Pros & Cons and Packet Size: What are the advantages and disadvantages of Kafka? What is the Kafka packet size limit?
• JDBC vs. Hibernate: Compare JDBC and Hibernate. I couldn't elaborate much here as I've primarily used JPA or Hibernate in my projects, not JDBC directly.
• Checked vs. Unchecked Exceptions: Explain the difference between checked and unchecked exceptions in Java.
• Sending Large Data to Client (Non-SFTP): Apart from SFTP, what are other methods to send large data to a client?
• Detecting File Corruption During Transfer: If a few bits get corrupted while sending a file to a client, how can you identify them? I suggested using a file checksum.
• Java Version Improvements (8 to 11 to 17): Discuss the key improvements and features introduced from Java 8 to Java 11, and then to Java 17.
• Internal Working of HashMap: Explain the internal working mechanism of a HashMap in Java.
• JVM Memory Model: Explain the Java Virtual Machine (JVM) memory model.
• Garbage Collection & Object Eligibility: Describe Java's Garbage Collection process and the ways to make an object eligible for garbage collection.
• Garbage Collection Types & Use Cases: What are the different types of Garbage Collectors in Java, and what are their respective use cases?
• Major and Minor GCs in G1 Garbage Collector: Explain the concepts of major and minor garbage collections within the G1 Garbage Collector. I knew G1 GC and its use cases but was not aware of major and minor in G1 GC. I feel that's quite a minor detail unless one needs to know these specifics.
• Project Deadlock Scenario: Describe any situation where you faced a deadlock in a project. I couldn't recall any such scenario at the moment.

Interestingly, there were no Low-Level Design (LLD) questions, which I had prepared for. I managed to answer about 80% of the questions. The remaining 20% felt like very minor details or scenario-based questions, such as the Kafka packet size limit, major/minor G1 GC, or specific deadlock situations I'd encountered.

I received a rejection email at the end of the day. I requested feedback, and the recruiter mentioned she would share detailed feedback in a couple of days, but it never arrived. My guess is that my performance in the second round wasn't satisfactory for them.

I had an interview at Walmart that centered around a challenging data structure design problem. I was asked to implement a data structure capable of performing several operations—specifically, returning the oldest, newest, minimum, and maximum elements, as well as fetching and removing the oldest and newest elements—all with a strict O(1) time complexity requirement.

I recently had an online interview for a Frontend Engineer role at Walmart Global Tech India, based in Bangalore. The interview started with a coding question which I found to be an easy to medium level problem, solvable using the two-pointers technique. After the coding part, the interviewer focused on grilling me on various frontend concepts. We discussed questions such as what DOM and virtual DOM are, React hooks with a strong emphasis on the useEffect hook, JavaScript basics, the differences between scope, block, and inline elements in HTML and CSS, and the CSS flexbox concept. Additionally, I was asked to predict outputs for some code snippets provided by the interviewer. Overall, I felt that the interview went well, but I am still waiting to hear back from the recruiter regarding the outcome.

I had my interview for an SDE2 position, or an equivalent designation, at Walmart in Bangalore. During the first round, I was presented with several questions. The interviewer appeared to be in a rush, which unfortunately meant I had barely any time to thoroughly think about or solve the questions. Despite the time constraint, I tried my best to tackle the problems posed.

Walmart Global Tech visited our campus in August to hire students for the Software Development Engineer role. Following an initial CGPA-based shortlisting, 98 students, including myself, were selected for the Online Assessment.

Online Assessment (September 2nd, 1 hour 15 min on HirePro)

Round 1 (Technical Interview 1): 1-1.5 hours

Round 2 (Technical Interview 2): 1.5 hours

Round 3 (Technical Interview 3): 1.5 hours

I recently interviewed for the Software Development Engineer role at Walmart Global Tech in Bengaluru. The process kicked off with a CGPA-based shortlisting, leading to an Online Assessment on the HirePro platform. This was followed by three intense technical interview rounds. I'm thrilled to share that I successfully received a full-time offer!

Online Assessment

Round 1 (Technical Interview 1)

Round 2 (Technical Interview 2)

Round 3 (Technical Interview 3)

I started my interview journey at Walmart with a Data Structures & Algorithms round that lasted an hour. I was presented with two problems. The first involved reversing a linked list in k-groups. The second problem was a variation of implementing a Trie, specifically designed to handle wildcard searches, where a '.' could match any single character. This required designing a data structure for operations like adding words and searching with patterns like '.ad' or 'b..'.

The second round was a technical discussion, also lasting an hour. This round included a Low-Level Design (LLD) question. I was asked to design a system to manage inventory updates between warehouses and stores, considering different mapping relationships (1:1 store to warehouse, 1:N warehouse to store). I approached this problem using the Observer pattern, which the interviewer seemed to be looking for, and we delved into its implementation details. Additionally, there were questions on core Java concepts such as Threads, Lambda functions, anonymous classes, and functional interfaces.

Finally, I had a one-hour Hiring Manager round focused on behavioral questions. We discussed a critical technical problem I've solved, my experience with production bugs and how I resolved them, and my ability to handle multiple projects simultaneously (to which I responded I hadn't yet). The interviewer also inquired about my motivations for leaving my current role, especially after a recent promotion, and what new things I've learned and implemented in my work. There were several other behavioral questions as well.

It took about two weeks after the second round for the Hiring Manager round to be scheduled. Ultimately, I received an offer for the SDE-III position.

The journey began after a recruiter from Walmart reached out to me on LinkedIn. Following a resume submission and availability check, I embarked on a series of eliminatory rounds, needing to clear each one to progress.

Round 1: DSA Round
This 1-hour round featured two LeetCode medium-level questions. The first was a unique graph problem, where I not only had to code the solution but also rigorously explain my data structure choices, the rationale behind using DFS or BFS, and how to optimize the approach. I managed to code it within 15-20 minutes, followed by running it to validate against test cases. The second question was a backtracking problem, strikingly similar to 'Letter Combinations of a Phone Number'. I also demonstrated its functionality with basic test cases. The round concluded with a brief discussion on my projects and resume.

Round 2: LLD + Project Based + JAVA
Lasting 1 hour and 20 minutes, this round delved deeply into Java, my primary tech stack. The interviewer sought in-depth answers to questions, particularly focusing on Multi-Threading and ThreadPools. I also briefly presented the architecture of my current project. Towards the end, I was given a Low-Level Design challenge: to design a File Structure System akin to a Linux file system, capable of listing all files and directories when a command like 'ls /path/' is executed.

Round 3: HM Round
My final interview, approximately 1 hour and 15 minutes long, was with the Hiring Manager of the team I was potentially joining. We discussed my current project, my tech stack, and my past work experience. Several behavioral questions were also posed. The round concluded with one medium DSA question, where I presented my approach and then coded it.

Verdict: I am pleased to share that I was selected and received an offer.

I recently interviewed at Walmart for an SDE III position in June 2024. I am currently working at a product-based company and have 3 years of experience. The interview process consisted of three main rounds, culminating in an offer.

Round 1 (DSA or Problem Solving Round)

• Remove duplicate nodes from a sorted linked list.
• Merge two sorted linked lists.
• Find the largest width of a binary tree.
• Perform a left boundary traversal of a binary tree.
• Create a binary tree using preorder and inorder traversal.

Round 2 (Java + LLD)

• What happens behind the scenes when we click the run button in IntelliJ to start our application?
• A detailed discussion on Exception Handling in Java, covering various mechanisms and best practices.
• In-depth questions on Object-Oriented Programming (OOP) Principles, with deep dives based on my responses.
• Questions on SOLID Principles: I was asked to design and write a service adhering to SOLID principles. The interviewer focused on my design choices, the reasoning behind them, annotations used, and how I would add additional features while maintaining SOLID compliance.
• There was also a question aimed at assessing my ability to create separate classes and define relationships between them effectively.

Round 3 (Hiring Manager Round)

My interview process for the SDE 2 role at Walmart consisted of four distinct rounds.

The first round was a 60-minute coding challenge. I was asked to solve problems like the Right Side View of a Binary Tree and one related to Kadane's theorem, likely focusing on the Maximum Subarray Sum.

The second round was another 60-minute coding session. Here, I tackled a problem involving cloning a linked list, often referring to a linked list with random pointers. Additionally, I was challenged to design a data structure capable of storing key counts at each timestamp, optimized for 'put' and 'get' operations.

The third round was a 60-minute Java-focused discussion. This round was quite intense, with significant grilling on language internals. Key areas of discussion included debugging sudden memory increases in a production environment without metrics, which led to a deep dive into Java Garbage Collection (GC), and the intricacies of the Java Memory Model. I also had to code a multithreaded program to print even and odd numbers sequentially.

Finally, the fourth round was a System Design HLD (High-Level Design) session. The first 30 minutes were spent discussing my past projects in depth. The remaining 30 minutes were allocated to system design, which I felt was insufficient for a proper evaluation. The core design problem was to design a 'Past Purchase Page' for an E-commerce website. This included features like displaying order details (OrderId, Amount, items), showing price distribution on item click, search functionality, and time-based filtering.

Ultimately, I was rejected after the system design round.

I had an interview for an SDE 3 role at Walmart. The first round was a technical round focused on Data Structures and Algorithms. I was asked to find the minimum element in a sorted rotated array, which I was able to answer correctly. The second DSA question involved finding the right view of a binary tree, assuming a normal binary tree. I struggled with this one and couldn't come up with a proper answer. Additionally, there were questions on MySQL covering topics like what an index is in SQL and why indexing makes queries faster. Overall, I was rejected from this opportunity.

I shared my worst interview experience with Walmart for a Software Engineer 3 role in Bangalore. The hiring drive took place on November 16th, 2023.

Round 1: Data Structures & Algorithms

This round consisted of two coding questions. I solved and coded the first problem in 15 minutes. After some thinking, the interviewer provided the second problem, which I also solved and coded in about 15 minutes.

Round 2: Core Java

This round involved a barrage of theoretical questions, all within 45 minutes. The interviewer ended the session 10 minutes early. I answered most questions appropriately and correctly, though I struggled a bit with JVM architecture and forgot to make the private constructor for the singleton design pattern. Despite these minor hiccups, the interviewer seemed impressed and discussed potential work at Walmart.

Result

I was unfortunately rejected. Recruiters stopped responding to my calls, and I only learned about the rejection through a friend who referred me.

I secured an off-campus opportunity at Walmart for the SDE role in Bangalore, thanks to a senior's referral and a job posting on Unstop. My resume strategy involved using Overleaf for a one-column format to optimize ATS scores, focusing on my top experiences, projects, and achievements with quantifiable metrics.

Online Assessment

Interview Rounds

1. First Round (Technical)

2. Second Round (Extensive Technical)

3. Third Round (Team Lead & Coding)

I interviewed for the IN3 position at Walmart Global Tech India with approximately 3 years of experience. The interview process was structured into several rounds:

Round 1: DSA and Problem Solving

This round focused on Data Structures and Algorithms. I encountered a variation of a binary search problem and a medium-difficulty linked list problem.

Round 2: Java and Low-Level Design (LLD)

This round was comprehensive, delving into Java concepts and LLD. I discussed my past projects in depth. Key technical questions included differentiating between ArrayList and LinkedList, explaining Runnable versus Callable interfaces, discussing Dependency Injection and Inversion of Control (IoC) along with IoC containers. I was also asked to code a scenario based on qualifiers (though the specific scenario isn't detailed here) and explain various Spring Boot annotations. Further topics covered SOLID principles, various design patterns, and I solved two SQL queries. A significant part of this round involved designing the class diagram for a Snake and Ladder game.

Hiring Manager Round

The HM round was more behavioral and project-focused. We had an in-depth discussion about my current projects, the biggest challenges I've faced, and my approach to solving new problems. I also shared my strengths, reasons for looking for a new job, and what I knew about Walmart, which led to a discussion about the organization and its projects.

HR Round

The final HR round covered standard questions such as my motivations for joining Walmart, reasons for leaving my current role, salary expectations, and notice period. I was informed that the offer letter typically takes about a week to be released after this round.

My interview process for the SDE2 (Fresher) role at Walmart Global Tech India was an on-campus hiring event for the 2023 batch, consisting of three rounds conducted over Zoom.

The first round was a technical assessment, lasting 45-50 minutes. It began with a self-introduction, followed by a brief discussion about one of my internship projects, a React application focused on frontend development. The interviewer delved deeper into my work, asking counter-questions about my process. Following this, I was given a coding question to validate a list of IPv4 addresses, returning a boolean array. I explained my logic, coded it, and then addressed potential error handling and input validations. The round concluded with basic Computer Networks questions, like 'what happens when you search google.com on your web browser,' and discussions on the differences and use cases of ArrayList vs. LinkedList, BST vs. LinkedList, and abstract classes vs. interfaces.

The second round, lasting another 45-50 minutes, focused on Data Structures and Algorithms. I mentioned Trees as my most comfortable data structure. The interviewer then presented a variation of the LeetCode problem 'Two Sum IV - Input is a BST', asking me to find the count of pairs with a given sum k. I initially proposed an O(N) time and O(N) space solution using inorder traversal. Upon being prompted for a space optimization, I offered an O(Nh) time and O(h) space complexity solution, which satisfied the interviewer, and I coded both. Subsequently, I tackled the 'Gas Station' problem from LeetCode, explaining my O(n) time and O(1) space approach and coding it out.

The third and final round was an HR discussion, approximately 40 minutes long. After a brief chat about my day and another self-introduction, we extensively discussed my internship projects, including challenges I faced and how I overcame them. The interviewer then explored my strengths and weaknesses. A particularly memorable part was when she asked about something I wasn't happy about and how my life would be if I had what I expected. I shared my journey from getting ECE due to JEE Mains scores to how it fueled my passion for the CS domain, which she received very positively.