Two phone screens. None of the questions were from LeetCode.
In my first phone screen, I coded up the solution but got stuck solving the edge cases, so I probably got passed on for a second phone screen.
Onsite was 6 rounds + lunch. Two of those interviews were culture fit interviews.
No prep needed for the culture rounds, really. Just be yourself and chat candidly and you'll be fine.
Two rounds were coding rounds, which involved writing the solution in an IDE, compiling it, and testing it against their test cases. The questions were pretty straightforward.
There was a system design round and an experience round.
The system design round was like any other system design round, but with less fluff about technologies to use and more about identifying bottlenecks, improving them, and getting the data model right. I really enjoyed the system design round.
The experience round was just me explaining one of my most recent projects.
Overall, a very good experience. I had a lot of fun talking to the engineers there.
NDA
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.