After my profile was shortlisted, the recruiter called and scheduled an interview. They explained the interview process in an email, which I have copied below.
We intend to cover 5 rounds, with details provided below. Each round would last for an hour on average.
The recruiter called the next business day. As I am not working in Bangalore, I asked them to arrange logistics. They then told me there would be one telephonic round, and the rest would be onsite. I agreed, as they would ensure the candidate is up to the mark before I spend on logistics.
When I attended the interview, I was surprised to see the level of questions and their expectations. None of the questions aligned with the process the recruiter explained over email. All were theoretical Java questions, which I remembered preparing when I was a fresher and in college.
Trust me, there was no DS, Algo, or problem-solving.
I am sure if we have to go to service-based companies, interviews would be like this, and people focus on those skills only, rather than DS, Algo, and problem-solving. But I didn't expect this from a product-based company. I ended up wasting 30 minutes, and thankfully, I didn't have to waste a full day by traveling to their office.
I can guess what quality of work they might be doing if it's just language.
The following metrics were computed from 1 interview experience for the Walmart Sr. Software Engineer role in Bengaluru, Karnataka.
Walmart's interview process for their Sr. Software Engineer roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Walmart's Sr. Software Engineer interview process in Bengaluru, Karnataka.