Messy. The process started with an Airbnb recruiter reaching out to me. I agreed to an interview and was scheduled for the following week.
Come time to start the interview, I never received a call. I went back to check if my number was correct, and it was. I emailed to inquire what happened, only to find out the recruiter had transferred, quit, or been fired. Luckily, the second recruiter got things back on track.
After a couple more emails, I learned the second recruiter would transfer me to a third HR person. I had to wait another couple of days to find out the interview was scheduled a second time. During this back and forth, I explained that I was looking for an SRE/DevOps position, but they still wanted to test coding skills. Fine.
Come interview time, I was asked the palindrome question. After the general introduction and Q&A regarding the problem, I had 30 minutes left to code. While I don't code day to day, I know my way around. I began to construct the brute force solution as agreed upon. After completing and passing all test cases provided, I thanked the interviewer and hung up.
Palindrome from LeetCode
The following metrics were computed from 1 interview experience for the Airbnb Infrastructure Software Engineer role in United States.
Airbnb's interview process for their Infrastructure Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Airbnb's Infrastructure Software Engineer interview process in United States.