Taro Logo

Software Engineer New Grad Interview Experience

November 29, 2018
Negative ExperienceNo Offer

Process

I applied online and was quickly emailed back for a recruiter chat, followed by a phone interview, and then an onsite visit.

Most of the experience was great. I really felt that the recruiters were on top of their game and passionate about the product. They were honest and transparent, which is a breath of fresh air compared to most other companies.

Most of the engineers I spoke to genuinely cared about their product and were great to talk to. In comparison to other places I've interviewed, they placed a heavy emphasis on ensuring cultural fit, with a few behavioral questions during the onsite.

However, the reason I rate this experience overall as negative is that one interview during my onsite significantly detracted from the overall experience. There were three technical interviews, two of which were LeetCode-style algorithm problems.

The third interview, however, was different. I had informed the company beforehand that I preferred interviewing in Java. Despite this, at the start of the interview, I was asked to use Python. Even when I stated I wasn't familiar or comfortable interviewing in it, the question prepared was Python-specific.

The question involved using a feature of Python I had never encountered before, either in coursework or in practice, to solve a hypothetical problem. Consequently, I struggled significantly to comprehend it. I spent a considerable amount of time asking the interviewer clarifying questions, which I could tell was beginning to make them impatient.

I managed to get through part of the question correctly but was unable to complete all the challenges due to my questions. This ultimately resulted in me failing the onsite.

While it's fair game to ask about anything on my resume (I had listed experience with Python for a project), it felt akin to attending a lecture on a new topic and then being given an assignment on that topic to complete during the explanation in order to pass the class. It wasn't a pleasant feeling, and I didn't feel I was being accurately assessed on my programming abilities.

I hope they will reconsider using questions like this. Additionally, I encountered two separate issues with trip expenses that required resolution. The individuals who assisted me were very apologetic and resolved them quickly, but it added further stress to an already disappointing experience.

Questions

Recruiter chat 1 LeetCode question during phone interview 3 technical interviews during onsite 3 behavioral interviews (lunch, PM, hiring manager, I recall)

Was this helpful?

Interview Statistics

The following metrics were computed from 13 interview experiences for the Affirm Software Engineer New Grad role in United States.

Success Rate

31%
Pass Rate

Affirm's interview process for their Software Engineer New Grad roles in the United States is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive62%
Neutral31%
Negative8%

Candidates reported having very good feelings for Affirm's Software Engineer New Grad interview process in United States.

Affirm Work Experiences