SDE-3 Walmart (Interview Experience)
Summary
I interviewed for an SDE-3 role at Walmart, which comprised a DSA round, two LLD/HLD rounds, and a final hiring manager discussion. The technical rounds included popular LeetCode problems like Number of Islands II and Longest Consecutive Subsequence, alongside system design challenges for a Ledger System and a Ticket Booking System. The hiring manager round focused on my current projects and behavioral questions.
Full Experience
Total YOE : 3.5 yr
- 1st Round (DSA Round) (Online) :
- Number of Islands 2 (leetcode medium)
- Longest Consecutive Subsequence (leetcode medium)
- 2nd Round (LLD/HLD Round) (On-site) :
- Ledger System Design : Asked about the LLD & HLD , FR, NFR, Schema design , DB Design , Design Pattern
- 3rd Round (LLD/ HLD Round) (On-site) :
- Ticket Booking System : asked only HLD Concepts - grilled on FR, NFR, Schema Design, DB design , Locking (Optimistic, Pessimistic)
- 4th Round (Hiring Manager) (On-site) :
- Current Project Drill Down , STAR Pattern Question , Few Technical Question .
Best of Luck !! :)
Interview Questions (4)
Number of Islands II
I was asked to solve the 'Number of Islands II' problem, which is a known LeetCode medium problem. This problem typically involves a grid and processing queries to add new islands, then reporting the number of islands after each addition.
Longest Consecutive Subsequence
I was asked the 'Longest Consecutive Subsequence' problem, a classic LeetCode medium problem. The goal is to find the length of the longest consecutive elements sequence from an unsorted array of integers.
Design a Ledger System
This system design round focused on building a Ledger System. I was asked to cover both Low-Level Design (LLD) and High-Level Design (HLD) aspects, including defining Functional Requirements (FR), Non-Functional Requirements (NFR), designing the schema, discussing database design choices, and incorporating suitable design patterns.
Design a Ticket Booking System
In this system design round, I was asked to design a Ticket Booking System, with a specific emphasis on High-Level Design (HLD) concepts. The discussion involved Functional Requirements (FR), Non-Functional Requirements (NFR), Schema Design, Database Design, and a deep dive into locking mechanisms, specifically Optimistic and Pessimistic locking strategies.