The interview process started really well. I really liked that they offered the option of a take-home assignment, which I thought was complex but very interesting.
The virtual onsite was standard. I spoke with the Hiring Manager, had a take-home project review, a standard coding question, an API/Database design question, and a mobile-specific coding exercise. All were pretty interesting, and I found them easier than the take-home assignment.
Where the experience went completely off the rails was after the interviews. I was asked for references two days later, which I thought meant they would be making an offer. However, after that, I didn't hear anything from them for 10 days. I only got an update after sending two emails, and the response was basically just "we still don't have an update." After three more days, I asked for updates again, and the response I got was again "no updates." Finally, 10 days later, they sent me an email saying that they decided to go with a "more junior" candidate.
In total, it took almost a month to get a response after the interview. I only got updates because I asked for them. I'm sure that if I hadn't sent emails asking for updates, I never would have heard from them. All this time, the team knew I was on a tight deadline.
Take-home iOS coding assignment
Generic coding question
API/Database design
Mobile-specific coding exercise
The following metrics were computed from 1 interview experience for the Airtable Mobile Software Engineer role in San Francisco, California.
Airtable's interview process for their Mobile Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Airtable's Mobile Software Engineer interview process in San Francisco, California.