Taro Logo

Software Engineer Interview Experience - San Francisco, California

May 1, 2016
Negative ExperienceNo Offer

Process

The interview process was smooth enough. It was odd that I had three different recruiters contacting me at different times. I never knew who I would be speaking with at any given moment. Even when I arrived, I was told to ask for a specific person. Instead of that person, a different recruiter came to meet me. However, everything was scheduled well, and I was never left in limbo.

The interview itself was fairly straightforward. The first interview involved a discussion of software engineering and projects I've worked on in the past. The interviewer was nice and probed enough to ascertain my knowledge.

The bad interview I had ended up ruining the entire process for me. I was interviewing for an app development position but never actually talked to the app developers who were interviewing me. One person left me in a room by myself with vague instructions to create a search feature. After a little less than an hour and a half, I was told that time was up. By then, I had created the search feature using the libraries they use and written it in a way that demonstrated my ability to create production-level code in an interview. It wasn't perfect, but given the time limit, I did an exceptional job.

I never spoke to or saw the person who left me in the room. Instead, I spoke with two other developers who asked me a bunch of very simple questions about my approach. They never indicated anything wrong with my code or asked specific questions.

I was informed later that I did not get an offer because I did not complete the assigned task. From my perspective, I not only completed it but used it as an example of my knowledge of their stack and how easily I can work with it. Apparently, my RecyclerView item did not contain two views that they wanted to see. Those views were mentioned once but never asked about when going over my approach to the task.

I am not claiming to be the best app developer, but I do know what I am doing. If anyone had asked about those views, I would have very simply added them in an efficient way. My mistake was thinking that they were looking for a well-made search feature and not simple layout design.

Questions

Given an endpoint, create a search feature.

Was this helpful?

Interview Statistics

The following metrics were computed from 82 interview experiences for the Airbnb Software Engineer role in San Francisco, California.

Success Rate

20%
Pass Rate

Airbnb's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.

Experience Rating

Positive43%
Neutral23%
Negative34%

Candidates reported having mixed feelings for Airbnb's Software Engineer interview process in San Francisco, California.

Airbnb Work Experiences