J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Walmart (Sunnyvale, CA) en mars 2020
Entretien
5 week process
1)Phone with Recruiter - Messy, recruiter not organized, hard to schedule the call, had to postpone twice.
2)Hackerrank - Nice interviewer, easy OO problem.
3)Onsite - hard to schedule, hard to contact recruiter, not organized.
- 4 interviews: 1 system design and 3 (some medium, some easy) leetcode style problems. I was thrown an extra one at the end.
4) Rejection after 2 days - I did very well in the onsite: solved all the problems and had nice conversations/clicked with everyone but was told they were looking for someone more senior. They should have challenged me more or asked better questions if they wanted to gauge my level, not trap me into problems that juniors can solve.
Questions d'entretien [1]
Question 1
Given an unsorted array of integers and a target, find all triplets that sum to the target.
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.
Questions d'entretien [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.