Initial communication is with the recruiter. Then you get a take-home test. If that goes well, you move to a phone screen, then an onsite interview.
The take-home test is a 90-minute test that you need to submit over HackerRank. In this case, it was an incomplete app that needed certain features to be added. However, the app didn’t build initially, which cost me a ton of time to try and build.
Keep in mind that they give you a test app, and if it builds, then the actual real test app that’s incomplete should build too. However, this wasn’t the case, so I spent the first half of the 90 minutes trying to figure out how to fix the Gradle issues I was getting.
I followed steps from Stack Overflow from someone who had a similar issue and solved it. However, it didn’t fix the issue. I ended up creating a project from scratch and copying over files one by one. By the time I was done, I barely had time to do one feature.
They didn’t move forward, and I expressed to them these issues. However, I don’t think they cared.
Improve an Android app
The following metrics were computed from 1 interview experience for the Airbnb Android Engineer role in San Francisco, California.
Airbnb's interview process for their Android Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Airbnb's Android Engineer interview process in San Francisco, California.