Questions d'entretiens pour le poste de Data Scientist chez Facebook | Glassdoor.fr

Questions d'entretiens pour le poste de Data Scientist chez Facebook

Entretiens chez Facebook

218 Avis sur les entretiens

Expérience

Expérience
54%
22%
24%

Obtenir un entretien

Obtenir un entretien
37%
28%
20%
9
2
2
2

Difficulté

3,0
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (26)  

Entretien de Data Scientist

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

Candidature

J'ai postulé via une recommandation d'un employé. Le processus a pris 4 semaines. J'ai passé un entretien à Facebook.

Entretien

One call with the recruiter and one phone interview with a Data Scientist and moved on to on-site interview with 5 rounds of interviews. In the phone interview, it's mostly brainstorming metrics and an SQL query question. The 5 rounds of on-site interviews includes 2 SQL, 2 A/B testing and 1 Math interviews.

Questions d'entretien d'embauche

  • If there's a new feature that attracts more pop stars to use it, how do you evaluate whether this feature is successful or not?   2 Réponses

Autres avis d'entretien pour Facebook

  1. Utile (5)  

    Entretien de Data Scientist

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

    Candidature

    J'ai postulé via un recruteur. Le processus a pris une semaine. J'ai passé un entretien à Facebook (San Francisco, CA (États-Unis)) en décembre 2017.

    Entretien

    I had two phone interviews with the recruiter. She was very nice, informative and helped me set up for success. I had to pull out after that due to other offer.

    Questions d'entretien d'embauche

    • Common statistical and python related questions.
      1) How do you proof that males are on average taller than females by knowing just gender or height.
      2) What is a monkey patch
      3) How do you get the count of each letter in a sentence   8 Réponses

  2. Utile (7)  

    Entretien de Data Scientist

    Employé anonyme - Palo Alto, CA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

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

    Entretien

    Very similar to what others have mentioned.

    -first call with recruiter, mainly going over your resume and having them explain the process. Afterwards he sent over prep material for the phone interviews and onsite interview. The material is really comprehensive and probably somewhat overkill, but if you review it all you will be prepared. The recruiter really really wants you to feel prepared as well, so use them as a resource! That was what stood out the most to me in the process, more than anywhere else they want you to feel ready.

    -phone interview with shared screen coding with a data scientist. Basic sql, coding, and stats questions.

    -another phone interview, very similar to the first.

    -on site interview with a mix of open ended data science problems, coding questions, sql questions, behavioral questions

    -follow up phone interview with only one subject that they felt they didn't ask enough about at the onsite

    Questions d'entretien d'embauche

    • Tell me about a time when you received constructive criticism and how you handled it.   2 Réponses
  3. Utile (1)  

    Entretien de Data Scientist

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    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 novembre 2017.

    Entretien

    The process starts with a 15 minute call with the recruiter that covers basic questions about your background and level of interest. It's nearly impossible to mess up this step. My recruiter was incredibly kind and courteous. The following interview is an ~1 hour video conference with a coding (SQL, Python, or R) question and analysis question focused on a proposed change to one of their products. This interview is conducted by a data scientist. Mine arrived late, wasn't very nice, and was kind of condescending. It seemed like they thought this was a waste of their time. I failed this interview step most likely because I don't have the requisite experience in defining KPIs. In all honesty, this position seems more like a "data analyst" position that they relabelled "scientist" in order to attract more applicants. In the analytics team, it seems like they are only performing descriptive and inferential statistics--not building predictive models. The next step would have been an on-site interview had I made it.

    Questions d'entretien d'embauche

    • Given an event-level table of interactions between pairs of users (note that there aren't duplicates in one day for one pair of users), for each possible number of "people interacted with" find the count for that group in a given day (i.e. 10 people interacted with only one person, 20 with 2, etc.).   3 Réponses

  4. Utile (2)  

    Entretien de Data Scientist

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

    Candidature

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

    Entretien

    The interview started with live coding exercises. Some technical questions were asked about statistical concepts. The next part was product development questions. Finally, it ended with questions about experimental design.

    Questions d'entretien d'embauche

    • How would you explain a confidence interval to a non-technical audience?   4 Réponses

  5. Utile (8)  

    Entretien de Data Scientist

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

    Candidature

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

    Entretien

    Recruiter reached out on Linkedin, initial 15 min phone chat to understand the role, 45 min vchat first round interview with a data scientist on the team, then five 30 min interviews onsite. I communicated with quite a few recruiters as they seem to handle different steps in the interview process, they also sent very exhaustive emails for both rounds of interview for preparation. There's another 30 min call right before the onsite with a data scientist on the team as a chance for you to ask what to expect. Interview schedule was pretty flexible; waited for less than a week to hear back after the onsite.

    The onsite interview itself wasn't that difficult! I'm giving it an "Average", but I'd say it's really on the "Easy" side if you studied the emails the recruiters sent you and the Glassdoor interview questions.

    Specifically, the interactions with my recruiter were very positive. He was very informative, helpful, timely, and professional.

    Questions d'entretien d'embauche

    • Some SQL questions with fake tables. It was kind of tricky to wrap my head around it as white boarding was quite different from writing code on your computer screen.   Répondre à cette question

  6. Utile (3)  

    Entretien de Data Scientist

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

    Candidature

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

    Entretien

    First a phone screen with the recruiter who explains the position and the interview process. Then a video interview with a data scientist which consists of a technical coding exercise and some product questions about what could be driving activity.

    Questions d'entretien d'embauche

    • Very disappointing experience from interviewing with FB. Absolute worst and least professional interviewer I have ever had.

      * FB does video interviews for the first round (along with coding in an online environment). This is fairly surprising since it can't serve much legitimate purpose. I'm sure their legal team is thrilled at the additional burden they face in discrimination lawsuits since the interviewer clearly can has information about the appearance of the candidate and they can't plead ignorance. Of course perhaps they are looking for unkempt candidates or trying to demonstrate the culture of transparency at Facebook, but read on!

      * Interview was 5 minutes late to video interview and had disheveled appearance during whole interview. He was constantly fidgeting and playing with the neighboring chairs and objects on the table and even put his feet on the other chairs and table! An interview for a position is a two-way street, so the interviewer also needs to be on "best behavior".

      * In addition to the behavior above which was unprofessional, he interrupted very frequently. This goes beyond steering the conversation. This is really tricky since one person is judging you, nobody wants to say "Please allow me to finish explaining my answer and reasoning" and hope somebody like this won't hold it against you. He possibly spent just as much time talking as I did during the interview answering his questions. The interruptions came both in the coding sections when I explained my thought process before implementing it and during the product questions when explaining possible scenarios. Of course clarifying comments are helpful to make sure the candidate is on the right track, but interrupting somebody just because they want to use a subquery (and you wouldn't) and is going to solve the problem slightly differently than you would is indicative of your lack of emotional intelligence and perhaps also the programming language you're working with.

      * He obviously wasn't paying attention during the process and didn't take it seriously. He was constantly working on his computer. Of course he could have been taking notes, but after I answered a question twice and explained my thoughts twice, he stated what the correct answer was--which was in fact what I said twice, but he apparently hadn't been listening then and was occupied with the chair/table objects/computer.

      * The interviewer seemed to only accept very specific answers that aligned with his thoughts and preferred answers. This mentality is obviously horrible for open-ended questions like "what could be causing this" or "what data would you look at". You may be looking at this data all the time and know which fields are useful for this task, but when you condescendingly react like the interviewee is a complete idiot for thinking of looking at the timestamp patterns for app usage you don't demonstrate your intelligence but rather your closed mindedness and unfamiliarity and inexperience with working with any type of data except the dataset at your company.

      * It is probably clear from reading the interview questions from other candidates and what the recruiters provide you as prep, but this really isn't a data scientist position: it's more or a data analyst or SQL monkey position. For this reason I was borderline on interviewing here anyway but thought, "hey, it is Facebook". I'm sure everybody in the industry knows that this is what FB data scientists do, so while the name cache might carry advantages when looking for a job later, it could actually harm you if you want to be thought of as a data scientist and move on to legit data scientist/software engineer positions.

      * The information you receive that you can solve the questions in SQL or Python or R is possibly incorrect. My interviewer wanted it in SQL or Python. Not a big deal since I know all three, but when when this is one of the first things you hear (along with all the rest of the insanity of this interview) it is enough to throw you off your game. SQL seems to be the preferred solution, so I'd recommend forgetting about the others if your SQL is decent.

      * The one positive of all of this experience is that the recruiters were professional--both in scheduling the interviews and in explaining the role and answering any questions you may have.

      Overall, I agree with some of the other comments here that you might get unluckly with a very egotistical interviewer. Officially I haven't heard back from FB yet, but I would be shocked to advance and really have no interest to work with someone like this. Bad apples exist in all companies, but a bro culture like this really does dampen any interest of anything FB. Yikes.   Répondre à cette question
    • Do you have any questions?   1 réponse
    • You have a table with appID, eventID, and timestamp. eventID is either 'click' or 'impression'. Calculate the click through rate. Now do it in for each app.   2 Réponses
    • Likes/user and minutes spent on a platform are increasing but total number of users is decreasing. What could be causing this?   1 réponse

  7. Utile (5)  

    Entretien de Data Scientist

    Candidat à l'entretien anonyme
    Aucune offre d'embauche
    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.

    Entretien

    It was a 45-min technical interview. The interviewee was navigating me to give him the answer he was looking for. I answered the questions on a white board. I was asked statistics questions but with a Facebook product story behind it. I was asked to write a script that reads a file and then stores project names and people who are assigned to it.

    Questions d'entretien d'embauche

  8. Utile (2)  

    Entretien de Data Scientist

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

    Candidature

    J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en novembre 2017.

    Entretien

    Got contacted by a recruiter, who initially told me to consider Data Science Manager position. The first interview was with the Recruiter, who was going over my background, and, specifically leadership skills. Next day I've got an email that due to the headcount, they can not offer me this position this year, but can consider for a Data Scientist position. The interview process was supposed to be two virtual over the web (Analytical and Technical (SQL or Python or R - my choice)), followed by an on-site interview in Menlo Park (Statistical with a choice of R or Python as a tool)

    Questions d'entretien d'embauche


  9.  

    Entretien de Data Scientist

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

    Candidature

    J'ai postulé via une autre source. Le processus a pris une semaine. J'ai passé un entretien à Facebook (Menlo Park, CA (États-Unis)) en novembre 2017.

    Entretien

    I came in through the Insight Data Science program. The phone screen was 45 min with some easy probability, SQL and a quick product-dive that we ran out of time on. Onsite was 4 half-hour technical interviews back to back. Everyone was engaged and thoughtful and I thought that the questions were fair. Had one hiccup misinterpreting one of the probability questions (due to ambiguous wording I thought that I was supposed to answer a much more complicated question than what was posed). Probably wasted at 10 min before we uncovered the miscommunication.

    Questions d'entretien d'embauche

    • Some medium difficulty SQL and probability questions. Some problem-solving/modeling deep-dives   1 réponse

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