The process began with an initial recruiter call, followed by a take-home assignment. I breezed through the take-home assignment in three days and was subsequently invited for a virtual onsite interview.
To begin with, their product was overwhelming to understand. However, they have decent documentation on their website. The company employs smart engineers (ex-Facebook, Google, etc.) and they were straight to the point during my interview. There was no "tell me about yourself" prompt; they appeared very busy, or at least seemed that way.
The onsite interview consisted of four different rounds with four engineers and a director.
The first two rounds were fairly okay. The final two were where things started to get really weird.
In one round, the engineer stated it was his first time interviewing SDETs and mentioned his partner was an SDET at Google whose role was canceled. While I understand that roles like SDETs may not exist at large companies like Google or Facebook, it's important to remember:
This made the experience very awkward. In the last round, there was one engineer and a lead engineer. The lead engineer only showed up for the last 5 minutes of the interview, which was very unprofessional and seemed like they were completely disinterested.
Here's what we were asked to do:
The following metrics were computed from 2 interview experiences for the Airtable Software Developer In Test role in United States.
Airtable's interview process for their Software Developer In Test roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Airtable's Software Developer In Test interview process in United States.