Questions entretien Production Engineer chez Facebook | Glassdoor.fr

Questions entretien Production Engineer chez Facebook

Entretiens chez Facebook

121 Avis sur les entretiens

Expérience

Expérience
81%
7%
12%

Obtenir un entretien

Obtenir un entretien
51%
29%
10%
6
4

Difficulté

3,4
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (7)  

Entretien de Production Engineer

Employé anonyme - Menlo Park, CA (États-Unis)
Offre d'embauche acceptée
Expérience positive
Entretien dificile

Candidature

J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en août 2018.

Entretien

I was contacted via LinkedIn and asked to apply in 2014. I went through the full process then but didnt get an offer. Facebook contacted me again this year and we went through the process again.

As is well documented, you will have two phone interviews. One will be coding, the other will be systems. If you get thumbs up for both, Facebook will fly you to Menlo Park CA for on-site interviews.

I flew from Sydney AU direct to SFO - Facebook where happy to do direct flights rather than via LAX (who likes layovers?). In 2014 Facebook put me up in a hotel for 3 nights but this year mercifully it was 4 nights - it was much nicer to have a relaxing evening after the on-site interviews rather than rushing straight to the airport. Facebook was also happy for me to pick one of their Hotel options (which are all nice enough), but which put me closer to things I wanted to explore. I flew out on Saturday morning Sydney time to land Saturday morning SF time, which gave me two nights to partially adjust to local time before interviews on the Monday. These finished mid afternoon, which left plenty of time to explore a few more things this second time before flying out on the tuesday (where as in 2014 I had to pretty much head to the airport to check in on the Monday).

Questions for the phone interviews are mentioned in many places here and on peoples blogs, so I wont repeat them.

On-site you will have 5 interviews, all kept to strictly 45 mins. Your recruiter or the interviewing person will escort you at all times (fair enough) and the recruiter will take you to any of the restaurants on-site for 30 mins lunch break. The recruiter and reception will offer for you to stock your pockets or bags with snacks and drinks - this isnt a trick question so grab a few Coke's and anything that wont melt!

Each on-site question is 45 mins, of which perhaps 5 mins at the start will be pleasantries and a few minutes at the end is set aside for questions. Think about what you might ask ahead of time. A chose to ask:
- What is something you didnt do before Facebook, but do now, that you would always do in future jobs? (generally they responded with something thats automated)
- What do you like about Facebook that keeps you here? (one response was that things with a billion-to-one chance happen 3-4 times a day at Facebook)

Questions d'entretien d'embauche

  • One interview is with a manager. They will ask probing questions about your work history and personality.   1 réponse
  • Another interview will be coding - on a whiteboard.   1 réponse
  • Another interview will be networks- again on a whiteboard.   1 réponse
  • Another interview will be systems. This is again verbal and whiteboard. The interviewer might provide a printout of some debugging.   1 réponse
  • Your final interview will be Design. This is verbal and whiteboard. The other of these interviews may vary.   1 réponse

