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

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.