Facebook Production Engineer Interview Questions in San Francisco, CA

Updated Jun 25, 2015
13 Interview Reviews

Interview Experience

Interview Experience

84%
7%
7%

Getting an Interview

Getting an Interview

84%
7%
7%

Interview Difficulty

3.8
Average

Interview Difficulty

Hard

Average

Easy

13 Candidate Interview Reviews Back to all Interviews

Sort: Popular Date Difficulty

 

Production Engineer Interview

Anonymous Employee 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

Other Interview Reviews for Facebook

  1. Helpful (5)  

    Production Engineer Interview

    Anonymous Interview Candidate 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."   Answer Question
  2. Helpful (5)  

    Production Engineer Interview

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

    Production Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Neutral Experience
    Difficult Interview

    Application

    I applied through a recruiter. The process took 1+ week. I interviewed at Facebook (Menlo Park, CA) in February 2015.

    Interview

    A recruiter reached out to discuss a position that may be a good fit with my skillset. It started with a phone interview followed up with a code review interview. The process took about 10 days. The interview questions were not difficult, some with several answers. Unix Process, networking, tcp/ip stack, and system administrative commands. The process was casual, I did notice before the interviews even started. Their coordination was awkward, after receiving numerous misspelled emails and wrong phone numbers. I was a little leery of working for them. Nonetheless, I continued with the 45-min code review interview and answered the question. Overall, the interviews were comparable to other companies. Also, they were efficient with their responses and answering questions.

    Interview Questions

    • Given a sentence convert the sentence to the modified pig-latin language: Words beginning with a vowel, remove the vowel letter and append the letter to the end. All words append the letters 'ni' to the end. All words incrementally append the letter 'j'. i.e. 'j','jj','jjj', etc...   2 Answers
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5. Helpful (7)  

    Production Engineer Interview

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

    Application

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

    Interview

    Was initially contacted via LinkedIn by an internal Facebook recruiter that dealt specifically with this role. I was impressed with the recruiter's technical knowledge, always a good sign, and agreed to go through the screening and start the interview process. The process is 5 steps: * Call with recruiter about position * Phone screening with a few trivia questions regarding systems administration. * Co-operative coding phone interview * Systems phone interview * On-Site interview The call with the recruiter was mostly about the position description and duties, and assessing whether both sides think it's a good fit. The phone screening, also done with the recruiter, is just a few questions that anyone who has administered Linux for an organization would be able to answer off the top of their head. The coding interview was done using a collaborative editing tool, so both parties could see what was being typed. The coding questions were not your typical abstract data manipulation questions, but rather questions that required systems knowledge, and in my case were most easily answered with shell scripts. I didn't actually do the systems phone interview, as they considered my programming interview strong enough to simply skip this step. I'm informed this is not uncommon. The on-site interview loop included five 45-minute segments: Programming, Systems, Networking, Solution Architecture, and meeting with the Manager (not in that order). Additionally, lunch with the initial recruiter and a brief chat afterwards with a different recruiter that dealt with the financial and logistics portions of the interview and negotiations. One thing that struck me during the entire process is that *everyone* I spoke to, and I mean *everyone* because I asked them all, absolutely loved working there. Every time I asked someone how they liked working at Facebook, their face lit up and they started listing off reasons they loved working there, and everyone had the same reason: They liked everyone around them, felt trusted and respected, and trusted and respected the people around them. This was unanimously the first reason, usually followed by "and the work is really interesting".

    Interview Questions

    • What options do you have, nefarious or otherwise, to stop people on a wireless network you are also on (but have no admin rights to) from hogging bandwidth by streaming videos?   2 Answers

    Negotiation

    My negotiations were all pre-offer. There is a compensation department that comes up with an offer based on your years of experience, strength during the interview process, and current pay. They will almost certainly exceed your current pay if you disclose it, though I should probably point out they didn't verify mine. In my case they offered base pay approximately 10% higher than my prior base pay, and I presume this is fairly standard.

  6. Helpful (1)  

    Production Engineer Interview

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

    Application

    I applied through a recruiter. The process took 3+ months. I interviewed at Facebook (Menlo Park, CA) in October 2013.

    Interview

    I was contacted by a recruiter on Linkedin. I first had a really quick phone call + technical screening with the recruiter (port numbers, shell commands...). After that was a 2 questions coding interview over the phone which I believed didn't go so well even though the questions were easy (Think first CS college course level), but I passed anyway. Next I had a another technical phone call on systems (kernel, shell commands, basic troubleshooting...) I was then invited to fly over to California for an on-site interview which I was really excited about. I stayed in a pretty nice hotel and everything was paid for by FB. On-site, I had 5+ interviews with engineer, managers and recruiters which were similar to the phone interviews, just a little deeper/harder. I also had the opportunity to tour the FB campus which looked great... nice office space, lots of free perks, great people... I had an offer about a week later and accepted. You don't ofter get to work for one of the biggest/greatest/most traffic website/platform...

    Interview Questions

    • Explain everything that happens over the network when a client tries to access a website.   2 Answers
  7. Helpful (6)  

    Production Engineer Interview

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

    Application

    I applied through a recruiter. The process took 4+ weeks. I interviewed at Facebook (Menlo Park, CA) in August 2013.

    Interview

    HR contacted me from Linkedin. There was 3 phone interviews for screening, code test and system administration test. First interview, recruiter went through some questions, such as port number, routing, Linux commands, and some basic language wise questions. Second interview was a coding test. Engineer had me to write two script for csv data processing, and system monitoring. Third one was for system administration. The questions were pretty open. The interviewer had me to dig into the internals of operating system, such as performance tuning, memory model, paging, swap, process forking, system call, interrupt, and etc. I passed 3 interviews, and flew to Facebook campus for a whole day onsite interview (with NDA signed). During the interview process, I felt people there are super nice, and gave me chances to answer questions correctly. My suggestions - Use your strongest language (scripting language will help a lot) - Familiar with operating system internals and system analysis tools - Familiar with networks and infrastructures (TCP/IP, DNS, HTTP, and etc) - Think about scalability

    Interview Questions

    • How can you find whether a process is I/O bound or CPU bound?   1 Answer
  8.  

    Production Engineer Interview

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

    Application

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

    Interview

    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

  9. Helpful (20)  

    Production Engineer Interview

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

    Application

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

    Interview

    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
  10. Helpful (2)  

    Production Engineer Interview

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

    Application

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

    Interview

    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

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.

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.