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
Initial phone call.
A Technical that was not technical. This was the part of process that I kind of got thrown off by. Typically technical interviews are to assess your coding ability and knowledge of the specific stack. This was not that. First three questions were behavioral what if scenarios. The questions revolved around the same issues, and basically the same question asked over and over again. Next, I was asked to design a warehouse space and then told there was no wrong answers (often translates there is only one right answer, and you better follow it to a T). Overall, I felt a bit set up to fail. As the email describing the interview said the interview cover topics such as the basics of Computer Science and the tech stack, so immediately going into the interview I was thrown off.
Interview questions [1]
Question 1
What would you do if someone took credit for your work?
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.
