Taro Logo

Software Engineer Interview Experience - Seattle, Washington

November 1, 2014
Negative ExperienceNo Offer

Process

  1. Behavior/Past experience
  2. Ninja
  3. Lunch (not rated)
  4. Design
  5. Ninja

The behavior interview is about 1 hour, focusing on your past and current experience and projects. It includes a 15-minute coding test.

The first Ninja session is an opening question where you create your own question based on a scenario and then code it. My experience was really good, allowing flexibility to design questions I was familiar with.

Lunch was a chat with a senior team lead. It was a relaxed opportunity to ask questions.

The Design session was easy for me, as I had worked on a similar system in my current job.

The last Ninja session really sucked. The question involved a really unconventional event processing model using a "pulling" instead of the standard "push" model (like Storm). The interviewer didn't talk much and was unhappy when I proposed a much simpler and intuitive push model. I failed on this one.

Questions

The second ninja (coding) test was about an event processing system using a pulling model, which literally no one in the industry is using.

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