Taro Logo

Software Engineer Interview Experience - Seattle, Washington

October 1, 2016
Positive ExperienceNo Offer

Process

The speed at which the interviewing timeline happens is very welcome. Most companies take weeks to provide feedback and then relay their decision. Facebook did this in a matter of days, which is definitely an advantage in snagging top candidates before they commit to other companies. Overall, the process took three weeks from receiving an email about an on-campus (university) interview to the final decision after an on-site interview.

I applied through the career fair at my university and received an on-campus interview the following week. I passed that interview and then went on-site in Seattle about a week later. During the on-site interview, I felt I choked and became too nervous. Overall, the questions were challenging, but nothing extremely difficult.

During the on-campus interview, the structure involved about five to eight minutes discussing my background, followed by a technical question, and then time for me to ask the interviewer questions. However, during the on-site interview, the interviewer introduced himself and then immediately stated we would try to get through two technical questions. We started the questions and completed about one and a half. It would have been possible to get through both if I had been less nervous.

The biggest con to the overall process was the lack of interaction with my interviewer on the on-site interview. I felt he didn't get an accurate sense of my ability as an overall programmer and peer, as there was no chance to introduce myself. Due to this, I didn't get a chance to converse even a little bit before doing the technical questions, which I think might have helped me relax.

Overall, a good experience, but I wish there had been a chance to be a little more personable with my on-site interviewer.

Questions

Print a graph in column order, starting from left to right.

Implement a queue using a circular buffer.

Write a function that takes an integer and prints its English text representation. For example:

Input: 1432 Output: 'One thousand, four hundred thirty-two'

Was this helpful?

Interview Statistics

The following metrics were computed from 106 interview experiences for the Meta Software Engineer role in Seattle, Washington.

Success Rate

17%
Pass Rate

Meta's interview process for their Software Engineer roles in Seattle, Washington is very selective, failing most engineers who go through it.

Experience Rating

Positive54%
Neutral31%
Negative15%

Candidates reported having very good feelings for Meta's Software Engineer interview process in Seattle, Washington.

Meta Work Experiences