Taro Logo

Software Engineer Interview Experience

August 3, 2020
Negative ExperienceNo Offer

Process

Worst Interview Process.

This process involved a long take-home assignment, estimated at 6-8+ hours, requiring the implementation of multiple features based on a redline mockup and provided media assets. The assignment felt like an entire workday with overly detailed requirements to achieve perfection. Following this, there was absolutely no feedback from the hiring team. The process only consisted of two rounds; candidates could only proceed to the next onsite group round if they successfully completed the lengthy and detailed written coding assignment.

The only person candidates interacted with was the recruiter, who immediately assigned the take-home task. This task involved a fully functional feature story with many sub-assignments, compensated with a petty gift card and no feedback on performance. Completing this take-home interview, with its numerous detailed project requirements and sub-parts, took an entire day.

In addition to building multiple elaborate features, candidates were also asked for detailed written documentation on their project's development process, how they would code the next story, how to create a project plan, and recommended best code practices. After submitting the code, a week later, vague reasoning was provided for not being selected for the final round, despite the project being fully functional and meeting all specified requirements.

This felt more like a knowledge transfer assignment on feature development rather than a hiring interview. My takeaway is that the company is using candidates to complete difficult work for the low cost of a petty Amazon gift card, while wasting candidates' time.

Questions

Build multiple (3-4) elaborate features, following the redline mock exactly and using company assets.

It looked like the same/similar features built during the assignment were implemented on their webpage.

They also asked for detailed written documentation on how the project was made, how the next story would be coded, and how to make a project plan and best code practices to follow, etc.

This seemed more like a knowledge transfer assignment on how to make features, rather than an interview for hiring. My takeaway is they are just getting their difficult work done through petty Amazon gift cards and wasting candidates' time.

Was this helpful?

Interview Statistics

The following metrics were computed from 22 interview experiences for the Airtable Software Engineer role in United States.

Success Rate

9%
Pass Rate

Airtable's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive32%
Neutral23%
Negative45%

Candidates reported having negative feelings for Airtable's Software Engineer interview process in United States.

Airtable Work Experiences