Taro Logo

Software Engineer Interview Experience

February 20, 2017
Negative ExperienceNo Offer

Process

I was contacted through LinkedIn about an opportunity at Facebook. I pondered whether to give it a try or not. My impression was that Facebook was a PHP shop, and as a Scala developer, I felt it wouldn't align with my skillset (and I had no interest in returning to dreaded C++ either). After some deliberation, I agreed to a phone interview.

I have pretty good experience (10+ years). Most of these interviews are not cakewalks, but they're not hard either. My only concern is the need for absolutely neat, monkey-coded, textbook solutions within 30-40 minutes. Most interviewers are nitpicky and want perfect code. You typically have 10 minutes to think and 30 minutes to code in a CollabEdit session. Unless you can "monkey code" the solution while talking to the interviewer, it's best to simply avoid these. It's nothing but sheer nonsense. But if you want to practice, then ;-)

Questions

The interview called up 30 minutes late and was rushed through.

Given a string, break it up into meaningful sentences: "thesystemisrunning" => the system is running.

After 3 weeks, I got a call for another interview.

Given a million integers, find the kth smallest.

Got a call saying they needed to take another interview. I was nearly about to say thanks but no thanks, but ended up taking it just for practice.

LRU cache, which gives the latest accessed element.

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