Questions entretien Front End Engineer chez Facebook | Glassdoor.fr

Questions entretien Front End Engineer chez Facebook

Entretiens chez Facebook

38 Avis sur les entretiens

Expérience

Expérience
76%
11%
13%

Obtenir un entretien

Obtenir un entretien
48%
23%
19%
10

Difficulté

3,1
Moyenne

Difficulté

Difficile
Moyenne
Facile

Utile (2)  

Entretien de Front End Engineer

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

Candidature

J'ai passé un entretien à Facebook en mai 2019.

Entretien

A friend of mine referred me. Hr called me by phone and asked me some basic conceptual questions about Javascript. The next day I received an email saying that I was rejected.

Questions d'entretien d'embauche

Autres avis d'entretien pour Facebook

  1. Utile (27)  

    Entretien de Front End Engineer

    Employé anonyme
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

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

    Entretien

    I applied for a Front End Engineer Intern position through a referral. A recruiter got back to me in about 3 weeks with a 30-minute phone screening. I had two additional 45-minute video+CoderPad sessions before receiving an offer.

    Questions d'entretien d'embauche

    • Explain the concept of ES6 Promises to a 5-year-old.   1 réponse
    • What are the advantages of using ES6 maps over objects? What about using ES6 sets over arrays?   2 Réponses

  2. Utile (21)  

    Entretien de Front End 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 août 2017.

    Entretien

    Skype interview

    Questions d'entretien d'embauche

    • Given input:

      // could be potentially more than 3 keys in the object above
      items = [
      {color: 'red', type: 'tv', age: 18},
      {color: 'silver', type: 'phone', age: 20}
      ...
      ]

      excludes = [
      {k: 'color', v: 'silver'},
      {k: 'type', v: 'tv'},
      ....
      ]
      function excludeItems(items, excludes) {
         excludes.forEach(pair => {
            items = items.filter(item => item[pair.k] === item[pair.v]);
         });
         return items;
      }

      1. Describe what this function is doing...
      2. What is wrong with that function ?
      3. How would you optimize it ?   17 Réponses
  3. Utile (30)  

    Entretien de Front End 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 octobre 2016.

    Entretien

    I applied through a recruiter who contacted me in September. She was nice and we booked a Phone/Screen coding interview.

    They are using CoderPad for these. This first interview consisted of 3 questions, they all seemed pretty easy and then the interviewer asked for edge cases, a bit more challenging but nothing impossible. The interviewer was really nice and encouraging.

    After that, I had another Phone/Screen interview which was basically the same. There was a basic question which was to code an observer pattern. It wasn't too hard but much more challenging than the first one, especially when the interviewer ask about some edge cases. Again the interviewer was really nice and encouraging and giving you clues when he saw I was blocked.

    I finally got to the last step, the onsite interview, and it was a bit different in my opinion. First, the process took a lot of time, I had a chat with a recruiter but I didn't know if I would have the interview in London or in Menlo Park. It took almost a month before I had the interview organised. I finally flew from London to Menlo Park for the onsite interview, the organisation was pretty easy though, everything is arranged by Facebook, I flew 2 days before the interview and returned the evening after the interview.

    The onsite interview consisted of 4x45 min interview, 2 coding interviews on a whiteboard, 1 conversation interview and 1 architecture interview. I felt like one of the coding interview was much harder than any other interview I had with Facebook and it was also much harder to get things right on a whiteboard, and I was absolutely terrible at this one. The other coding interview was more like the phone/screen interview, not too hard but a bit more challenging when I got to the edge cases, it made me wonder if I've just been very unlucky for the first coding interviews that I had a much harder one, but well that's part of the game. I can see that people were asked to code the array flatten in a iterative and recursive way for the first phone/screen interview, but I did it in a recursive way only, so I guess I got lucky in other interviews.

    In those interviews you will be mostly asked algorithms questions: iterative and recursive patterns, complexity (big O notation) and data structures. Don't hesitate to ask questions and to talk about the problem before even starting to code, that's very important especially that on a white board it's much harder to amend code (you can't copy paste or add line breaks everywhere), it's very important to know what you're going to do before writing anything, rather than writing as you think, like I did. Also the interviewers were very nice and encouraging even though I was terrible, they kept giving me clues and ways to think. I also was super stressed and slept around 3h the night before because of the jetlag, which didn't help.

    Besides those coding interviews that were the challenging part for me, the conversation interview was more about getting to know me and classic interview questions (Why Facebook? Why Front End? Tell about a project you had and how you solved it? Tell about a conflict you had at work and how you dealt with it?), for this one the recruiter told me about all these questions before so I had everything prepared.
    The architecture interview was more about how you would approach a front end problem and how you would structure your code, whether it's about HTML, CSS or Javascript. This one didn't seem to be too hard, if you have enough experience with layouts and front end issues, it shouldn't be fine.

    After that one, I came back to London in the evening, a recruiter called me on Skype 2 days later and told me the team didn't want to go forward. I was kind of expecting it since I haven't been good in the coding interviews, still I was very disappointed and frustrated that I went all the way to Menlo Park, visited the Facebook HQ and that I eventually failed... But still the recruiter was very nice and keen to give me any feedback, I was just so disappointed that I didn't ask anything.

    In the end I'd say it was a very positive experience, all the people I've been in touch with were very kind and encouraging, the interviews seemed reasonable and looked like things I should be able to solve if I was a top coder. I have to wait more than 1 year to try again and I might do it, I hope I can have the onsite interview in London this time.

    Questions d'entretien d'embauche

    • Given 2 identical DOM trees (but not equal) and one element of the first DOM tree, how would you find this element in the second DOM tree?   3 Réponses
    • Write an array flatten function.   3 Réponses
    • Write an emitter class:
      /*
      emitter = new Emitter();

      // 1. Support subscribing to events.
      sub = emitter.subscribe('event_name', callback);
      sub2 = emitter.subscribe('event_name', callback2);

      // 2. Support emitting events.
      // This particular example should lead to the `callback` above being invoked with `foo` and `bar` as parameters.
      emitter.emit('event_name', foo, bar);

      // 3. Support unsubscribing existing subscriptions by releasing them.
      sub.release(); // `sub` is the reference returned by `subscribe` above

      */   6 Réponses

    Réponse de Facebook

    15 déc. 2016 – Your Friends at Facebook

    Thanks for sharing your feedback. We're happy to hear that your interview experience was positive and our interview team was impactful. Please stay connected with us through our talent communities... Voir plus


  4. Utile (1)  

    Entretien de Front End 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 novembre 2016.

    Entretien

    This process consisted of an initial Skype chat (with a couple of technical questions at the end), then two technical screening Skype / CoderPad interviews, then an on-site interview. The on-site interview itself consisted of one behavioural interview, then two technical coding interviews, then one design / architecture interview. I was guided through the process by recruiters and a co-ordinator.

    Questions d'entretien d'embauche

    • Can you write a function that deeply flattens an array?   6 Réponses

  5.  

    Entretien de Front End Engineer

    Candidat à l'entretien anonyme
    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 en octobre 2016.

    Entretien

    1 HR Phone Call followed by a Video Call interview. The interview process was very pleasant and I can't say enough about how amazing the recruiter was that helped me through the process. I feel like I needed to brush up more on Javascript fundamentals, best practices with CSS, and being more careful with iteration and recursion concepts.

    Questions d'entretien d'embauche

    • I was asked basic Javascript concepts for the phone interview. For the video call I was asked to flatten an array recursively and iteratively in Javascript as well as to do some HTML and CSS design given a picture by the interviewer.   Répondre à cette question

  6. Utile (24)  

    Entretien de Front End Engineer

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

    Candidature

    J'ai postulé en ligne. Le processus a pris +4 mois. J'ai passé un entretien à Facebook (Seattle, WA (États-Unis)) en août 2016.

    Entretien

    I've interviewed with lots of big companies and overall have had mostly terrible experiences. Facebook was different, in a very good way. You can tell that a lot of thought and care have gone into their recruiting process.

    I saw that they were hiring for front end engineers in Seattle, so I applied on a whim and sort of forgot about it after a while. A couple months later, a recruiter reached out to me and we had an initial phone conversation. This was a very initial screen that was mostly non-technical with the exception of some quick and simple JavaScript pop-quiz questions at the end (== vs ===, describe event delegation, etc).

    Next step was a technical phone screen. This was pretty fast-paced as the interviewer was trying to squeeze in as much as possible in a short amount of time while leaving time at the end to field my questions. He did a very good job at keeping things moving and on track, asking me some general questions about my background and then some simple coding exercises to test my knowledge of HTML and CSS, and consequences of going with different design choices. Then a simple JavaScript tree problem.

    Next were the in person interviews. This is the part I thought they did exceptionally well compared with other companies. The whole process was extremely transparent and I was given lots of information and resources ahead of time so that I knew what to expect. It consisted of 2 coding (ninja) interviews, a design (pirate) interview, and a behavioral (jedi) interview, all about 45 minutes each. Between interviews a lunch was scheduled with another engineer, who is not part of the feedback loop, giving me plenty of opportunities to ask my questions about company and culture, as well as get a tour of the office.

    Overall, the questions seemed very relevant to the position. The interviewers were also super friendly and helpful along the way, and seemed to genuinely want you to succeed. No over-bearing egos set out to prove how much smarter than you they were, or trying to trip you up with trick questions or irrelevant questions (I've been asked physics questions before for front-end roles, sigh).

    Great experience.

    Questions d'entretien d'embauche

    • (Phone) Given two identical DOM tree structures, A and B, and a node from A, find the corresponding node in B.   1 réponse

    Négociation

    It sounds like the recruiter tries to negotiate on your behalf to get the highest offer up front. If you have a competing offer you may be able to push back and get a little more. In my case, I wasn't able to negotiate up on base salary, but was able to get more equity (they even gave me a little more than I had asked for).


  7. Utile (6)  

    Entretien de Front End Engineer

    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

    It was a forty five minute phone call. We chatted for a short amount of time to start then got into the questions. Afterwards, I asked some questions about the company.

    Questions d'entretien d'embauche

  8. Utile (1)  

    Entretien de Front End Engineer

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

    Candidature

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

    Entretien

    For an internship at MPK:
    Referred by a friend
    Recruiter sent a take home puzzle
    Had a phone interview
    Flown to MPK for a single on site interview and campus tour
    Received offer day after interview

    Questions d'entretien d'embauche


  9. Utile (17)  

    Entretien de Front End Engineer

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

    Entretien

    The interview process started with a 15 min technical call with the recruiter who asked basic JavaScript questions. I would recommend studying JS's built in data structures and their associated functions (i.e. map, forEach, reduce for an array).

    The recruiter scheduled the next phone interview (45 min technical with an engineer) shortly after. You can look at the other interviews to get a sense of the question difficulty/subject. I was asked to design a class with some member functions that required JS concepts such as closure and callbacks. It seemed they are really looking if you can write idiomatic JavaScript quickly and nearly bug free. After the phone interview I was contacted for an onsite interview.

    The onsite consisted of 3 interviews (2 technical with engineers , 1 behavorial/technical with an engineering manager). The first interview was a leetcode style problem with a front end slant. I was unable to complete the code but made significant progress. The second interview was less algorithm focused and more domain knowledge. This interview ended up being my favorite as we got to touch on many topics in front end development which gave me a chance to demonstrate my experience. The third interview was with an engineering manager. The first half was behavorial where I was asked about my background, motivation, and previous experience. The second half was a technical question about CSS.

    A couple days later my recruiter contacted me and said that I would be having a final 45 technical interview over the phone. I was asked a leetcode style question and after completing it was asked to optimize a snippet of code. A few days later my recruiter called and told me I had an offer.

    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.