Walmart Global Tech India Interview Experience (Backend / SSE) – Detailed Breakdown

Sharing my recent Walmart Global Tech interview experience to help others preparing. I went through all rounds till HM and was

rejected at the end. Overall, the process was technically solid and very

Sharing my recent Walmart Global Tech interview experience to help others preparing. I went through all rounds till HM and was

rejected at the end. Overall, the process was technically solid and very practical.

Role: Backend Engineer / SSE

Experience: ~7 years

Interview Mode: Virtual

Overall Duration: ~2 weeks --- ##

Round 1 DSA (60 mins, Live Coding)

Format: - 2 coding questions - Second question was optional - Language of choice (I used Java)

Q1 (Primary – Medium): - Sliding window / string problem - Similar to Longest Repeating Character Replacement - Required maintaining character frequency and window validity

Q2 (Optional – Medium): - Prefix sum + HashMap - Similar to Subarray Sum Equals K - Included handling negative numbers and edge cases I was able to solve both questions, including the optional one, and explained time/space complexity and edge cases. --- ##

Round 2 Java + LLD (90 mins) This round focused heavily on

Java fundamentals and object-oriented design.

Topics discussed: - Core Java concepts - Collections - Thread safety and concurrency basics - Design patterns (high-level discussion) - Tradeoffs and reasoning

LLD Question: -

Design LRU Cache

Approach discussed: - HashMap + Doubly Linked List - O(1) get and put operations - Eviction from tail - Move-to-head on access - Thread safety discussion using: - synchronized - ReentrantLock - Tradeoffs between simplicity and fine-grained locking This round went very smoothly with a lot of discussion. --- ##

Round 3 High Level Design (HLD)

Problem: Design a parcel delivery / dispatch system that efficiently assigns parcels to delivery partners.

Key requirements discussed: - Assign parcels based on geographical proximity (radius-based matching) - Consider live traffic conditions - ETA-based optimization - Efficient utilization of delivery partners - Handle large scale (many parcels and partners) - System should be scalable and fault-tolerant

Discussion areas: - High-level architecture (services, data stores) - Geo-indexing for radius-based lookup - Real-time location and traffic updates - ETA calculation service - Event-driven architecture - Near-optimal vs optimal assignment tradeoffs - Failure handling (partner drop, traffic changes, retries) This round was very practical and focused on real-world tradeoffs rather than just diagrams. --- ##

Round 4 Hiring Manager (HM) This round was not behavioral-heavy. - No STAR-based behavioral questions - Entire discussion was around: - Projects on my resume - Architectural decisions - Tradeoffs - Scale and failure handling - One thing that came up during discussion was lack of direct e-commerce / logistics background --- ## Final Outcome

Rejected after HM round.

Feedback (implicit): - Decision seemed to be more about team/domain alignment rather than technical performance - No explicit technical gaps were highlighted --- ## Takeaways - Walmart interviews are technically strong and practical - DSA matters, but clean explanations matter more than speed - Java fundamentals and concurrency are tested seriously - LLD expects clarity, not overengineering - HLD focuses on real-world systems (logistics, optimization, event-driven design) - At HM stage, domain alignment can matter Overall, it was a good learning experience and a well-structured interview process. Hope this helps someone preparing. Happy to answer questions.