found out about the job through Hired. I had a phone screen with a recruiter who was so incredibly enthusiastic about the company, it made me excited to progress in the process. I had another phone screen with an engineering team member, then they flew me out for an interview. An executive assistant booked everything for me. My in person interview was half a day in the office. I was offered the job 2 weeks later.
Surprisingly easy-going for a big name like Walmart. The interview started with a simple coding challenge focused on detecting cycles in directed graphs. I felt pretty relaxed during the technical rounds, which were straightforward and conversational. The wild part was recognizing the question as a close variant of one I had practiced on PracHub just days earlier. It definitely boosted my confidence. Overall, I was impressed with the process and was thrilled to receive an offer, which I happily accepted.
Interview questions [1]
Question 1
Course Schedule (detect a cycle in a directed graph using topological sort / DFS)
First, standard short phone call with recruiter. Then a 1-hour interview with an engineer on the team, asked about technical experience and background, and did a live coding assessment via video call. Fairly standard Leetcode style questions
Intense but rewarding — the interview for the Software Engineer position at Walmart Labs was tougher than I anticipated. The technical rounds included an LRU Cache implementation question where I had to articulate my design thoughts on thread safety, followed by a complex system design for a real-time inventory service. What made a difference in my prep were the company-specific prompts I found on prachub.com; they really helped me understand the types of questions I might face. Despite the challenging nature of the interviews, I ultimately received an offer but chose to decline.