Initially contacted by a recruiter.
The first step was a 15-minute HackerRank online coding test. This was a fairly easy sorting question.
The second step was a 45-minute Skype interview. The first 10 minutes or so included questions about my resume and background, as well as "Why Yelp." Then, there was 30 minutes of coding on a Coderpad. The question was similar to the "design" style questions on LeetCode, around a medium level for an optimal solution. A few minutes at the end were left for questions.
The third step involved two back-to-back 45-minute Skype interviews. Each of these progressed similarly to the first, with background questions and the majority of the time spent coding. Then, a few minutes at the end were left for questions. The first question was an easy level, the second a medium. The first question was unique and not like most LeetCode problems. The second was a variation of the LeetCode merge interval problem.
After a bit more than a week (and two follow-up emails), I received a rejection from the recruiter.
All of my interviewers were professional, and I thought the coding questions were reasonable. I liked that they weren't all just straight LeetCode questions like most places.
Why Yelp?
What's the difference between C++ and Python?
Tell me about yourself?
The following metrics were computed from 280 interview experiences for the Yelp Software Engineer role in United States.
Yelp's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Yelp's Software Engineer interview process in United States.