The total process from start to finish was around 3.5 weeks.

I had a referral and outstanding offers from two "big 4" companies, so they did a great job of hurrying along the process.

I had two phone screens.

The first was an interesting problem that's not currently on LeetCode in any variant. I'd rate it somewhere between LeetCode medium and hard. I barely finished it in time, as I was debugging for the last 15 minutes.

The second phone screen was a LeetCode easy/medium problem. The trick is not to overcomplicate it.

Onsites consist of several interviews: some are coding interviews, some are architecture interviews, and some are fit interviews.

Unlike other companies, Airbnb prefers a working solution within the allotted time, even if it's suboptimal. Your code is expected to run. So, I'd recommend taking no more than 10-15 minutes to come up with the algorithm. Start coding up the naive solution if you're stuck, and if you have time at the end, you can explain a better algorithm to use.

The fit interviews are pretty straightforward. This isn't something you should "study" for, but read up on Airbnb's core values and think about how you align with them. They care a lot about fit, which is probably why everyone seems so awesome to work with.

The architecture interview was much more intense than any of the tech giants. I found it to be highly disorganized, but we basically did a deep dive into a system. If you're an experienced engineer, you'll find it fast-paced but not terrible.

The experience interview is very pleasant. You talk about cool projects that you've worked on and how they work.

Due to an NDA, I cannot provide specifics, but I strongly suggest studying:

• Graphs
• Networking
• Less common data structures like tries/radix trees and min/max heaps
• Bit manipulation
• Searching (BFS, DFS, binary search)