# Completed Airbnb's Staff+ loop - here are my thoughts — retained record

> Retained reddit record from reddit:cscareerquestions.

Canonical: https://highsignal.app/data/records/7fe5bc894dd58c97

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:cscareerquestions)  published 2026-09-19 20:36 ingested 2026-09-20 02:36

[original source ↗](https://www.reddit.com/r/cscareerquestions/comments/1wkwvym/completed_airbnbs_staff_loop_here_are_my_thoughts/)

## retained text



```
EDIT: Removed the links to the tagged questions since many people seem hung up on this being a potential ad. I understand, we're all tired of ads. Now back to the aim of this post, providing clarity on the process.

**Summary**

I just completed Airbnb's Staff+ loop recently and I want to share some thoughts about the process, the timeline, my preparation strategy and feelings about the future as I wait for the result.

**Background**

I have interviewed with Airbnb for a senior role about five years ago and bombed so bad in the very first round that it made me question my choice of career.

This time, a sr recruiter reached out to me on LinkedIn in July and I formally started the interview process soon after that. I believe Airbnb changed its loop structure (not sure if it's for all levels or for staff+ only) during this time so there was *some* churn on the interview structure as I was going through it.

**Process**

We scheduled a quick phone call to go over the process that looks like this at a high level:

|Round|Format|Notes|
|:-|:-|:-|
|HM Screen (1x)|60 minutes; a mid-level conversation about my work ex., preferred areas of work, team's area of work, short to mid term challenges the team faces etc.|It is my belief that beyond helping Airbnb decide if they should spend time interviewing me, it also helps decide the level I should continue interviewing for.|
|Architecture (2x)|60 minutes; 1 system design problem, few follow up questions on scaling, edge cases, CAP theorem tradeoffs etc.|What I found most interesting was that they turned out to be super engaging conversations between two staff+ engineers about interesting edge cases in the given problem and clever optimizations one could add. The actual diagramming I did was super minimal and I was told not to worry about it since the conversation is going in the "right" direction.|
|Experience Interview (1x)|60 minutes; a low-level conversation with a staff+ engineer about my work experience in general and up to two long-running, large-scale projects specifically.|I always have two slide decks (with diagrams) lying around to explain two of my recent/favorite projects. It also helps that one of the large features I've shipped is publicly used by about 2 billion MAUs so I use that as a "live" demo, too! The conversation then went deep into all the real-life sharding issues, and operational concerns one deals with at that scale.|
|Coding (1x)|45 minutes; a heavily modified version of a popular problem tagged to Airbnb.|I was able to quickly solve the problem, clear the edge cases and get it to run. We spent the rest of the time optimizing it for runtime and discussed how something like this could be deployed in production.|
|Core Values (x1)|60 minutes; a behavioral round seen through the lens of Airbnb's [core values](https://careers.airbnb.com/life-at-airbnb/).|This turned out to be more deep and personal than any interview I've taken or given. Very interesting!|

**Timeline**

I had a great time managing the timeline for this loop. I really appreciated the level of flexibility Airbnb offers candidates. You get your own portal where you can track and manage your interview process with them. You can request reschedules (latest by an hour before the interview) and push interviews away as far as you need.

**Preparation Strategy**

Preparing for this loop felt really smooth compared to some of the loops I've given before. Something that really helped this time around was the sheer of volume of interviews I've conducted on behalf of my current employer. I got really used to the process, its stated claims, and ways to optimize those 60 minutes from one side of the desk, that it made the other side very approachable.

I did not prepare for my architecture interviews at all. One of my unpopular opinions is that any staff+ engineer should be able to give an architecture interview in a moment's notice. It's very simply a narrow application of something you ought to be doing everyday at work, at least ideally.

I always go back to [this video](https://www.youtube.com/watch?v=PJKYqLP6MRE) by Jackson Gabbard as my foundation for preparing for behavioral interviews and this time was no different.

For the coding rounds, I focused on the Airbnb tagged questions. This was very helpful.

I would also recommend this sequence of processing coding problems as it really helped me:

1. Verbally explain the naive solution (e.g. to pick the Kth largest element, we could simply sort this array and pick the Kth element from the end) and why you wouldn't want to implement that.
2. Write down your proposed solution as a multi-line code comment. If possible, outline possible edge cases or rooms for optimization right away.
3. Write down the key steps of your algorithm as single line code comments and get buy-in.
4. Write actual code by expanding the single line comments into actual code.
5. Perform a dry-run and keep optimizing as much as the time allows.

**Closing Thoughts**

I had a great time preparing for and giving these interviews. I am optimistic about receiving a hire decision but not very sure about the leveling (I'm staff now but would like to land Sr Staff). But nothing is guaranteed until I get the news. Time to enjoy not having to grind PracHub and crack open a cold one.

Happy to answer your questions but please do not DM me.
```



document fetched 2026-09-20 00:23 · canonical https://reddit.com/r/cscareerquestions/comments/1wkwvym/completed_airbnbs_staff_loop_here_are_my_thoughts
