There was a quick 10-15 minute interview that included general questions in computer science. After that round, I got the second coding interview. For that interview, I was given a tricky question, and I failed to think of a solution. My approach to that question was to directly think of the most optimal solution. I think that's why I failed.
I could have thought of a sub-optimal answer and built upon it. The main lesson I learned from the interview is to remember the Master Theorem so I can calculate the complexity of a recursion. (By the way, the optimal answer had nothing to do with recursion. My answer used recursion, and I failed to correctly calculate its complexity.)
For the coding interview, I got a tricky question. It has a very simple answer.
As I mentioned in the above review, I should have gone with a sub-optimum solution and at least compiled it once, before actually thinking about the optimum answer.
The following metrics were computed from 2 interview experiences for the Yelp Software Engineer Internship role in United States.
Yelp's interview process for their Software Engineer Internship 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 Internship interview process in United States.