Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Yelp

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Yelp reviews | Yelp jobs | Yelp salaries | Yelp benefits
      Yelp interviewsYelp Front End Engineer interviewsYelp interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Front End Engineer Interview

      10 Jun 2010
      Anonymous interview candidate
      No offer
      Negative experience
      Average interview

      Application

      I applied online. The process took 2 weeks. I interviewed at Yelp in Jun 2010

      Interview

      The initial hr recruiter was very nice and usually prompt with replying to my emails. He did an initial phone screen verifying the information on my resume and then set me up with a technical phone interview with another front end engineer. The first technical interview went very well. The engineer conducting the interview was pleasant enough and knew what he was talking about. First we discussed my experience listed on my resume and I believe he was mainly trying to see how I thought about large projects, how I organized myself, how I manage multiple tasks. He also asked me about my team project experience, and dealing with troublesome members, etc. The next part of the interview consisted of technical questions mainly about front end technologies. He asked a lot about various CSS and cross-browser bugs and how to deal with them. Also various questions about JavaScript (some language specific syntax and such) and JavaScript optimization. After the first phone interview I was green lit to do a coding test. The coding test, in my opinion, is very poorly designed. The problem I was given was an information retrieval problem that has been studied for years. There are lengthy college research papers on this topic and is an interesting problem to study for a few years in the academic circles. Making this a problem for a code test is ridiculous. You could literally spend years studying and researching the algorithm they asked you to create on this code test. They give you no guidelines or guidance as to how complete the algorithm should be so said to myself I would spend a weekend on this problem and that would have to be enough. Luckily, my work was enough and I was moved on to the next round. Also, they wanted the code to be unit tested. In my opinion that was the first sign this company didn't know what they were doing in the hiring process and I probably should have just deleted the assignment and gained my weekend back. Having passed the code test, I moved on to the next round. I'm from out of town, so instead of an on-site interview I had to endure one more phone interview. This time, the interview went terribly. First, the interviewer was very awkward on the phone. I know these tech companies hire a lot of programming gurus that have little in the way of social skills but make it up in programming skills. However, these same people should not be allowed to conduct phone interviews. The interviewer would talk a thousand words a second, and then abruptly stop. Meanwhile, I would be making comments or otherwise being civil and sociable over the phone. Whereas the first interview would respond and we'd engage in conversation, the second interviewer mainly just breathed into the phone, making for a highly awkward interview. Second, I'm not entirely convinced this interviewer was actually a front end engineer. I spent three days studying nonstop for this interview, covering every single aspect of XHTML/CSS/JavaScript/PHP, and it turns out NOTHING I studied ever came up during the interview. He asked me the same exact questions from the first interview regarding my resume and past experience. Then he delved into backend questions regarding SQL and databases. I know these are on my resume, but I'm not an expert in them and don't pretend to be. I'm being hired for a front end position not a back end position. Seeing as I was having trouble with his questions, instead of moving on to another topic, the interviewer delved deeper into the topics I wasn't an expert in. We ended up spending 20 minutes talking about data structures in databases and sorting algorithms. Then the interview abruptly ended because we were coming to time. Not once did he discuss ANY front end technology. There were no talks or questions regarding XHTML, CSS, JavaScript, or even PHP. So how he could assess my skills as a front end developer are beyond me. Needless to say I did not get called in for an on-site. I asked for another technical interview because that interview was not appropriate for my position but of course these requests fell on deaf ears. I was simply sent a form letter saying good luck in your search. After all the time and effort you put into their interview process you'd think they'd have the decency to provide you with a hand written email or tell you why you are being let go. Frankly, I was and still am pissed about the process. It's obvious this company has no idea what they're doing with their hiring process. I would suggest you avoid this company. There are other companies out there with better hiring processes than Yelp. It also makes you wonder what kind of people they're really hiring and how far this company will go when they completely suck at looking for talent.

      Interview questions [2]

      Question 1

      What situation arises when you have a parent div and all it contains is a pair of floating divs? And how can you remedy the situation.
      3 Answers

      Question 2

      In Javascript, what is the === symbol?
      1 Answer
      4

      Other Front End Engineer interview reviews for Yelp

      Front End Engineer Interview

      6 Aug 2017
      Anonymous interview candidate
      San Francisco, CA
      No offer
      Neutral experience
      Easy interview

      Application

      I applied online. I interviewed at Yelp (San Francisco, CA) in Mar 2017

      Interview

      Applied for position in February and reached out to recruiter on LinkedIn. Exchanged a few emails and after a phone screen, the recruiter set up a coding challenge. Communication wasn't the best, and I had to reschedule once due to the interviewer not being available. I was informed that it would be a timed challenge and that it would include front end technologies. I assumed there would be some javascript involved, but the challenge was strictly HTML and css. Very easy! I passed the challenge and set up an interview for a Skype meeting with an engineer. I was not given any information on this interview, and was caught off guard by one question he asked me. The answer he was looking for involved an outdated jQuery method, and I answered using AngularJS. So, I think that led to his dismissal of me as a candidate. Overall it seemed like he wasn't too thrilled about yelp or interviewing me. I would assume the already had other candidates in mind. Overall, I was not properly prepared for either interview. Both were very easy, but they were very transparent about having their eye on another candidate.

      Interview questions [1]

      Question 1

      Design and build a modal and tooltip
      Answer question

      Front-End Engineer Interview

      28 Oct 2018
      Anonymous employee
      San Francisco, CA
      Accepted offer
      Positive experience
      Average interview

      Application

      I applied online. The process took 3 weeks. I interviewed at Yelp (San Francisco, CA) in Mar 2017

      Interview

      There was phone screen, 1:1 technical interview, onsite interview. 1:1 technical interview was a Javascript question. No HTML or CSS question. I was expecting CSS questions, since it's a Front End role.

      Interview questions [1]

      Question 1

      Build a tooltip with Javascript without using jQuery
      Answer question

      Front End Engineer Interview

      20 May 2014
      Anonymous interview candidate
      No offer
      Positive experience
      Average interview

      Application

      I applied through an employee referral. I interviewed at Yelp in May 2014

      Interview

      I applied online and got an email about a week later asking for a phone screen in the next week. Everyone else is right on the money about how it goes: Questions about your background, why Yelp, do you use Yelp, etc. Then they get to the technical questions. Important! If you're applying for a front-end job, read this and not all the other interview reviews. I got seriously scared that they were gonna ask me about octets and really CS-based questions that I never use in my day to day work. I'm self-taught so a lot of stuff that people learn in classes never got to me or I glossed over it. Anyway, the questions are below (that I remember): 1. In HTML, what does <title> do? 2. In CSS, what are the different values in the Position property? 3. How would you hide images on a page? 4. Would not naming a variable in JavaScript cause an error message? I passed and got send a coding test. If I pass that there is a Skype interview and then an in-office interview.

      Interview questions [1]

      Question 1

      They weren't that difficult. I think I stumbled because I was psyched out by all the reviews I read on this website.
      Answer question