The initial phone interview with the recruiter was a straightforward Q&A, which I appreciated. I dislike when recruiters, lacking coding knowledge, ask "explain this" or indirect questions. That's usually the first sign I don't want to continue the interview process. However, at Yelp, the recruiter asked direct questions. I can't recall the exact questions, but some seemed related to HTTP GET and POST requests.

The next round was a phone interview with an engineer. This engineer appeared disinterested in conducting the interview.

He asked questions such as:

• Talk about your most recent project.
• Code Test: (The interviewer shared their screen and asked me to type so they could see my progress.) Given a file containing chat messages, find the top 10 chatters efficiently. Assume usernames are unique. For example: <Nick1> : Howdy <Nick2> : Some message <Nick3> : Something else <Nick1> : I am good Nick1 is the top chatter; find nine others like this.

I dislike coding questions during phone interviews because I have to hold the phone in one hand (and arm, etc.) while typing with the other. Furthermore, the interviewer's yawning was not helpful.

He then asked some very basic Unix questions, at which point I realized I had not performed well.

Coding over the phone, as listed in the description.