Senior Software Engineer Interview Experience - United States
Process
The interview process consisted of a standard LeetCode medium phone round followed by an onsite round.
I received a canned rejection email a day after the onsite. I sent multiple emails asking for feedback but received no response.
How poor is a process and company where a recruiter cannot take five minutes to call and share feedback after a candidate spends eight hours interviewing? I have no idea where the mismatch occurred, and I will probably never know.
I will never interview with them again.
Questions
Some standard LeetCode-style problems, a system design round, and a behavioral round with a manager.
Was this helpful?
Interview Statistics
The following metrics were computed from 4 interview experiences for the Airtable Senior Software Engineer role in United States.
Success Rate
Airtable's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very negative feelings for Airtable's Senior Software Engineer interview process in United States.
Airtable Work Experiences
- 3.0It used to be amazingSenior Software Engineer • Current EmployeeSan Francisco, California, United StatesJanuary 22, 2024Pros: WLB is good, pay used to be good.Cons: Exit (IPO, acquisition) is looking harder and harder.
- 5.0Great company and interesting productSenior Software Engineer • Current EmployeeSan Francisco, California, United StatesJanuary 10, 2024Pros: - Strong engineering teams - Interesting product and problem domain - Great potential to achieve larger market share in the enterprise solution spaceCons: - Competitive category - Growth slowing down with the broader macro environment
- 3.0Too much red tapeSenior Software Engineer • Former EmployeeSan Francisco, California, United StatesSeptember 14, 2023Pros: Great work-life balance, good compensation, unlimited PTO, and hybrid work (effectively remote as we have to go once a quarter to the office).Cons: A lot of red tape in development. The gut instinct of a select few triumphs over any data that you may have. If you want to build anything, there will always be someone who says no. There is no one to take a technical leadership role, so for building everything, we need to have consensus among everyone to do it. If you have heard alternate truths on the news, you will hear about alternate design principles here. My manager actually used the word "alternate principle" when I tried to point out the design flaws by pointing out basic CS principles. Design disagreements never get resolved as there is no technical leadership.
