Taro Logo

Software Engineer Interview Experience

October 1, 2014
Positive ExperienceNo Offer

Process

I met the recruiter at a career expo by my university. A few weeks later, we scheduled a phone interview. The phone interview was supposed to be 15 minutes but only lasted about 5. The recruiter speaking over the phone was very nice, but the noise from their environment made it a bit difficult to listen. It also felt as if they were rushing to finish the call and just spat a bunch of information at me. It was pretty much an overview of the intern program at Yelp and making sure that you're sane enough. After the phone interview, they sent a coding challenge via HackerRank.

The challenge from HackerRank was 28 minutes and had 15 questions.

  • 14 questions were quick technical questions that can be found on Glassdoor.
  • The last question was a coding question in which you had to submit code.

28 minutes was kind of odd. I think 2 more minutes would have allowed me to fix my output. Because I didn't get to, I messed up and didn't proceed with the interview process.

Questions

Given a string, print true or false if you can create a palindrome with it.

Was this helpful?

Interview Statistics

The following metrics were computed from 280 interview experiences for the Yelp Software Engineer role in United States.

Success Rate

9%
Pass Rate

Yelp's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive43%
Neutral44%
Negative14%

Candidates reported having very good feelings for Yelp's Software Engineer interview process in United States.

Yelp Work Experiences