Facebook
4.5 of 5 676 reviews
www.facebook.com Menlo Park, CA 5000+ Employees

Facebook Software Engineer Interview Questions & Reviews

Updated Jul 8, 2014
All Interviews Received Offers

Getting the Interview 

25%
22%
18%

Interview Experience 

60%
25%
13%

Interview Difficulty 

Average Difficulty
326 candidate interviews Back to all interview questions
Relevance Date Difficulty
in

No Offer

Neutral Experience

Average Interview

Software Engineer Interview

Software Engineer

I applied online and the process took 5 days - interviewed at Facebook in May 2014.

Interview Details – The recruiter was excellent and quickly scheduled the first interview, but the manager seemed too busy and unprepared for the interview. When asked about development processes, make sure you show how flexible you are. They aren't looking for candidates who follow a strict SDLC; they want someone who can deal with less structure.

Interview Question – Tell me about the N-1 problem with ORMs.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Neutral Experience

Difficult Interview

Software Engineering Interview

Software Engineering

I applied through a recruiter and the process took 5 days - interviewed at Facebook in May 2014.

Interview Details – Got contacted for a Embedded Software Engineer position. I am a low level developer. The interviewer was a research scientist. Our backgrounds were poles apart. He did not have a clue about the position I was interviewing for. At the end both were wondering why he was asked to conduct the interview.

Interview Question – Sink Zero in Binary Tree.   View Answer

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Negative Experience

Average Interview

Software Engineer Interview

Software Engineer
Seattle, WA

I applied online - interviewed at Facebook in April 2013.

Interview Details – A recruiter contacted me. After a few days of back and forth we set up a phone interview. In the phone interview we discussed a possible problem that involved trees. I struggled to implement the necessary algorithm.

Eventually, I got to ask a couple of questions about facebook.

Received a decline a couple weeks later.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Positive Experience

Average Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

I applied through an employee referral and the process took 2+ weeks - interviewed at Facebook in May 2014.

Interview Details – FB is very efficient in hiring. The HR first sent some regular questions for me to answer, including the time to start working and so on, and then arranged the phone interview directly. On the same day of my phone interview, she arranged for onsite interviews. I was impressed with how efficient they are.

Interview Question – The interview questions were not extremely difficult, but I can tell they want people who understand the most basic concepts really well and can code clean and bug-free at once or after a little bit hints. The design questions were challenging though. Be prepared for that.
The interview questions include two sum, reverse integer, edit distance, clone graph, etc.
  Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

59 people found this helpful

No Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Menlo Park, CA

I applied through a recruiter and the process took 3 months - interviewed at Facebook in November 2013.

Interview Details – This was for a position in their Infrastructure team in Cambridge MA.

Recruiter contacted me in September and was very interested in my background and experience with highly scalable systems - both in Finance and Mobile phone payments.
I attended some small intimate presentations they did as they were initially opening a new Boston office and wanted to grow it out. The meetings were great and I learned a lot about how they solve some of their biggest problems.

I then did a screening interview on-site (because I don't do technical screens well on the phone). The question was "Given a binary tree, write code to print the tree out line by line". I did OK and got the Breadth First Search down fine, but couldn't figure out the - line-by-line part. (Turns out this is Facebook's #1 question to ask in interviews).

Although my performance wasn't great they gave me a break on that and asked me back for another screening interview. This time I prepared well for another coding interview but it turned out to be a Design interview. The problem was

"Imagine you have 10,000 servers and need to monitor the performance of each one, how would you do it" - naturally you need to be able to NOT take too much of the bandwidth and so you'll have to do sampling, have some history to watch for trends etc.

I passed that and was very excited to be flown out to Menlo Park for the final round.
I studied like CRAZY based on questions on this site and CareerCup. I took 4 weeks and studied about 15 hours per week.

Turns out I focused on the wrong questions - I studied Tree, String, Array and List algorithms based on the distribution of Q&A but I was asked Binary math and heap algorithms. Here are the questions I was asked.

1) How would you implement division without +, - or multiplication (a "classic" question, but not one of the ones I would focus on). I bombed on this as I was not expecting and could not recall my binary math. I figured out the high level outline but that was all. That I was asked this in the "culture fit" interview made this doubly unexpected.

2) Given 10,000 servers containing a Billion integers each how would you find how to find the median? I knew the answer to this question (use two heaps) - not because I had focused on it, but I had found it an interesting question while studying. However he then asked "How much memory do you need?" and I didn't know how big the heaps would need to be. The real answer I was trying to get is - what is the minimum heap you need. I had a guess but I think I got this wrong.

3) Given a List structure where each node contains a Next node and optionally a pointer to another list, flatten that list
e.g.

