Facebook Production Engineer Interview Questions | Glassdoor

Facebook Production Engineer Interview Questions

Updated Sep 21, 2017
47 Interview Reviews

Experience

Experience
70%
10%
19%

Getting an Interview

Getting an Interview
63%
17%
10%
4
4

Difficulty

3.3
Average

Difficulty

Hard
Average
Easy

47 Candidate Interview ReviewsBack to all Interviews

Filter

Sort: PopularDateDifficulty

Filter

Sort: PopularDateDifficulty

 

Production Engineer Interview

Anonymous Interview Candidate in Seattle, WA
No Offer
Positive Experience
Difficult Interview

Application

I applied through a recruiter. I interviewed at Facebook (Seattle, WA) in September 2017.

Interview

Two phone screens (one on software dev, the other on systems topics) using coderpad.io, then an all day on-site made up 5 interviews (software dev again, systems again, design, networking, and a general fit interview). Each interview is about 45 minutes long, and generally they wrap up a few minutes early to give you time to ask any questions you might have.

A common theme in the interviews is that they will tweak the requirements a little bit to see how you handle change or make some suggestions to see what you do with feedback. The problems themselves aren't especially difficult as they have to be solved (usually twice) in under 45 mins, and they are also used to gauge how well you work with others and if you can quickly find other solutions.

Finally, I have to give a big shout out to the recruiting team at FB. The process was extremely well organized, at not point did I feel like I was imposing on anyone I talked to, and I feel like everyone wanted to give me a fair shot. The recruiters did an excellent job of letting me know what to expect and following up with feedback after each step of the process. This was the least stressful and most enjoyable interview I've been to for a large company.

Interview Questions

  • What happens during the boot process from the moment you turn on the machine until you get a login prompt?   1 Answer

