Questions entretien Production Engineer chez Facebook | Glassdoor.fr

Questions entretien Production Engineer chez Facebook

Entretiens chez Facebook

116 Avis sur les entretiens

Expérience

Expérience
81%
7%
12%

Obtenir un entretien

Obtenir un entretien
52%
27%
10%
7
4

Difficulté

3,4
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (22)  

Entretien de Production Engineer

Candidat à l'entretien anonyme - Los Angeles, CA (États-Unis)
Aucune offre d'embauche
Expérience positive
Entretien dificile

Candidature

J'ai postulé en ligne. Le processus a pris +4 semaines. J'ai passé un entretien à Facebook (Los Angeles, CA (États-Unis)) en juillet 2016.

Entretien

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.

Questions d'entretien d'embauche

  • What is the default signal that is generated when sending a kill command to a process in Linux?   5 Réponses

Autres avis d'entretien pour Facebook

  1. Utile (14)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme
    Offres d'embauche déclinées
    Expérience positive
    Entretien facile

    Candidature

    J'ai postulé via un recruteur. J'ai passé un entretien à Facebook.

    Entretien

    Recruiter was very friendly and accommodating. They seemed like they really cared about getting the interview scheduled. First interview was a phone call about 15-20 mins, just a get to know you and see if you're a good fit for the company. After that they schedule the other technical interviews which is about 45 mins and consists of a coding session.

    Questions d'entretien d'embauche


  2.  

    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 6 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en février 2016.

    Entretien

    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.

    Questions d'entretien d'embauche

  3. Utile (2)  

    Entretien de Production Engineer

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

    Candidature

    J'ai postulé via une autre source. Le processus a pris 2 jours. J'ai passé un entretien à Facebook (New York, NY (États-Unis)) en février 2017.

    Entretien

    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.

    Questions d'entretien d'embauche

    • In IPv6 what is the A record equivalent?   4 Réponses

  4. Utile (3)  

    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 février 2017.

    Entretien

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

    Questions d'entretien d'embauche

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

    Négociation

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


  5. Utile (25)  

    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 5 jours. J'ai passé un entretien à Facebook.

    Entretien

    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.

    Questions d'entretien d'embauche

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

      Know Kernel to the CPU interrupt level...   1 réponse

  6. Utile (2)  

    Entretien de Production Engineer

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

    Candidature

    J'ai postulé via un recruteur. Le processus a pris 3 jours. J'ai passé un entretien à Facebook en avril 2017.

    Entretien

    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.

    Questions d'entretien d'embauche


  7. Utile (3)  

    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 avril 2012.

    Entretien

    Recruiters were very eager and helpful, the process was still being worked out especially on the international and immigration front, but the actual interview was well ran. The questions were somewhat hard, especially since they assumed a different approach to e.g. software development.

    Questions d'entretien d'embauche

    • Algorithm to find 3 integers adding up to 0   4 Réponses
  8. Utile (12)  

    Entretien de Production Engineer

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

    Candidature

    J'ai postulé via un recruteur. J'ai passé un entretien à Facebook.

    Entretien

    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.

    Questions d'entretien d'embauche

    • Import a CSV / JSON file. If condition is met, print two attributes for that condition.   1 réponse
    • Add each number in an array until the sum equals the rest of the array   4 Réponses

  9. Utile (6)  

    Entretien de Production Engineer

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    Expérience neutre
    Difficulté moyenne

    Candidature

    J'ai postulé en ligne. J'ai passé un entretien à Facebook en juillet 2017.

    Entretien

    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.

    Questions d'entretien d'embauche


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