Airtable Interview Questions

What Airtable asks looks a great deal like what Airtable builds. Across 16 recorded questions, 14 of them from Software Engineer interviews, the problem that keeps returning is undo and redo for a spreadsheet, which appears twice, once framed explicitly around making the command history extensible. Around it sit questions on serialising JSON that contains circular references, picking the data structures behind a dispatcher's scheduling loop, and designing a search service that shards as it grows. One prompt comes straight off the product roadmap: design an assistant that turns natural language into an Airtable formula. Category weight is unusually flat, 4 each in software engineering fundamentals, system design and coding, so no single track carries the decision. The pressure sits late in the process rather than early, with 11 of the 16 asked onsite. Only 3 questions open a runnable console, since most of this is modelling and discussion, though 13 arrive with a written solution to check your design against. Difficulty leans gentle next to the coding-heavy banks, 11 medium and 4 easy against a single hard question, so what sinks candidates here is a vague design answer rather than a missed algorithm.