I found this interview process to be unnecessarily lengthy and, relatedly, disrespectful to the candidate. To substantiate that claim, I’ve outlined the interview process I went through for the Analytics track and added commentary on each phase. TLDR: This interview process was unprofessional enough to make me leave this long of a Glassdoor review. A function of: • Too many interviews (n=10) and redundant questions (e.g. was asked ‘Why Airbnb’ 5 separate times throughout the process, was asked a selection of ‘how would you measure x’ questions in 4 separate interviews). People have actual jobs – be considerate of their time. • Arrogant attitude (e.g., not a single interviewer introduced him/herself; out of 10 interviews, there were 5 minutes I had to ask questions). If you want the world to believe your ‘Be a host’ pitch, help your candidates get to know you too – at the very least be friendly. Details: The process amounted to 10 total interviews/meetings which spanned about 3 months from application to decision. A function of: • 1 30-minute phone screening with a sourcer who seemed to be reading from a script and was not knowledgeable enough about the role/team to answer beyond-surface-level questions • 1 45-minute SQL CoderPad interview + 'metrics interview' over the phone (e.g., 'How would you go about measuring Airbnb's customer service team's success?', etc.). The interviewer was unfriendly and seemed annoyed that he had to take the call. He said nothing other than the scripted questions. • 7 on-site interviews/meetings o 1 on-site presentation interview (15 minutes + 15 minutes for Q&A). This was with a panel of 4 listeners. 1 of them was the hiring manager, but I couldn’t tell you who the other people were because no one introduced themselves. Also worth noting, no one smiled. o 1 exploratory data analysis interview (60 minutes), where you’re given a dataset and asked to dig into it o 1 metrics interview (30 minutes), where you’re asked how you’d measure various Airbnb business dynamics + drilled into on what would move those metrics (e.g., what would an increase in x do to the average? The median?) o 1 ‘experience’ interview (45 minutes), where there were 1-2 questions about past project experience and then, mid-way through, a surprise case. This was disappointing because it was the only interview throughout the entire process that was supposed to be a chance to talk to someone on the actual team that the role was on and connect on a personal level at all vs. showing that you can be a human calculator. I had a handful of stories prepared on my work experience, most of which I wasn’t given an opportunity to share. I was also interested in getting to know the manager as a person in this interview – learning about her background or an example project she envisioned the person taking on, but unfortunately she didn’t introduce those things, and there wasn’t much time to ask questions due to the surprise case on the back end of the interview. o 2 ‘cross-functional’ interviews (each 30 minutes), which are conversational and meant to assess fit with Airbnb’s culture/values. These are a really nice concept, but they’re with random people in the organization – it would make more sense to use these an opportunity for the candidate to meet the team. o 1 non-evaluative lunch with a Data Scientist not on the team you’re applying to, meant for asking questions/getting to know Airbnb’s culture better • 1 final ‘case’ phone interview, which again consisted of ‘tell me how you’d measure x’ questions. This really felt overkill – the questions were identical in nature to many of the questions that had been asked in interviews prior. On a positive note, the recruiter responded with a decision within a week and was respectful enough to share the news over the phone. But then, of course, there was no interview feedback offered.