Taro Logo

Software Engineer Interview Experience - United States

December 24, 2015
Negative ExperienceNo Offer

Process

The whole process for intern goes like this: first you complete a pre-interview questionnaire and a code challenge, as I've heard from other people, some people will get very easy questions, and some people will get hard questions, good luck getting the easy ones. If you do well in the code challenge, you'll have a 45 minutes technical phone interview. And maybe there will be a follow up phone interview. If you pass the technical interview, you will interview with the team that you interested in.

First need to finish a code challenge, 2 questions in one hour. The first was extremely easy and the second one my solution times out many test cases, I think that's why I got rejected. One thing to say is that I didn't receive an email telling that I was rejected, only that I never hear back from them. I don't think it's a courteous way to treat applicants.

Questions

The second question is given an array of integers, output an array that contains the number of prime factor for each integer. My solution gets too slow, but maybe it's just Python is too slow for this problem.

Was this helpful?

Interview Statistics

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

Success Rate

16%
Pass Rate

X's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive38%
Neutral33%
Negative29%

Candidates reported having mixed feelings for X's Software Engineer interview process in United States.