The interview process was very efficient. After solving the HackerRank challenge, it took about a day to get a call from the recruiter and set up a follow-up coding interview. After only a few days, I got to the onsite, which consisted of a system design interview, a coding interview, and two behavioral interviews. All the interviews were enjoyable, and the questions were well-designed and understandable. The coding questions were not too difficult, and there was an emphasis on providing a testable solution. Each time, the interviewer would ask me how I would test my code and what I would improve.
Given a list of entries of type { "from": User, "to": User, "message": Text }, create a leaderboard of users who received the most number of messages.
Follow-up: Add a way of filtering SPAM messages (multiple messages from one user to another of the same text).
Given a list of businesses and a desired search text, find the first 5 businesses prefix-matching the searched phrase (on any of the words).
Example
businesses = ["Burger's Johns", "Papa Burgers", "Pizza Italiana"] search = "bur" result = ["Burger's Johns", "Papa Burgers"]
The following metrics were computed from 10 interview experiences for the Yelp Software Engineer role in London, United Kingdom.
Yelp's interview process for their Software Engineer roles in London, the United Kingdom is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Yelp's Software Engineer interview process in London, United Kingdom.