Fragen in Vorstellungsgesprächen bei Facebook für Production Engineer | Glassdoor.de

Fragen in Vorstellungsgesprächen bei Facebook für Production Engineer

Vorstellungsgespräche bei Facebook

115 Bewertungen von Vorstellungsgesprächen

Erfahrung

Erfahrung
81%
6%
13%

Einladung zum Vorstellungsgespräch

Einladung zum Vorstellungsgespräch
53%
27%
9%
6
4
1

Schwierigkeit

3,4
Durchschnittl.

Schwierigkeit

Schwer
Durchschnittl.
Leicht

Hilfreich (3)  

Production Engineer-Vorstellungsgespräch

Anonymer Mitarbeiter in Menlo Park, CA (Vereinigte Staaten von Amerika)
Angebot angenommen
Positive Erfahrung
Durchschnittl. Gespräch

Bewerbung

Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 3 Monate. Vorstellungsgespräch absolviert im Oktober 2013 bei Facebook (Menlo Park, CA (Vereinigte Staaten von Amerika)).

Vorstellungsgespräch

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

Fragen im Vorstellungsgespräch

  • Explain everything that happens over the network when a client tries to access a website.   2 Antworten

Andere Bewertungen von Vorstellungsgesprächen für Facebook

  1. Hilfreich (18)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter in Menlo Park, CA (Vereinigte Staaten von Amerika)
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im März 2014 bei Facebook (Menlo Park, CA (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

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

    Fragen im Vorstellungsgespräch

    • 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 Antworten

    Verhandlungsdetails

    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.


  2. Hilfreich (19)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im Juli 2014 bei Facebook.

    Vorstellungsgespräch

    Was contacted by a recruiter. The recruiter initially asked me a handful of one-word-answer system administration questions. Subsequently had three phone screening interviews spaced over a couple of weeks before being invited to fly out to SF for an on-site interview.

    The screening interviews were straightforward 45-minute phone calls using an shared text editor site to code.

    The on-site interview was a full day consisting of 4 seperate interviews on different topics. The engineers I interacted with were all very friendly, and the questions asked were at times difficult but very fair: everything I was asked seemed very relevant to the potential job and assessing my general programming skill (no "stupid hard for the sake of being stupid hard" sort of questions).

    The campus is fantastic, and I got to spend a lot of time with the recruiter, who was incredibly knowledgeable and helpful, asking questions and wondering around checking the place out. The trip would have been worth the time even if I didn't get an offer.

    About a week after my on-site interview, I got a call from the recruiter saying they wanted to offer me the position. The next day we discussed the compensation details, and a few days later I accepted.

    Verhandlungsdetails

    You will be asked what compensation you are expecting annually

  3. Hilfreich (47)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert bei Facebook.

    Vorstellungsgespräch

    A recruiter contacted me. After confirming that I would like to interview for the position, I was asked basic questions around networking, Linux system administration, and programming. A graduating Computer Science student should expect to pass this with little difficulty.

    Next was a phone interview for programming. I was asked to take input text and identify the unique words in the text and how many times each word occurred. Edge cases were important as was the performance. Interviewer asked for an analysis of the run-time and memory usage. Any second-year CS student should have no problem completing this in far less than the allocated time.

    Next was a phone interview for systems administration. I was given the bare minimum information possible about a system and told to describe how I discover running services and potential issues. As I progressed, the interviewer gave me information reasonable based on my descriptions and identified when I had correctly discovered a problem or possible problem. In investigating problems, it was important to be specific about why the problem was occurring and how to address the issue. When addressing problems, the performance, scalability, and maintainability of the solution was very important. Be prepared to identify how a file system is mounted or if it's local, and be prepared to encounter a single central share mounted by many servers with active read/write activity from them all. This will be difficult for anyone without good real-world Linux systems administration experience.

    Next I was flown out to HQ for a series of on-site interviews. A manager spoke to me to gauge my understanding of Facebook and the Production Engineering position (rely on the job description and don't be afraid to ask your recruiter lots of questions!) and to get to know me.

    There's another interview about coding and another one for systems administration. Both are along the same lines as the phone interview, but more in-depth and more difficult.

    There's a systems design interview, where you'll be given a target and asked to design a scalable and performant system to accomplish the goal. You may be asked to analyze the storage requirements (core and/or persistent) and network requirements of your system.

    The last interview type is a networking interview, which is very in-depth and requires extensive knowledge of TCP/IP, UDP/IP, DNS, etc. Essentially, start at a command prompt and think of what happens when you type "telnet www.facebook.com 80" - be prepared to talk about almost every single network-related thing that happens at all seven OSI layers. Know your packet layouts!

    Throughout the entire process, my recruiter was always on top of keeping me informed and always answered questions very quickly (I rarely waited even most of a day for a reply). I rarely needed to ask anything about what to expect because she kept me so well informed. Don't worry too much about thinking at Facebook's scale, they understand that very few people have worked on anything even approaching their size and scale. Everyone you deal with will work hard to make things go as smoothly as it can.

    Fragen im Vorstellungsgespräch

    • The entire networking interview was very difficult, I was not expecting the amount of in-depth knowledge expected for that interview.   Frage beantworten

  4.  

    Production Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte mehr als 6 Wochen. Vorstellungsgespräch absolviert im Juli 2014 bei Facebook.

    Vorstellungsgespräch

    Contacted on linkedin based on Google experience. Fairly long interview process, with a phone screen, then two technical phone interviews, then a full day interview in Menlo Park. Took several weeks for them to get back, too, but they came up with a very competitive offer, and came back fairly quickly when I countered.

    Fragen im Vorstellungsgespräch

    • Some real curveballs about how specific protocols worked. HTTP, SMTP, etc.   Frage beantworten

    Verhandlungsdetails

    I negotiated, got a good 5-10% based on my previous experience and bluffing about how much I was searching.


  5. Hilfreich (1)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Menlo Park, CA (Vereinigte Staaten von Amerika)
    Kein Angebot
    Negative Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte 4 Wochen. Vorstellungsgespräch absolviert im Juni 2012 bei Facebook (Menlo Park, CA (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    I was contacted by a recruiter over linkedin. After doing a technical screen with the recruiter, there were two phone interviews with engineers. The first was a fairly simple programming test, and later a more in depth systems test.

    Fragen im Vorstellungsgespräch

    • The systems interview was more open ended than I expected   3 Antworten

  6. Hilfreich (1)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter in Menlo Park, CA (Vereinigte Staaten von Amerika)
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte mehr als 4 Wochen. Vorstellungsgespräch absolviert im Oktober 2011 bei Facebook (Menlo Park, CA (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    The process was tough but fair. The phone screens were a bit harrowing because I didn't know what to expect. However, during the on site, the employees did everything they could to make me as comfortable as possible and gave me every opportunity to answer the questions correctly.


  7. Hilfreich (7)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Menlo Park, CA (Vereinigte Staaten von Amerika)
    Kein Angebot
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich auf anderem Weg beworben. Der Vorgang dauerte mehr als 6 Wochen. Vorstellungsgespräch absolviert im November 2012 bei Facebook (Menlo Park, CA (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    The process was pretty spread-out but extremely well coordinated and communicated. Expectations were perfectly managed. Since I was remote, they had me go through a set of 3 phone screenings, each very technical. Passing each phone screen lead to the next, with passing the final round leading to an in-person interview and trip to Menlo Park, CA.

    The pictures of the campus there don't do it justice. It's a really surprising environment.

    I really can't say enough how awesome their recruiting staff is. They always replied promptly and helpfully, and were awesome to work around my schedule every step along the way.

    In the final analysis I just wasn't a good fit for the position - and I even agree with them. After seeing and hearing so much of the cool stuff they do behind the scenes and are working on doing, I am not (yet) qualified for that job. In the end, the thing I felt most qualified in was my big stumble. What I learned was to be on their level, it wasn't enough to have just done what I've done for a long time - that they justifiably want an expert in multiple disciplines.

    Their benefits are just absurdly great. Everything they offer is top-notch including their facility in Menlo Park, where the old Sun research campus used to be.

    In the end, it was a great experience. I got to go and interview with one of the biggest Internet companies in the world and meet some brilliant people and see just how great their environment is. I realized that in the right environment, I can go head to head with some of the best - and got a quick trip out there to boot!

    Fragen im Vorstellungsgespräch

    • Why wouldn't you want a root DNS server to answer queries for you, instead of delegating you to an authoritative server?   5 Antworten
    • For a given set of software checkins, write a program that will determine which part along the branch where the fault lies.   4 Antworten
  8. Hilfreich (9)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Mitarbeiter
    Angebot angenommen
    Positive Erfahrung
    Schweres Gespräch

    Bewerbung

    Ich habe mich online beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im Mai 2015 bei Facebook.

    Vorstellungsgespräch

    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.

    Fragen im Vorstellungsgespräch

    • 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 Antwort

  9. Hilfreich (70)  

    Production Engineer-Vorstellungsgespräch

    Anonymer Bewerber im Vorstellungsgespräch in Menlo Park, CA (Vereinigte Staaten von Amerika)
    Angebot abgelehnt
    Positive Erfahrung
    Durchschnittl. Gespräch

    Bewerbung

    Ich habe mich über einen Personalvermittler beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im März 2015 bei Facebook (Menlo Park, CA (Vereinigte Staaten von Amerika)).

    Vorstellungsgespräch

    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.

    Fragen im Vorstellungsgespräch

    • 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 Antwort

Finden Sie heraus, was Mitarbeiter von Facebook sagen

StarStarStarStarStar   Akt. Client Partner in London, England (Vereinigtes Königreich)

Pros: “I've been with Facebook for nearly 2 years and I have to say that it is the best place to work! - Smart and genuinely good people - Positively challenging work - Potential for...”“I've been with Facebook for nearly 2 years and I have to say that it is the best place to work! - Smart and genuinely good people - Positively challenging work - Potential for growth & career progression - Inspiring leadership” – Vollständige Bewertung

Verpassen Sie nicht Ihren Traumjob
Laden Sie Ihren Lebenslauf hoch, um sich schnell und einfach für Jobs zu bewerben. Bewerben leicht gemacht!