Web Developer applicants have rated the interview process at Yelp with 2.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 55.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Web Developer roles take an average of 18 days to get hired, when considering 9 user submitted interviews for this role. To compare, the hiring process at Yelp overall takes an average of 18 days.
Common stages of the interview process at Yelp as a Web Developer according to 9 Glassdoor interviews include:
Phone interview: 50%
Skills test: 29%
One on one interview: 14%
Background check: 7%
Here are the most commonly searched roles for interview reports -
The first interview was relatively easy with all the trivial questions other have already mentioned - what port is used for HTTP, what does SSL stand for, what is the difference between GET and POST, etc..
On the second interview I was asked to code feed-buzz, create a simple code for caching values (used an array where key is md5(value)), set a timer in JS. Some questions will be dynamic - they will ask you to code something easy and then will ask you to modify it, for instance to handle a sightly different task or dataset. The interviewer was really nice, we chatted about our favorite programming books, etc..
Interview questions [1]
Question 1
On the 1st interview they asked me a few "number of digits need to code octet" and some bits and bytes types of questions which I successfully failed but it didn't seem to have affected the 1st interview much and I was still passed to the 2nd one.
I applied online. The process took 2 weeks. I interviewed at Yelp in Apr 2014
Interview
Applied through Indeed.com, received an email from recruiter a few days after, passed 1st round phone screen which went pretty much same as previous posts. 2nd step is a javascript code test (cannot disclose details as asked by Yelp) which is supposed to finish in 5-6 hours, I turned it in the next day and it got passed. 3rd step is skype interview which I assume is the usually talked about "2nd round" by previous posts, I prepared a lot on data structure and algorithm, but none of those questions were asked, the question instead was to create code to report javascript exceptions to remote server. Although I have many years of javascript experience and created successful front end applications, I was not able to answer specificly questions such as what JS error message will be for a certain wrong javascript code, the next day I received an "NO" email.
Interview questions [1]
Question 1
javascript error messages for running this code: var foo; foo["abc"]();
I applied online. The process took 3 weeks. I interviewed at Yelp in Oct 2013
Interview
I applied through their careers site and was contacted by a recruiter initially. The recruiter had a laundry list of questions for pre-liminary screen.
1. On which port HTTP runs?
2. Time Complexity for searching an item in HashMap
3. Time Complexity for searching an item in BST
4. SSL full form
5. Maximum value of 32 bits unsigned int?
6. Complexity of adding an element to the head of a linked list?
7. Protocol underneath HTTP
8. Time Complexity for searching an item in Sorted Array.
I answered all of them, so after that I was setup for a Skype Interview with one of the developer.
Second Round:
During the skype interview, I was asked a bunch of questions related to technology and then there was a problem solving to code.
1. What happens when you type yelp.com on your browser
2. Lets say your yelp.com homepage is loading slowly how would you start addressing the problem?
3. inner join vs left outer join
I pretty answered all of them, then was a problem solving question.
Interview questions [1]
Question 1
Write a function which will determine if a given string is palindrome or not.
bool ispalindrome(string input);
I was able to complete the problem and even the interviewer seemed satisfied with the solution.
Test Cases:
"racecar" => true
"!!a!" => true
"abc" => false
"a" => true
"A Man, A Plan, A Canal – Panama!" => true