The process began with a HackerRank test. It was pretty simple, although there was one case that I missed. This missed case became the focus of the entire second interview with the hiring manager. It was quite interesting coding up a follow-up to the HackerRank question.
After that, I had a discussion with one of their Android engineers. We spoke about my experience, and I was asked a few technical questions. Following this, I was given a take-home test.
When I didn't hear back after the take-home test, I contacted the hiring manager. They informed me that the position had been closed. I assume either they hired someone with more experience or something went wrong with the position, and it's no longer open.
The hiring manager was very pleasant and mentioned he would share all my interview materials (tests and projects) with other hiring managers within the company. He also advised me to contact them if I didn't hear anything.
I didn't end up hearing back from another manager, so I did indeed contact the manager again. Unfortunately, I haven't heard anything to this point.
It was a great interview experience, though unfortunate that it ended so abruptly. I was quite interested in the team and company.
NDA
The following metrics were computed from 2 interview experiences for the Walmart Android Engineer role in San Francisco, California.
Walmart's interview process for their Android Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Walmart's Android Engineer interview process in San Francisco, California.