The interview process involved phone screens that focused on background and algorithmic skills, followed by an onsite day of algorithms and personality tests.
Most of the interviewers were a pleasure to speak with, and the coding questions were mostly fun. Overall, the interviews felt collaborative, and the interviewers were mostly genuine in learning about me, my hobbies, skills, and past. Finally, there was no whiteboard coding!
The turning point during the onsite was when one interviewer spent the entire interview playing on his phone. He didn't really acknowledge most of what I said while coding. It was extremely disrespectful, and he was very snobby. The only thing he talked about was himself. I got the same vibe from interviewing at Facebook, so it was no surprise that he used to work there.
Every company has its sour apples, though. Overall, I have a pretty good opinion of the company. The office workspaces were quite crowded but had good food and exceptionally cool meeting rooms.
No algorithm questions were too tricky.
They were designed to see your thought process and were relatively achievable.
There were a lot of personal questions for the culture fit interview, which were both fun and a bit intrusive.
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.