I applied to the new grad role online and received the HackerRank assessment shortly after. The online assessment was a simple graph question, assessing which nodes are accessible from specific starting positions given a limited travel distance.
After that, I was quickly reached out to for a technical video interview. There was a disconnect between what the recruiter described the interview to be and what it actually ended up being. The recruiter said the interview would have resume questions, knowledge questions, and "potentially a coding question".
The first thing my interviewer told me when we started was that this interview would be solely a coding interview. Not a big deal because I was expecting a coding question either way, but just something to note.
The question wasn't too complicated, and I felt I had a good grasp of what to do in order to solve it efficiently. My interviewer was very nice and accommodated for technical issues I had at the start of the interview, and she was great with answering questions at the end.
That being said, I didn't move forward.
Hackerrank: Simple graph question, assessing which nodes are accessible from specific starting positions given a limited travel distance.
Video interview: Given a list of dictionaries, each storing a sender, receiver, and message, determine who has received or sent the most messages (each message must be unique; otherwise, it doesn't count).
The following metrics were computed from 2 interview experiences for the Yelp Full Stack Software Engineer role in United States.
Yelp's interview process for their Full Stack 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 Full Stack Software Engineer interview process in United States.