Taro Logo

Software Engineer Interview Experience

June 26, 2015
Negative ExperienceNo Offer

Process

The interview process started with a screening test where I was given two relatively simple problems to solve online.

Next, I progressed to an interview on their CodePair platform with one of the founders. During this interview, I was given a more difficult, but still quite doable, problem, followed by some informal discussion.

Finally, I was tasked with building a plugin for a text editor or IDE of my choice that would integrate the HackerRank API.

I spent a significant amount of time coding this last project and was looking forward to receiving feedback. However, I never heard back from them after that point, which was a few months ago.

Even if they had determined my programming skills were lacking, I would have expected some form of communication after the time I invested in the process. It seems to me that these individuals may not possess a great deal of empathy or consideration for others.

I ended up accepting another job shortly after this experience, so it was not a major setback. However, I definitely lost a lot of respect for HackerRank, which is disappointing because I believe they offer an excellent product.

Questions

In the CodePair interview, I was given a dynamic programming question that was a little tricky. They didn't care about complexity, though, and the problem was not too difficult to solve with a Big O of n^2.

Was this helpful?

Interview Statistics

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

Success Rate

0%
Pass Rate

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

Experience Rating

Positive22%
Neutral22%
Negative56%

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

HackerRank Work Experiences