I applied to multiple roles and heard back for the new grad Android developer role. My interview process had 2 technical phone screens on HackerRank, followed by a virtual onsite that had 4 rounds of various types. Two of them were the typical problem-solving rounds one would expect, while the other two rounds were Android code review and feature/DB design rounds, respectively.
I really enjoyed interviewing with Wish, as every interviewer made me feel like a co-worker rather than an applicant. The interviewers were actively discussing the problems with me, which made me feel like I was collaborating with the interviewers rather than being tested. One of the interviewers even spent more than the scheduled 1 hour to discuss the questions that I had about the company.
My virtual onsite was on a Friday, and I heard back about the offer the following Thursday.
The questions were mostly LeetCode mediums with some LeetCode hards. Each round started off with an easy version of a problem and ramped up in difficulty by adding space/time constraints. I was asked if it would be possible to optimize the solutions for questions that could be solved with DP, but I didn't have to implement the DP solutions.
The following metrics were computed from 8 interview experiences for the Wish Software Engineer role in San Francisco, California.
Wish's interview process for their Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Wish's Software Engineer interview process in San Francisco, California.