Taro Logo

Software Engineer Interview Experience

January 9, 2015
Negative ExperienceNo Offer

Process

Applied through an employee referral.

Failed on a phone screening. The interviewer spoke extremely fast. In addition, there was a strong reverberation (it looked like she spoke in a large room) over the line. As a result, I mostly guessed her questions. Even when I asked her to repeat a question a few times, she didn't change anything in her speech. I've had phone interviews before, and they were good enough, but this one was hell.

Besides a few usual questions about previous experience and the reason for changing jobs, there were only two technical questions, both about algorithm complexity (O-notation), which were quite useless. I think I answered them correctly (it makes no sense to remember them anyway).

It took about 20 minutes. Overall, it was a terrible experience. The worst part is that I failed not due to a lack of technical skills, but simply because of communication issues. I have a lot of Java experience (they had open positions for it) and some other modern tools and technologies, and I am open to learning new technologies. Unfortunately, I haven't had any chance to demonstrate this on any technical phone interviews.

Never again.

Questions

Had no chance for such questions. Only useless questions about the complexity of algorithms (every developer understands when data structure A is faster than B for insert, delete, or search).

Was this helpful?

Interview Statistics

The following metrics were computed from 1,861 interview experiences for the Meta Software Engineer role in United States.

Success Rate

14%
Pass Rate

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

Experience Rating

Positive54%
Neutral30%
Negative16%

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

Meta Work Experiences