I applied through a recruiter. The process took 2 weeks. I interviewed at Airbnb (San Francisco, CA) in Apr 2017
Interview
Recruiter reached out to me with a very nice email. 1st technical phone screen was not hard, 45 min I finished in 33min or so. They use CoderPad, need the code to be compilable and fully working. They skipped 2nd phone screen for me, invited me to onsite directly. Free lunch. Onsite still 45 min each for coding sessions, and 30 min each for non-coding sessions mostly. I ran out of time for the coding sessions, didn't make them fully working. Got rejected after two days. Suggest should prepare/practice more for making the coding fully working within the 45 time window before coming for Onsite. The recruiting team were very professional, friendly, helpful, responsive, and welcoming throughout the entire process, especially the initial recruiter. My suggestion to the recruiting team is better to arrange one or two 10 min breaks between the onsite sessions. No offer, but good experience.
Interview questions [1]
Question 1
Tree related, and others. Need write fully working compilable code. Can't say much, coz of NDA.
I applied through a recruiter. The process took 1 week. I interviewed at Airbnb in Apr 2017
Interview
A recruiter reached out to me via email. We scheduled a phone interview for the following week. The interview used CoderPad. My interviewer went straight to the question as soon as he called. He also wasn't very helpful in nudging me along when I got stuck. Overall, the interview felt a bit cold compared to some of the other unicorns I've interviewed with. Later in the day, my recruiter called to let me know they wouldn't be moving forward with my candidacy.
I applied through other source. I interviewed at Airbnb in Mar 2017
Interview
Phone interview, and onsite. Phone interview went well, although I was a little dismayed when the interviewer didn't understand why someone would want to set functions in the constructor for JavaScript. (I was trying to demonstrate using a closure in javascript's new class syntax).
On site interviews started out great, the first 2 behavioral interviews where conducted by some excellent folks that both offered very good information about AirBnB.
The experience interview was conducted very poorly, the interviewer required continual explanation of terms to the point of it heavily disrupting the interview. This included questions like "what do you mean by low power machines" when talking about performance concerns. I am not sure if it was to try and sound more engaged, or if they actually didn't understand these concepts.
The technical interviewers were a mixed bag. Two were conducted extremely well, while the other was unprepared and was half asleep.