A recruiter contacted me via LinkedIn and set up an onsite interview directly on a Saturday afternoon. I had two coding/problem-solving rounds. Each panel had two interviewers (junior staff).
They expected me to code on paper. Good companies have long moved away from this practice and use CoderPad.io (with a laptop provided). I opted for a whiteboard, which was barely there.
Unless you have memorized the exact solution and can reproduce it precisely, don't expect to clear the round. Remember, junior staff straight out of college often only know this method. Someone with double-digit years of experience doesn't really write tree problems in their day-to-day work. And I am pretty sure Walmart engineers also don't.
The recruiter did not set expectations around the nature of the interview rounds, such as coding versus problem-solving versus design/architecture. Also, they would send me home sharing feedback like 'your DS/Algo is weak' or 'coding is rusty,' etc., in front of all the other interviewers sitting in the conference room. Learn to respect the privacy of candidates.
Their practices are on par with service companies.
Tree problem (lifted from geeksforgeeks.com - a 3.5 medium level problem). Interviewers didn't even bother to look at the resume.
Problem around the longest substring (again lifted from geeksforgeeks).
Problem on finding a palindrome in a Linked List.
The following metrics were computed from 2 interview experiences for the Walmart Principal Engineer role in Bengaluru, Karnataka.
Walmart's interview process for their Principal Engineer roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Walmart's Principal Engineer interview process in Bengaluru, Karnataka.