Facebook Production Engineer Interview Questions in San Francisco, CA | Glassdoor

Facebook Production Engineer Interview Questions in San Francisco, CA

Updated Jul 23, 2017
21 Interview Reviews

Experience

Experience
76%
4%
19%

Getting an Interview

Getting an Interview
80%
9%
4%
4

Difficulty

3.9
Average

Difficulty

Hard
Average
Easy

21 Candidate Interview ReviewsBack to all Interviews

Filter

Sort: PopularDateDifficulty

Filter

Sort: PopularDateDifficulty

Helpful (2)  

Production Engineering Interview

Anonymous Employee in Menlo Park, CA
Accepted Offer
Positive Experience
Difficult Interview

Application

I applied through a recruiter. I interviewed at Facebook (Menlo Park, CA) in June 2017.

Interview

Initial phone conversation with the recruiter, phone interview with a leader, technical phone interview, a day of on-site interviews that covered various technical and non-technical topics, including a code interview (coding on the whiteboard). The recruiter did an excellent job of making sure I was well-prepared as to what to expect. Don't feel like there were any attempts to "trick" or "surprise" me, it was all about making sure I was set up to be comfortable - felt like they want you to be successful.

Interview Questions

  • With very little detailed information, how would you approach tackling a performance problem in a web application (i.e., step through your thought process of what steps you would take, information you would seek, etc.).   Answer Question

