Facebook

www.facebook.com

Facebook Production Engineer Interview Questions

Updated Dec 29, 2014
Updated Dec 29, 2014
9 Interview Reviews

Interview Experience

Interview Experience

66%
11%
22%

Getting an Interview

Getting an Interview

77%
11%
11%

Interview Difficulty

3.7
Average

Interview Difficulty

Hard

Average

Easy

9 Candidate Interview Reviews Back to all interviews

Sort: Popular Date Difficulty

 

Production Engineer Interview

Anonymous Interview Candidate
Anonymous Interview Candidate
Application Details

I applied through a recruiter. The process took 1+ weekinterviewed at Facebook.

Interview Details

Over the phone coding screen, I was asked two fairly easy questions and I answered both of the them well and I understood the edge cases and answered all the questions the interview had about my solutions. The interview lasted about 50 minutes.

Sadly I was rejected based on feedback from the interviewer. The feedback stated the second question was fine, but the first question had an issue. The solution I provided wasn't what the interviewer wanted, and the solution that he wanted was different from what the question had asked.

No Offer
Neutral Experience
Easy Interview

Other Interview Reviews for Facebook

  1.  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Anonymous Interview Candidate in Menlo Park, CA
    Application Details

    I applied through a recruiter. The process took 2+ weeksinterviewed at Facebook in August 2013.

    Interview Details

    Recruiter contacted me through LinkedIn and we setup a phone interview. He went through some basic System Administration questions and at the end asked me for availability for a coding interview. Coding interview was about algorithm and solving three problems.

    Interview Questions
    No Offer
    Positive Experience
    Difficult Interview
  2. 15 people found this helpful  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Anonymous Interview Candidate in Menlo Park, CA
    Application Details

    I applied through a recruiter. The process took 6 weeksinterviewed at Facebook in June 2013.

    Interview Details

    Everyone I spoke with was reasonably personable and competent. The process went quite smoothly and was relatively painless.

    5 phone contacts:
    * basic screening (might you be a good fit for the position)
    * basic programming
    * (single) system administration
    * basic description of what will come next+handoff to another recruiter
    * in-depth description with new recruiter of what to expect during the on-site interviews

    5 onsite interviews+lunch:
    You first meet your recruiter, with a brief overview of the day.

    * Production Engineer Manager
      - Getting to know you, talk about what a Production Engineer does.

    * Coding
      - Algorithmically simple (write ____ system utility), but you need to be able to intelligently discuss complexity and tradeoffs of optimizations (CPU/RAM). What is the theoretical best performance?
      - You don't need to know exact details of APIs, but you need to know what calls are available, and have a deep understanding of how things work. You should know exactly what is happening, including the complexity of any system calls you make.
      - Accuracy and and efficiency in your code are crucial.

    * Systems
      - FB has problems on a scale you have not yet realized. They hit problems you haven't ever seen.
      - When you see ____ crazy problem, what do you do? How do you figure out what the fundamental problem is? Once you know the problem, how can you mitigate it?
      - Explain in detail what happens when you run ____ command.
      - Think about this sort of information: what problems are you going to run into while doing IPC (pipes, shared memory structures etc.)? How exactly does the OS transfer information across a pipe? What are the limits or bottlenecks?

    * LUNCH
      - Good food, relax and get to know your recruiter a little better. Get a better feel for the environment. Ask questions off the record, so to speak.

    * Design/Architecture
      - FB understands you probably don't have experience at their scale. Just do your best to extend what you know to their scale.
      - How do you do ____ across a large number of systems? How do you do it without interrupting production? How long will it take?
      - When doing estimation, be sure to explain your thought processes.

    * Networking
      - Probably the least important of the 4 technical interviews.
      - Be familiar with packet routing (How does the source computer know where to route packets? How do packets move across a network?).
      - Know how to configure and use at least one client/server network service (and talk about it intelligently). How does it work internally? What are the features of XXX protocol?

    Last, you talk to your recruiter about what you think about the recruiting process, the position, how well it fits you, considerations that you may need to think about before making a final decision.

    Interview Questions
    • The individual questions are not difficult.

      I'd expect any network engineer worth his salt to have no difficulty with the networking questions. Likewise, the coding shouldn't be a problem for a software developer, and systems isn't going to be hard for a systems administrator.

      The trouble is the /breadth/ of questions. What are the limits of your knowledge? Can you make a reasonable guess as to what is going on based on what you do know?
       
      Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  3. 2 people found this helpful  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Anonymous Interview Candidate in Menlo Park, CA
    Application Details

    I applied through a recruiter. The process took 3 weeksinterviewed at Facebook in July 2013.

    Interview Details

    Three 45-minute phone interviews. A positive review from each qualified me for the next.

    First interview was a basic-technical one with their recruiter: port numbers, subnet math, Linux commands.

    Second was a Collabedit programming interview. An engineer had me build a performance monitoring script, adding more features and improving efficiency as we went.

    Third was a systems interview. Heavy operating systems theory was involved. This engineer's confessed style was improvisational, probing areas of knowledge my previous answers had laid claim to. It helped to know enough systems stuff, and to be interested enough in it, to make the conversation span the whole interview time.

    I passed the third phone interview, so Facebook flew me to their campus for a day of on-site interviews. I had to sign an NDA covering my experiences on that day. What I can say is that I thought it went at least as well as my phone interviews, yet I got a rejection email a week later.

    Interview Questions
    No Offer
    Positive Experience
    Difficult Interview
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5. 3 people found this helpful  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Anonymous Interview Candidate in Menlo Park, CA
    Application Details

    I applied through other source. The process took 6+ weeksinterviewed at Facebook in November 2012.

    Interview Details

    The process was pretty spread-out but extremely well coordinated and communicated. Expectations were perfectly managed. Since I was remote, they had me go through a set of 3 phone screenings, each very technical. Passing each phone screen lead to the next, with passing the final round leading to an in-person interview and trip to Menlo Park, CA.

    The pictures of the campus there don't do it justice. It's a really surprising environment.

    I really can't say enough how awesome their recruiting staff is. They always replied promptly and helpfully, and were awesome to work around my schedule every step along the way.

    In the final analysis I just wasn't a good fit for the position - and I even agree with them. After seeing and hearing so much of the cool stuff they do behind the scenes and are working on doing, I am not (yet) qualified for that job. In the end, the thing I felt most qualified in was my big stumble. What I learned was to be on their level, it wasn't enough to have just done what I've done for a long time - that they justifiably want an expert in multiple disciplines.

    Their benefits are just absurdly great. Everything they offer is top-notch including their facility in Menlo Park, where the old Sun research campus used to be.

    In the end, it was a great experience. I got to go and interview with one of the biggest Internet companies in the world and meet some brilliant people and see just how great their environment is. I realized that in the right environment, I can go head to head with some of the best - and got a quick trip out there to boot!

    Interview Questions
    • Why wouldn't you want a root DNS server to answer queries for you, instead of delegating you to an authoritative server?   View Answers (3)
    • For a given set of software checkins, write a program that will determine which part along the branch where the fault lies.   View Answers (3)
    No Offer
    Positive Experience
    Difficult Interview
  6.  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Anonymous Interview Candidate in Menlo Park, CA
    Application Details

    I applied through a recruiter. The process took 4 weeksinterviewed at Facebook in June 2012.

    Interview Details

    I was contacted by a recruiter over linkedin. After doing a technical screen with the recruiter, there were two phone interviews with engineers. The first was a fairly simple programming test, and later a more in depth systems test.

    Interview Questions
    • The systems interview was more open ended than I expected   View Answer
    No Offer
    Negative Experience
    Difficult Interview
  7. 3 people found this helpful  

    Production Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied online. The process took 2+ monthsinterviewed at Facebook.

    Interview Details

    I applied online for a production engineering position. A recruiter did a screening interview with me to assess where my strengths lay, and to determine which role would be the best fit. They recommended a production engineering role. We scheduled a phone interview which covered several programming/scripting questions. After getting positive feedback, we scheduled another phone interview which covered linux system administration and troubleshooting. Although I received positive feedback from that interview as well, the existing production engineering roles were filled. My recruiter asked if I would be interested in pursuing another role within the organization, specifically a software engineering role. We scheduled an interview with that team. I had a bad day, and couldn't focus during the interview, totally blowing it. I didn't receive an offer, although if given another chance I believe I would be offered one.

    Interview Questions
    • Given a list of integers, output all subsets of size three, which sum to zero.   View Answers (2)
    • Given a list of integers which are sorted, but rotated ([4, 5, 6, 1, 2, 3]), search for a given integer in the list.   Answer Question
    No Offer
    Negative Experience
    Average Interview
  8. 2 people found this helpful  

    Production Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter. The process took 3 weeksinterviewed at Facebook in August 2013.

    Interview Details

    It starts with the screening call. Here I was asked a little about what I currently do, and then some general questions: ports, subnet math, linux commands, TCP. I got most of the right, so I was qualified to begin the proper interviews. I found out there were going to be two 45 minute phone interviews and if I passed both, I will be brought on site in their Menlo Park location for some more interviews.

    The first is a programming interview, in the language of your choice, using collabedit. You'll be asked to write a function and a small program that do different things. They will not actually run the code, but rather speak with you about what you've written down. The tasks were pretty basic, so I assume they also follow your general attitude towards the problems and how you structure everything and present what you are doing.

    The interviewer is not allowed to give direct feedback but you'll probably know if he's got a good feeling or not. After about a week I got an email telling me that I've passed and I scheduled my second phone interview.

     The second phone interview is a linux systems administration interview, also using (when needed) collabedit. This is a pretty thorough interview and the questions go as deep as the linux kernel. You'll have to know how things like how the bash interpreter works, process forking and killing, memory management, process tracing and debugging.

    My systems administration knowledge is not that deep so this interview did not go as well.

    Interview Questions
    • A question that involved using "strace". Since I have very little hands-on experience with it, I was not able to understand the problem/question.   Answer Question
    No Offer
    Positive Experience
    Difficult Interview
  9.  

    Production Engineer Interview

    Anonymous Interview Candidate
    Anonymous Interview Candidate
    Application Details

    I applied through a recruiter. The process took 2 weeksinterviewed at Facebook in February 2013.

    Interview Details

    Very polite and friendly people. Process took several weeks. Recruiter contacted me via LinkedIn. First screening interview with some technical questions. Next two were with technical people: scripting skills and infrastructure maintenance. Not so difficult questions but a little tricky.

    Interview Questions
    • What is the biggest challenge that I have on current or past projects.   View Answer
    No Offer
    Positive Experience
    Average Interview

Work at Facebook? Share Your Experiences

Facebook

 
Click to Rate
or

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.