A recruiter first reached out telling me they would love to interview me. I replied asking for more information, so we scheduled a phone call.
The recruiter asked questions about my interests to gather information about what team would suit me best. I am very happy they took the time to do this because at first they had a different role in mind for me.
The next step was a technical phone interview (using HackerRank). This seems to be pretty standard across the industry.
Next step seemed a bit unorthodox to me, as it was a coding exercise on HackerRank. Very much like the phone interview, but no interaction with an interviewer. I would have expected this step before the phone interview; failing this step wouldn't waste anyone's time, as it being automatically graded. Overall, not opposed to this step, as it gives more data points to the hiring committee at the end of the process.
After this, there was a string of 1:1 interviews with engineers from the team I would potentially join, the last one being with the team lead. The range of questions asked was really wide and gave me a good insight about what I could be doing for the company.
A mere two days after the on-site, I got an offer.
How would you decide whether or not two binary trees encode the same data?
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.