Autres avis d'entretien pour Facebook

  1. Utile (2)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience positive

    Entretien

    Very welcoming and helpful through every step of the process. The recruiters would always send informative emails about where in the interview process I was and what the next steps would be. All were very professional and prompt. Would interview again!

    Questions d'entretien d'embauche


  2. Utile (70)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme - Menlo Park, CA (États-Unis)
    Offres d'embauche déclinées
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en mars 2015.

    Entretien

    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.

    Questions d'entretien d'embauche

    • 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.   1 réponse
  3. Utile (3)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via un recruteur. Le processus a pris une semaine. J'ai passé un entretien à Facebook en mars 2015.

    Entretien

    First interview was with a HR, which i thought would be just about soft skills but i was asked 10-20 technical question mostly networking and system administration. Second round was a coding exercise and was asked to code using any language of my choice. Interviewer is looking for how you apply the logic. He did not ran my code but he made some modifications on the code and asked me what the output will be after the changes.

    Questions d'entretien d'embauche


  4. Utile (5)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme - Menlo Park, CA (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris +2 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en avril 2015.

    Entretien

    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.

    Questions d'entretien d'embauche


  5. Utile (8)  

    Entretien de Production Engineer

    Employé anonyme - Menlo Park, CA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en mars 2015.

    Entretien

    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.

    Questions d'entretien d'embauche

    • 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 réponse

  6. Utile (30)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme
    Offres d'embauche déclinées
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 4 semaines. J'ai passé un entretien à Facebook en février 2015.

    Entretien

    An recruiter contacted me by email and ask me to do a phone interview. She asked me whether I am familiar with production engineer's work and 10+ initial screen questions. They are all about basic Linux and networking knowledge, like port number and tcp protocol, Linux commands. Most of them are quite easy but they do really have some tricky questions. Afterward, I was told that I had passed and would have one coding interview and one system interview before making the final decision.

    The coding interview started about 1 weeks later. I was asked to code using stypi and there are two questions in 45 minutes. One is translate English to "Goat Latin" language with a set of predefined rules. It was not hard but I still spent 20-30 minutes on that, partly because I cared too much about the detail. The second question is more a shell-script coding, although I did not realize it immediately. I was asked to obfuscate local parts of email addresses found in all HTML files under a folder (also subfolders). Due to the time limit, I did not write a clean and complete code for it. But I discussed with the interviewers for the possible solutions (shell script + python regex operation).

    Then the recruiter told me I passes the first round and we moved on to system interview, which began 5 days later. Since it is totally new to me, I read lots of posts in glassdoor and other interviewing forums and there are very useful. The interview questions requires solid knowledge about Linux, operating system, performance monitoring. They both starts with a relatively simple questions but ends with lots of followup questions. Try your best to be open-minded and always talk with the interviewer. They want not only an correct answer, but also how you get this solution.

    Later that day I heard from the recruiter that the feedback seemed also great. After one week, they give me the offer. The salary is greater than I ever expected.

    Pros:
       The recruiter is super nice and willing to answer any of your question in a timely manner.
       The interviewing schedule is very flexible. You can propose any date as you like.
       The interviewers are quite smart and patient. They are always on your side and trying to guide you through difficulties.

    Questions d'entretien d'embauche

    • Explain in every single step about what will happen after you type " ls * " in your terminal.   Répondre à cette question
    • Suppose there is a server with high CPU load but there is no process with high CPU time. What could be the reason for that? How do you debug this problem? Does your solution always work, and if not, what's the reason for that?   2 Réponses

    Raison du refus

    I have to decline it because I got another offer from Palantir later as a software engineer intern. But FB is really great and I will definitely take it without the other one.


  7. Utile (9)  

    Entretien de Production Engineer

    Employé anonyme
    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien à Facebook en mai 2015.

    Entretien

    Got a phone screening, followed by two phone interviews. The entire process went quicker than I thought. The interviews were difficult but fair. I definitely prepared a lot beforehand (brushing up on knowledge of Linux, systems, networking, etc).

    I got an offer without doing an onsite, which I don't think is typical for Facebook.

    Questions d'entretien d'embauche

    • Phone screening was general system stuff: DNS, TCP, CLI tools, etc.
      First phone interview was coding based.
      Phone interview was very linux-y, system calls, signals (term, kill, etc), load vs cpu util. Also stuff about general cs.   1 réponse
  8. Utile (12)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme - Menlo Park, CA (États-Unis)
    Aucune offre d'embauche
    Expérience négative
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en septembre 2015.

    Entretien

    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.

    Questions d'entretien d'embauche

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

  9. Utile (18)  

    Entretien de Production Engineer

    Employé anonyme - Menlo Park, CA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via un recruteur. Le processus a pris +4 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en mars 2014.

    Entretien

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

    Questions d'entretien d'embauche

    • 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?   5 Réponses

    Négociation

    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.


Voir ce que des salariés chez Facebook disent

analyst

5 personnes ont trouvé cela utile

StarStarStarStarStar     Employé anonyme Actuel

Avantages: “dynamic, good, awesome, excellent, wonderful”“dynamic, good, awesome, excellent, wonderful” – Avis complet

Ne manquez aucun emploi que aimez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. C'est simple à configurer.