Taro Logo

Full-Stack Engineer Interview Experience - Los Angeles, California

April 1, 2016
Negative ExperienceNo Offer

Process

The interview process began with a couple of phone screens, followed by an on-site interview.

The on-site interview was very thorough and lengthy, involving meetings with approximately 10 different people.

Despite having highly relevant experience, I was rejected. The recruiters did not seem interested in explaining the decision.

In a word: confusing.

I still don't have a clear reason for my rejection, except that perhaps I was too nervous or lacked strong social skills.

Get plenty of sleep before the on-site interview, as it is long and will involve talking to many people.

Although the interview wasn't very technically challenging, I sense they prioritize social interaction. This information may be useful for future candidates.

Questions

Why are you interested in Tinder?

What are the advantages (in JavaScript) of prototypal inheritance?

What does an empty object literal coerce to when compared to a string?

e.g. "{} == ?"

What is a closure?

What are some advantages and disadvantages to using MongoDB?

What about Redis?

What databases are you familiar with?

What AWS services are you familiar with?

Are you familiar with SQS, Lambda, EC2, S3, Dynamo?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Tinder Full-Stack Engineer role in Los Angeles, California.

Success Rate

0%
Pass Rate

Tinder's interview process for their Full-Stack Engineer roles in Los Angeles, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Tinder's Full-Stack Engineer interview process in Los Angeles, California.

Tinder Work Experiences