I was contacted about an interview after applying with my resume at a college career fair.
The first round interview was non-technical, focusing on my interests going forward and such. There was almost no discussion of experience or any technical topics, but it perhaps served as a sanity check.
I was then contacted about a technical phone interview. The interview was straightforward and proceeded using Collabedit as the platform for responding to technical questions in the language of my choosing. This was fairly simple and went fine.
A few weeks later, I was contacted regarding an onsite interview and went to the San Francisco office. They were gracious enough to let me take the interviews in the afternoon, as I had a conference call to attend during lunch.
The interviews consisted of four 45-minute technical sessions:
They were generally pleasant and interesting people to talk to.
I ended up not performing great on them, particularly on questions about certain technical topics I was not familiar with (specific object-oriented concepts and design patterns).
While I'm not sure of the exact considerations, I was not made an offer.
I was asked to implement a function to take a collection of SET cards and identify a set if it exists, or return an error status or something similar if it does not. This is according to the rules of the game "SET", which you should look up for context.
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.