The first round was a simple HackerRank question that could be solved in 15-20 minutes.
The second round was a technical phone screen on Skype, which involved LeetCode easy/medium questions. They wanted to proceed to a second phone screen on Skype, which also involved LeetCode easy/medium questions.
By the time I was called on-site, I already had an offer and tried to expedite the process. The recruiter did their best but could not schedule interviews immediately due to the holiday season.
The on-site interview consisted of three algorithm rounds and one manager interview. I thought I did fairly well, except for one or two questions, particularly in the manager round. The questions were behavioral and could be disarming.
After my on-site, I requested them to expedite the process. After gathering interview feedback, a hiring committee made the final decision.
Two days later, they had collected all the feedback and wanted to collect my references' contact information. The use of phrases like "Green Signal" made me feel like the feedback had been positive.
I sent my references' contact information, and the following weekend, I spoke with the recruiter. Their final decision was not to move forward with an offer.
Why ask for reference checks and make the candidate wait for four days when they intended to decline? They jumped the gun too soon, and my experience post-on-site was quite disappointing. They also did not provide any specific feedback after four rounds of interviews.
Most of the questions asked are on Glassdoor.
The following metrics were computed from 92 interview experiences for the Yelp Software Engineer role in San Francisco, California.
Yelp's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Yelp's Software Engineer interview process in San Francisco, California.