L1 --> L2 --> L3 --> L7 --> L8
                      |
                      v
                     L4 --> L5-->L6

WIll be flattened to
L1 --> L2 --> L3 -->L4 -->L5-->L6-->L7-->L8

I did OK on this - getting the answer - but it appeared I took too long. The interviewer also interrupted me a lot while I was writing an initial solution and that threw me off - I like to be more iterative in my problem solving but I think he expected 100% immediate correctness.
He had an observer there too and that guy looked bored out of his mind and that bugged me a little too as it wasn't clear who would be doing the judging.

4) I was also handed some hard to read Python code (I don't know Python) and asked to figure out what it does. I did OK on this - but again surprised to be handed hard-to-read code in a language I didn't know.

5) One final question "How would you implement the "ls" Unix function in your language of choice. It should take the input:
>ls a/b/c/*/e/*/f/*/*/g
and the output should be similar the the output given by unix."

I used a tree structure to represent the file directory structure and wrote a solution from there. I did OK on this.

Overall: Everyone seemed very nice - I had a nice lunch and the campus is interesting but it was clear that what I studied was not what I needed to (so lesson learned: don't just trust the distribution of questions on Glassdoor or CareerCup). I even got to walk past Zuckerberg's office (more of a conference room) and saw Sheryl Sandberg in there.

One interesting thing I learned is a lot of Google people are leaving for Facebook. Also I'd say if you are over 30 (I am 41) you are a rare bird at Facebook :-)

I knew based on the reactions of the interviewers that it was very probably a bust, but overall a good experience and something I will learn from. Very disappointing as I really wanted to be one of the first few Facebook engineers in the Boston area - and to work on their super high scalability issues but such is Life.

Interview Question – How would you implement division without +, - or multiplication   View Answers (5)

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Neutral Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Palo Alto, CA

I applied through an employee referral and the process took 1+ week - interviewed at Facebook in April 2014.

Interview Details – Was referred by an employee working at Facebook. Was paired with a HR guy who facilitated the process via email. Did a phone interview with an engineer about a week after first contact. Did the technical interview and was told I would get a decision within the week. Didn't get a response after trying to follow up so I took it as a no.

Interview Question – The interview was pretty straightforward. The technical question had something to do with rearranging letters in a word, can't remember the details anymore.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Menlo Park, CA

I applied through a recruiter and the process took 4 weeks - interviewed at Facebook in November 2013.

Interview Details – Interviewed in November 2013. Initially contacted by a recruiter through LinkedIn. Entire process took around 3 or 4 weeks. Two initial interviews followed by an onsite interview. The initial interviews went well, but I failed onsite I believe. The company is very chill overall; they had a keg in one of the rooms when I visited.

Interview Question – Asked to do a presentation on a specific topic for the entire team.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Negative Experience

Very Easy Interview

Software Engineer Interview

Software Engineer

Interviewed at Facebook

Interview Details – A recruiter set up a short chat and ask some behaviour questions, and bad things happen. She ask me some cliche questions like "why facebook" and I give my answer by talking about the technology fb using, which she didn't understand. I guess she expect me to be a fan of social network but my topic is always technology. Finally she ask if I am talking with other company. I give her a name of a company. But she never heard that. Hey, that's a middle size company in bay area just ipo 2yrs ago. She just can't understand what I am talking in the phone call. Not even one. Got rejection few days later.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

1 person found this helpful

No Offer

Neutral Experience

Average Interview

Software Engineer Interview

Software Engineer

I applied through a recruiter and the process took 3+ weeks - interviewed at Facebook in March 2014.

Interview Details – 1 phone interview : merge sorted list, maximum path in tree
3 round onsite : Regular expression, strStr, anagram, split sentence into words, talk about projects
1 extra phone interview after onsite : talk about projects, count and say
All the questions can be found in leetcode

Interview Question – Regular expression and strStr. I was not able to give KMP algorithm to strStr   View Answers (5)

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

No Offer

Neutral Experience

Software Engineer Interview

Software Engineer

I applied online and the process took 2 months - interviewed at Facebook.

Interview Details – I applied online and was contacted by the recruiter and send me an invitation to solve the programming puzzle online. After it, I received the mail from recruiter and set up a technical phone interview.

Interview Question – 2SUM problem and how to optimize it.   View Answers (3)

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response
RSS Feed Embed
Interviews for Top Jobs at Facebook

Worked for Facebook? Contribute to the Community!

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.

Glassdoor is your free inside look at Facebook Software Engineer interview questions and advice. All 326 interview reviews posted anonymously by Facebook employees and interview candidates.