Envié una solicitud electrónica. Acudí a una entrevista en Walmart (Reston, VA) en may 2017
Entrevista
. Phone screen followed by an online coding exercise and then onsite. Walmart recruiters are the slowest recruiters that I have come across. My recruiter was someone called Burgos. Their interview process is so long than Amazon releases at least 1-2 products by that time. The recruiter emails you about your interest and forgets you for a month. Then after following up million times, the recruiter gets back with a phone screen which you will easily crack. After the phone screen, they give you an open ended coding exercise. If you are a decent developer who builds quality products, you will spend atleast 5-6 hours on the exercise( that is total time for uber + amazon interviews) .
The worst part is you need to follow up a million times to hear a feedback of your code and the recruiter doesn't even care to respond. I know for sure that my code was not that bad that they would reject without an email.
My feedback for them is to be responsive to candidates and appreciate the time that candidates spend for their exercises rather than being disrespectful to them.
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.