Other Interview Reviews for Facebook

  1. Helpful (1)  

    Production Engineer Interview

    Anonymous Employee in Menlo Park, CA
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 2 weeks. I interviewed at Facebook (Menlo Park, CA) in February 2017.

    Interview

    Recruiter contacted me via linkedin. I went through 3 phone interviews (one easy 10 minutes screening by the recruiter and two 45 minutes harder and more in depth) and 5 in person interviews (all 45 minutes each).

    Interview Questions

    • Questions usually start very general but quickly go very in depth. Know TCP/IP, BigO, kernel internals, etc. Try to think at big scale.   1 Answer

    Negotiation

    Easier to negotiate if you already have another offer from another competing company and if you did well in the interviews.


  2. Helpful (31)  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Declined Offer
    Negative Experience
    Average Interview

    Application

    I applied online. The process took 4+ weeks. I interviewed at Facebook (Menlo Park, CA) in April 2016.

    Interview

    I was shocked by how unprofessional the process was. My recruiter from the beginning was super flaky. They would not call me when they said they would and then call at completely random times catching me off guard. I appreciated that they tried to help me prepare for interviews, though, which they don't really "have" to do. Then, after the on site, they basically told me I had to commit to coming to Facebook before I would receive an offer. It basically seemed like the recruiter didn't want to go through the effort of filling out paper work if I wasn't going to come. This was pretty shocking after having spent a month jumping through all the hoops and spending basically a whole day on their campus for interviews. I was already leaning slightly toward another company and that really clinched my decision. Then when I told the recruiter I wasn't going to come they got really aggressive contacting me repeatedly over call/text/email trying to get me to change my mind. Still without giving me anything in writing! I was so shocked that a company with the reputation Facebook had would operate that way.

    Facebook Response

    Jun 6, 2016 – Your Friends at Facebook

    Thank you for recently interviewing with our team. We're sorry to hear that you did not receive the best possible interview experience with our team. We'll take your feedback and work to improve the... More

  3. 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.


  4.  

    Production Engineer Interview

    Anonymous Employee in Menlo Park, CA
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 6 weeks. I interviewed at Facebook (Menlo Park, CA) in February 2016.

    Interview

    It's a intense and length process with multiple steps, but all the interviewers were fair and helpful. Despite of the hard level of the questions, I left all interviews with a good feeling that I could show my skills and I could understand clearly my mistakes and week spots. The recruiter has also very responsive.

    Interview Questions


  5. Helpful (3)  

    Production Engineer Interview

    Anonymous Interview Candidate in San Francisco, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 2+ weeks. I interviewed at Facebook (San Francisco, CA) in January 2016.

    Interview

    I passed the first 2 then failed at system level interview, the interviewer is great and the env is very nice. They really set up one good question for people to understand easily at first then hold your back finally. I finally failed that but love to work with them in future.

    Interview Questions

    • when you saw many system interrupts, what could be the possible reason in linux   1 Answer

  6. Helpful (10)  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    No Offer
    Negative Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 2 weeks. I interviewed at Facebook (Menlo Park, CA) in September 2015.

    Interview

    Phone screen, then code-over the phone, followed by in person with 6-8 people in 4 interview sessions. The initial phonescreen covers typical techbusiness shibboleths, the coding interview was REALLY fun, and I was excited to do the inperson, but that when everything fell apart.

    For some reason, facebook has decided that at the inperson interview, you have to write your code on a whiteboard, and it can't have any bugs in it. They even tell you to practice coding on a whiteboard before the interview, because apparently, whiteboard coding is a big part of working at facebook. I'll just go ahead and say it, no one writes software longhand, it's not how it's done, and to expect people to write nontrivial things on a whiteboard in 2015 is beyond ridiculous, especially considering that part of facebook's own process is a code interview where you write a program using a computer!

    If you're interviewing a lumberjack, do you have him draw a chainsaw on a whiteboard?

    The most important thing to keep in mind if you want to get a job at facebook is that they reinvent everything. Every question they ask will be about how you would reinvent something. I was unprepared for the amount of guessing I was required to do (I'm terrible at guessing.) Remember when you're answering them that they have basically UNLIMITED RESOURCES and are willing to reinvent any wheel. I'm not saying what they're doing is bad, I'm saying it's completely different than anywhere else I've worked in many years in the business, and I think I'd be working there now if I had approached the questions with that in mind, instead of my instinct, which is to leverage the work of others as much as possible to my advantage, eg I look at what's out there on the internet, and then do whatever I need to. If there's something already there, I use that, if not, I'll write my own, or somewhere inbetween -- like everyone not working at facebook does. Don't blow it like I did, remember it's not a normal job, it's facebook, where there are always hackers hacking, and they have more money than Canada to hire more hackers to hack on whatever they've hacked together.

    The recruiters are nice, the management seemed friendly and capable, lunch wasn't very good but I was probably just stressed out. If you've ever been to the office when it was Sun Microsystems, be ready for a shock, also the cafeteria was like the mall at xmas.

    I'd love to work there, and on a different day I may have gotten the gig, but at the end of the day, you've still got to make it through a long gauntlet of bored looking engineers, looking to exclude you.

    They have unique problems there and it would be a super cool job, so I hope this helps someone else. As for me, I'll never go through it again.

    Interview Questions

    • How would you design a cache API?   1 Answer
    • reimplement 'tail' in a scripting language   1 Answer

  7. Helpful (53)  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    Declined Offer
    Positive Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 3 weeks. I interviewed at Facebook (Menlo Park, CA) in March 2015.

    Interview

    Quick tech quiz with the recruiter over the phone. Then we scheduled two phone screens, one on coding, one on systems, both of them 1 hour long. Once you pass the phone screens you'll have to schedule an on-site visit which consists of 5 interviews, 45 minutes each: systems, networking, cultural, system architecture, coding. If you're not from CA, they'll fly you over to SFO, preferably on a Monday.

    Interview Questions

    • The quiz was pretty simple, you'll be asked basic questions about Linux.

      Battleship game: write a function that finds a ship and return its coordinates.
      Write a script that connects to 100 hosts, looks for a particular process and sends an email with a report.
      What is a filesystem, how does it work? File permissions, properties, file types. A write operation failed with an error, how do you figure out what happened? What's a signal and how is it handled by the kernel? What's a zombie process?

      Talk about an iostat output (what does user vs system cpu load mean, what does iowait% mean, cache vs buffers, why do we need caching, how much cache is needed, how can disk performance be improved, where is the bottleneck)
      How do TCP, UDP work? Describe what happens when a client opens a web page. How does DNS work? How does HTTP work? How does a router work?
      Various questions about your current experience, talk about a conflict situation and how you handled it.
      How would you design a system that manipulates content sent from a client (e.g. clean bad words in a comment post)?
      Write a function to sort a list of integers that looks like this [5,2,0,3,0,1,6,0] -> [1,2,3,5,6,0,0,0] in the most efficient way.   Answer Question
  8. Helpful (5)  

    Production Engineer Interview

    Anonymous Interview Candidate in Menlo Park, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 2+ weeks. I interviewed at Facebook (Menlo Park, CA) in April 2015.

    Interview

    They recruited me at a conference. I had a recruiter phone screen followed by two engineering phone screens. One was focused on coding and the other on systems. This was followed by an all-day interview at the Facebook Campus. The all-day interview was 5 sessions with different engineers, 45 minutes each. Each interview focused on a different area like Architecture, Coding, Networking, and Systems.

    Interview Questions


  9. Helpful (8)  

    Production Engineer Interview

    Anonymous Employee in Menlo Park, CA
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 2 weeks. I interviewed at Facebook (Menlo Park, CA) in March 2015.

    Interview

    I was contacted by a recruiter through LinkedIn. He asked several simple questions and then set up two phone screens, one for "systems" and one for "software engineering." A few days later I was invited to Menlo Park, CA for a day of interviews. There were 5 45-minute sessions: software engineering, networking, manager, and design. The interviewers varied in quality, but we generally pretty good.

    Interview Questions

    • Under NDA to not reveal interview questions however they are very predictable questions which could be easily understood based on the names of the interviews. There were no odd trick questions like "deploy SSH to 10,000 servers on the moon."   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.