Other Interview Reviews for Facebook

  1. Helpful (2)  

    Production Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Negative Experience

    Application

    I applied through a recruiter. I interviewed at Facebook.

    Interview

    The first phone screen was with a recruiter to discuss the role and ask a few basic technical questions. The next step was a 45 minute coding focused phone interview. You are given two simple, but not practical coding challenges to answer live with the interviewer. If you have studied only interview coding type questions from the many online sites that charge a fee for answers, then you may do well, otherwise, don't count on it. If you don't succeed, they end the process there without asking any systems or networking related questions. So, if you want to pass their coding interview, study and do practice problems for months.

    Interview Questions

    • Import a CSV / JSON file. If condition is met, print two attributes for that condition.   Answer Question
    • Add each number in an array until the sum equals the rest of the array   2 Answers

  2. Helpful (1)  

    Production Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Neutral Experience
    Average Interview

    Application

    I applied online. I interviewed at Facebook in July 2017.

    Interview

    The interview process was fairly simple. HR is pretty quick and responsive to emails. In the beginning, I got a call from HR, which included some technical screening (linux, networking etc.) , following which I was scheduled for a coding interview.
    Their coding interview is not crazy, it is focussed on performance and efficiency (please be thorough with complexity analysis). HR provides you with proper material for preparation.

    During my coding interview, it appeared like my interviewer was a bit impatient (when I tried talking aloud my approach while programming) and at times I also had difficulty following him as well (I tried level best in keeping up and clarifying). Overall I thought I had done well with the coding interview because one of the questions involved around "battleship" which I clarified I am just familiar with, but I think I was still able to get something working as a solution. I did hear back from HR, as they decided not to proceed further (as they had better candidates). I thought I did stutter and feel nervous at one point, which may have made the interviewer a bit impatient. So my advice, be confident, clarify and also pray that you find a patient interviewer.

    Interview Questions

    • Linux internals, networking, basics (HR Screening), Standard coding interview questions   Answer Question
  3. Helpful (4)  

    Production Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 5 days. I interviewed at Facebook.

    Interview

    Initial HR Screen with Basic Linux INTERNALS Questions (10 - 15 questions) - most of the questions already available on glassdoor.

    IF you clear the HR round, you will be given the material to prepare for the subsequent rounds.... a wide variety of topics covering (way too many) everything that is going to be asked during the interview.

    But the truth is................................... that it is too late to prepare ( if u have 3-5 days to go for the next round.)..............all of it ....................... if you already don't have a solid foundation of OS concepts and Algorithms.

    If you are 4-6 months out from graduating ..............( YES !!! THEY ARE HIRING NEW GRADS FOR THIS ROLE..!!! ).............and there is a possibility of getting an interview(referral) for this position ., read the above paragraph again.

    Systems round

    They will ask you Linux questions .........till you feel.... you are out of your depth e. - an in-depth KNOWLEDGE OF LINUX INTERNALs is minimum criteria to clear this round.

    Pick up a Linux Kernel book.... (own it.)........ and have an Overview of Performance related commands( Truth --- >> know each parameter( if it changes(increase/decrease) and how it affects performance( This is where i failed) ---- )

    Last minute preparation
     Study the Entire Linux kernel and Performance related commands for 10-15 days before the interview.

    Try to understand how web farms(servers) are maintained.... Expect some very vague problem statements( troubleshooting question). Be ready for a set of large scale (Web scale) troubleshooting related questions. .... they just want to examine your approach, (there are no right or wrong answers).................. ( For Vague problem statements---- >> ask questions or better state your assumptions but keep the flow. Its key.

    Programming Round:

    If you are not new to coding... this should be straight forward.

    if you are new......... 3-4 weeks on hacker rank and algorithms basics( arrays, stacks, sorting) and you might get lucky.

    Interview Questions

    • Linux Performance commands..... ( Well the engineer spent ...15 mins on one command.. )

      Know Kernel to the CPU interrupt level...   1 Answer

  4.  

    Production Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Positive Experience
    Easy Interview

    Application

    I applied through a recruiter. The process took 3 days. I interviewed at Facebook in April 2017.

    Interview

    I was contacted by a recruiter over Linkedin. I went through a basic a HR phone screen with a few easy Linux/networking questions. I then had a programming interview where I was given two prompts to answer in 45 minutes. You could use any language and they were fairly straightforward. The first interviewer was very pleasant and quick. The second didn't say much and then described the job to me.

    Interview Questions

    • Name three states a process can be in.   2 Answers

  5. Helpful (4)  

    Production Engineering Interview

    Anonymous Interview Candidate in Seattle, WA
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied through a recruiter. The process took 4 days. I interviewed at Facebook (Seattle, WA) in March 2017.

    Interview

    FB contacted me to ask me to chat with them about their PE role. I contacted them a few years ago, and said that the interview process was too aimed at jr engineers for me. They assured me they had changed the initial tech questions, but they were about the same. These questions would be cake for someone who just finished their BA degree, but silly for someone who's 10-15 years into their career and mostly focused on automation. There were no questions about coding, automation, writing sql queries or config management, they were all on linux basics or networking. They turned me down on the call for the position, and suggested I spend less time automating and more time focusing on stuff far below my skill level. Complete waste of my time, and mildly insulting. They really need a second set of much harder questions for more sr engineers.

    Interview Questions

    • Where is the dns file located?   2 Answers
    • What signal do you send a service to end it?   2 Answers
    • What is the type of record that resolves urls to ip records?   2 Answers
    • Under ps, what are three states that a service can be in?   1 Answer
    • Out of the 5-6 states you can find under ps, which two takes up system memory?   1 Answer
    • If 0 is STDIN and 1 is STDOUT, what's 2?   1 Answer

  6.  

    Production Engineer Interview

    Anonymous Interview Candidate in New York, NY
    No Offer
    Negative Experience
    Average Interview

    Application

    I applied through other source. The process took 2 days. I interviewed at Facebook (New York, NY) in February 2017.

    Interview

    Their HR dept contacted me. First step was doing a phone interview with their HR dept, nothing intense. Second step was to do a code test. Spent 45 min while Facebook look at what you're writing. Did a coding challenge but there no way for you to test/complie your code. They assumed you know the correct syntax, etc.

    Interview Questions

    • In IPv6 what is the A record equivalent?   3 Answers

  7. Helpful (5)  

    Production Engineer Interview

    Anonymous Interview Candidate in Los Angeles, CA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied online. The process took 4+ weeks. I interviewed at Facebook (Los Angeles, CA) in July 2016.

    Interview

    I made it to the 2nd of 4 interviews. Both of my interviewers were extremely polite and professional. The first interview was a phone screening from a recruiter, which also included around 10 Linux sysadmin/networking questions (What command would you use to do _____?). The second interview was a coding test. I was asked to write code to accomplish two different tasks. The interviewer was very helpful in giving me suggestions when I would get stuck.

    Interview Questions

    • What is the default signal that is generated when sending a kill command to a process in Linux?   3 Answers
  8. Helpful (16)  

    Production Engineer Interview

    Anonymous Interview Candidate in San Francisco, CA
    No Offer
    Negative Experience
    Difficult Interview

    Application

    I applied through an employee referral. The process took 4 weeks. I interviewed at Facebook (San Francisco, CA) in March 2016.

    Interview

    I was referred by a former colleague, and was immediately contacted by the recruiter, who was extremely nice. He asked 20 basic questions involving coding, networking and systems. Then there were 3 phone interviews, each technical, consisting of coding, systems, and networking.

    The coding interview was straight forward and it was clear that this was a skill that is necessary, but not as important as the others.

    The systems interview was where I personally had the biggest issue. Not because of the material, but because of the content, and interviewer. The interviewer was the stereotypical Silicon Valley Nerd bully who even warned me before we started that he comes of "a little d*uchey." The moment he said that I knew that the interview was not going to go well. He would not clarify ANY of his questions, he would assume that my sub questions revealed lack of understanding or knowledge. The questions were ridiculous, down to how certain flag options affect the output of certain commands. I understand that a production engineer must know these details, but it is extremely stupid and unrealistic to think that these details cannot be looked up.

    Long story short, I feel like they didnt even test how much I actually knew about how Linux actually works, just how to look for certain arcane items that vary from distro to distro.

    Following this disaster, I was informed by the recruiter that they were "not able to offer me the position", as well as "not able to share feedback." Very bitter taste in someones mouth that had been studying and preparing for weeks, sometimes at the expense of my current job, just to be told "no" with zero accountability as to why.

    Oh wait, but there is more. After a long weekend of sadness and self reflection, I was called again by the recruiter, to say that "they actually want to continue the process to the networking interview, due to the fact that there are many PE teams that deal a lot more with networking than with systems." Naturally, I was ecstatic, seeing as how I am currently in the networking field, and would be able to crush any interview regarding networking.

    The networking interview came along, which I aced completely. I was contacted the next day, told that they were "not able to offer me the position" and "not able to share feedback"... again. Very weird and ridiculous considering the fact that they called me specifically to test my networking knowledge, only to ask super basic networking questions, have me get them right, then tell me no, and waste yet another week of my time and energy.

    The Recruiter at facebook was fantastic, the overall experience was not. All of the interviewers were fantastic, except for the systems one. All it takes is one egomaniac that thinks only the worthy should have the chance to work alongside them.

     Big attractive companies get away with lack of accountability in the interview process, and literally do not care at all about providing legitimate reasons as to why they think you cant do a job that you know you can do.

    Interview Questions

    • 20 questions

      coding - counting things in a logfile, basic algorithms

      systems - literally know every single detail of what could arise in a system and how to fix it exactly, hope and pray they ask you something that you have memorized

      networking - super basic, whats your favorite protocol. questions about DNS   Answer Question

    Facebook Response

    Jun 6, 2016 – Your Friends at Facebook

    Thanks for sharing your feedback. We're so sorry to hear about your interview experience. Every candidate moment matters to us and we'll leverage this feedback to improve our experience.


  9. Helpful (3)  

    Production Engineer Interview

    Anonymous Interview Candidate in Albuquerque, NM
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through college or university. The process took 2 weeks. I interviewed at Facebook (Albuquerque, NM) in March 2016.

    Interview

    4 total interviews, Phone, coding, systems, onsite. I made it through the first phone interview and the coding interview, the systems stuff was really what got me, they asked a lot of hard questions and were very serious about making sure their hires knew linux inside and out.

    Interview Questions

    • Common port names for different networking services.   1 Answer

Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.