There were 6 interviews total:
There is a lot to be found about Airbnb in general on the internet, so it was easy to be prepared for the cultural interview and understand what they were looking for. I must say I also enjoyed preparing for the technical aspect of the interview, reading about the coding practices at Airbnb, their technical choices, etc.
The interviews proceeded as follows: functional, lunch, technical, functional, cultural, technical, cultural. I was a bit caught off guard by the last cultural interview because, taking lunch into account, I assumed I had completed my 6 interviews.
The technical interviews weren't very difficult. Recruiters were trying to help, like spotting typos rather than watching you fail. I completed the interviews feeling I had solved the problems posed. One involved handling some front-end interaction in JavaScript, and the other was more about objects, context, functions, etc.
The cultural interviews were conversational. I really feel I hit it off on the first one. For the second, I was a bit tired and didn't start so strong, but we had a good talk, though.
The functional interviews involved me showing projects. These were personal projects I was happy with in terms of interest and execution.
In the end, I didn't get an offer and didn't know why. The recruiter delayed in giving an answer and couldn't offer feedback.
That was really disappointing because I don't know where I failed or what I could have done differently.
Handle interaction with elements in a web page.
The following metrics were computed from 82 interview experiences for the Airbnb Software Engineer role in San Francisco, California.
Airbnb's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Airbnb's Software Engineer interview process in San Francisco, California.