Questions entretien Production Engineer chez Facebook | Glassdoor.fr

Questions entretien Production Engineer chez Facebook

Entretiens chez Facebook

127 Avis sur les entretiens

Expérience

Expérience
81%
7%
12%

Obtenir un entretien

Obtenir un entretien
51%
30%
9%
6
3
1

Difficulté

3,4
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (9)  

Entretien de Production Engineer

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

Candidature

J'ai postulé via une recommandation d'un employé. J'ai passé un entretien à Facebook en novembre 2017.

Entretien

I applied Software Engineer position but received email from HR regarding interviews of this position. I had a quiz at first about commands of Linux. In the first round, I received two coding problems. Not hard.
The second round is system interview. It's more like discussion. A lot of question about linux troubleshooting.
Both rounds had no behavior questions even no self- introduction. Just directly solve the problems.

Questions d'entretien d'embauche

Autres avis d'entretien pour Facebook

  1.  

    Entretien de Product Engineer

    Candidat à l'entretien anonyme - Mountain View, 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 (Mountain View, CA (États-Unis)) en novembre 2017.

    Entretien

    Interview process is well-organized, can't complain. Onsite interview was super difficult, I failed 5 segments out of 5 and got a maximum cool off period outlined in the manual (5 years).

    Questions d'entretien d'embauche


  2.  

    Entretien de Production Engineer

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

    Entretien

    Got reached out to by a recruiter who set up a phone call to discuss the position. After that an algorithm round was established, and then a systems round. The algorithm round was quite standard and not too hard, but the topics that were recommended to study for the systems round were much too broad as in actuality, the interviewer focused on asking very small specifics that were impossible to study for given the time span.

    Other than that, the recruiter was very friendly and the process was very fast, but the process was disappointing at the end.

    Questions d'entretien d'embauche

  3. Utile (8)  

    Entretien de Production Engineer

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

    Candidature

    J'ai postulé via un recruteur. Le processus a pris +4 semaines. J'ai passé un entretien à Facebook en octobre 2017.

    Entretien

    Recruiter contacted me on LinkedIn and was extremely professional and helpful. 4 round interview process, recruiter, coding, systems (programming), and on site. Dropped out in phase 3.

    They describe phase 3 as a "systems interview", but it's extremely low level. Swap management, server flags, process management. A recommendation for a book called "The Linux Programming Interface."

    Questions d'entretien d'embauche


  4.  

    Entretien de Production Engineer

    Employé anonyme - Seattle, WA (É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 (Seattle, WA (États-Unis)) en octobre 2017.

    Entretien

    Two PS, then on site with five people loop.
    Coding, design, Linux, Network and soft skills.
    Each area are both check your knowledge breath and depth.
    Recruiter real helpful on preparing, they provide detailed guidance and help me prepare the interview.
    On-site experience is great, nice people and hard questions though.

    Questions d'entretien d'embauche

    • Linux kernel, Network deep dive, distributed system design   1 réponse

  5. 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.   2 Réponses
    • Add each number in an array until the sum equals the rest of the array   5 Réponses

  6. Utile (4)  

    Entretien de Product Engineer

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

    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 (Menlo Park, CA (États-Unis)) en septembre 2017.

    Entretien

    I was contacted by the recruiter.
    The first round is a BASIC HR screening test. (20 Questions) Anyone with systems knowledge can solve this easily.

    The next one was a coding round(45 mins). You should clearly know about space complexity and time complexity. Know Big O in and out. Don't expect to clear if you don't know it.

    The next round is systems.

    Questions d'entretien d'embauche

    • 1) Basic Algorithms. Do leetcode. Know different and better approaches of the same code. (o(1) solutions- dynamic programming)
      2) Do log parsing, Know how to validate IP, dates, credit card numbers. Regex is your bestfriend.   Répondre à cette question

  7. Utile (2)  

    Entretien de Production Engineer

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

    Candidature

    J'ai postulé via un recruteur. J'ai passé un entretien à Facebook (Seattle, WA (États-Unis)) en septembre 2017.

    Entretien

    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.

    Questions d'entretien d'embauche

    • What happens during the boot process from the moment you turn on the machine until you get a login prompt?   2 Réponses
  8.  

    Entretien de Production Engineer

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

    Candidature

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

    Entretien

    I was contacted by email by a first level recruiter. After some back-and-forth (hem and haw on my part) I agreed to go through with the process. After passing a basic technical screen, I was scheduled for the initial phone interview to cover coding skills. After passing that, I was scheduled for a second phone interview to cover systems administration skills. After passing both remote interviews, I was moved to a second recruiter, with whom I worked with the entire rest of the interview process.

    First, they had a travel specialist contact me for preferred flight locations and times, and then they booked the flights and hotels for me, and scheduled my on-site interviews. They covered all travel expenses, including flights, uber/lyft rides, hotel, and meals.

    I interviewed at the Menlo Park primary campus, building 16. The on-site process consisted of five 1 on 1 interviews, each covering a specific topic and lasting about 45-60 minutes. The interview topics were Systems, Coding, Networking, Design/Architecture, and Behavior. The on-site recruiter would stop by in-between each interview to check up, and also took me to one of the on-site restaurants for lunch.

    Questions d'entretien d'embauche

    • Initial tech screen asked very basic questions, like what the "uname" command does, or what type of packet terminates a TCP connection.   Répondre à cette question

  9. Utile (7)  

    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


Voir ce que des salariés chez Facebook disent

StarStarStarStarStar   Research Scientist actuel à Menlo Park, CA (États-Unis)

Avantages: “- Very interesting research projects that really have an impact in real life - Company's culture - Benefits - Amazing people”“- Very interesting research projects that really have an impact in real life - Company's culture - Benefits - Amazing people” – Avis complet

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