real interview stories, told over a cup of tea ♡
Airtable Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
11 results
- Undo/Redo Design Round Plus a HyperAgent Take-HomeAirtable · Software Engineer · Senior+ · Onsite · Jul 2026
I was picked by the recruiter for the product omni team, working on Airtable's vibe coding agent. Airtable recently acquired DeepSky to build HyperAgent, and there are plans to connect it with Airtable itself, so it's basically multi-agent development (HyperAgent -> Omni). Recruiter call - 30 minutes, phone screen: why Airtable, what project I wanted to work on, my relevant past experience. Codin…
- Airtable Software Engineer interview with a sharp system design rampAirtable · Software Engineer · Online Assessment · May 2026
I started with an online assessment whose questions felt close to the kind of work Airtable actually does. After submitting it, I moved into a coding round focused again on data structures and algorithms, though it was framed more like a real-world task than pure LeetCode. The time limits and scoring varied, but the expectation stayed consistent: write clean code, handle edge cases, and make it w…
- Airtable Software Engineer interview: spreadsheet-style workflow screenAirtable · Software Engineer · HR Screen · Apr 2026Rejected
My first real step was a recruiter and phone screen combination. The recruiter was responsive and easy to follow, and the phone interview itself felt conversational. The follow-up questions seemed intended to understand how I thought rather than check whether I could recite a familiar pattern. The topic involved an Airtable spreadsheet-style feature. The recruiter had warned me that it wouldn't b…
- Weak BQ, a Dispatcher Coding Round, and a Fast RejectionAirtable · Software Engineer · Onsite · Feb 2026Rejected
Onsite. The rest of the loop covered questions that have already been discussed elsewhere, so I won't go over them again in detail. The behavioral question round was the usual boilerplate. I hadn't prepared for it, and I also didn't click with the hiring manager, so I answered pretty badly — I'm guessing this is where I get rejected. One of their signature questions: they push an inclusive cultur…
- Airtable Customer Success Engineer interview: scripted questions and unclear system promptsAirtable · Customer Success Engineer · Other · Oct 2025Rejected
The process started well. The recruiter seemed organized, and I was excited about the opportunity. Once I reached the interviews, though, it became difficult to take the process seriously. In one session, I was put on hold immediately. The recruiter then read questions from a script without much back and forth, and I didn't feel the interviewer was genuinely engaged with my background. The hiring…
- Airtable Full Stack Engineer interview: UI flow and hierarchical dataAirtable · Full Stack Engineer · Online Assessment · Feb 2025
I went through a longer interview loop that started with an online assessment and then moved quickly to a phone interview. The phone screen used an Airtable-style scenario. That set the tone for the live coding portion, where the questions were meant to feel realistic and the follow-ups focused on explaining my choices, not just producing working code. After that, I had several technical intervie…
- Airtable Software Engineer interview with live-coding trick questionsAirtable · Software Engineer · Technical Screen · Jun 2021
Recruiter outreach started the process, and the early conversation felt more like pressure to apply than an authentic screen. I then had a technical phone screen that felt like a live-coding trick problem. It seemed less focused on my actual experience and more focused on whether I noticed a specific inefficient behavior or used a particular "special term" they wanted to hear. The experience felt…
- Airtable Software Engineer take-home that took six hours or moreAirtable · Software Engineer · Take-home Project · Apr 2021
My process began with a call with a hiring manager, followed by a take-home assignment that took a very long time, six hours or more. After that, I went through an onsite that lasted six hours and included multiple rounds. There were coding and algorithm questions, design questions, a code review, and a culture-fit conversation with the hiring manager. The process felt manageable at first because…
- Airtable Software Engineer take-home assignment that took roughly eight hoursAirtable · Software Engineer · Take-home Project · Feb 2021
My recruiter call was followed by a take-home assignment that was supposed to take about four hours. The work didn’t feel close to that scope. I was expected to build a fairly substantial front-end library from scratch to support a complicated chart, something in the neighborhood of d3-style functionality. I spent roughly eight hours on it and still didn’t finish. After submitting it, I never rea…
- Airtable Software Engineer interview: six-hour coding exercise and $200 certificateAirtable · Software Engineer · Take-home Project · Jun 2020No response
I applied online and heard back quickly about a recruiter call, but the tone felt scripted and quota driven. It seemed like the person on the other end wasn't closely involved with the team or the role. The next step was a six-hour coding exercise before I had spoken with anyone from the actual team. I was told I'd receive a $200 Amazon gift certificate for completing it, but the exercise didn't…
- Airtable Software Engineer interview: five-hour assignment and six-interview onsiteAirtable · Software Engineer · Take-home Project · Dec 2019Offer
I started with a long independent programming assignment instead of a typical phone screen or live challenge. It took around five hours, and I received a $200 gift card regardless of how it went. The next step was an onsite in San Francisco with six interviews in one long day. The mix stood out right away. One interview focused on practical algorithms and design rather than the usual LeetCode sty…