Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Meta

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Meta | Offres d’emploi chez Meta | Salaires chez Meta | Avantages sociaux chez Meta
      Entretiens chez MetaEntretiens d’embauche pour Software Engineer chez MetaEntretien chez Meta


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer

      27 août 2019
      Candidat à l'entretien anonyme
      Redmond, WA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 3 mois. J'ai passé un entretien chez Meta (Redmond, WA) en août 2019

      Entretien

      Had a recruiter who kept sending me ping emails every month or so. After several months I responded with my canned "don't bother unless you can meet these criteria" message (things like relocation being a non-starter, salary and equity requirements, industries I won't work in, etc). He said he thought they could clear the bar on these issues and I ended doing a quick chat with a hiring manager about 2 weeks later, followed by a tech screen 2 weeks after that, and then another phone conversation about moving forward with an in-person interview a week and a half after that. So at this point it's a month and a half after my first response to the recruiter and I'm waiting on FB to schedule the in-person. At this point it's right before the July 4th holiday, so I figure it's not unreasonable if it takes a bit to get the scheduling together. I spend 3 weeks waiting before I get an email stating that they lost someone on their recruiting team, lost track of ME, and asking if I still want to come in for an in-person in the next couple of weeks. OK then. I said sure. The next day I get an email tentatively scheduling my on-site for another 2 weeks in the future. Along with that I get a flurry of mostly automated emails asking me for all sorts of information needed for travel arrangements. I live in Seattle. The on-site is in Redmond. I point out that I don't need travel accommodations, although I'm kind of sad I didn't just leave it, just to see if they were able to book a flight from SEATAC to SEATAC. One thing I asked about before the on-site was whether I could bring in a laptop to do coding questions on. My handwriting is bad and my hand tends to cramp up after a few hours holding dry-erase markers, and I generally prefer to use an editor while coding. I was told that while I wouldn't be allowed to bring my own device on-site, they had the option for candidates to do problems either on a whiteboard or on a company provided laptop for that purpose. Finally on the day of the interview I go in and do the thing. It's the standard "large tech company" interview cycle, where you spend an hour or so with different people, each one tasked with evaluating some aspect of your abilities. Right off the bat I was told that there was an issue with the interviewee computers and that I wouldn't be able to use one, for coding problems or otherwise. Most of the sessions involved me spending most of my time at the whiteboard, except for one case where I was talking to someone who was in an SF office over a video conference connection. He exclusively asked the soft questions like "Tell me about something you did that you were particularly proud of". The questions were pretty familiar because they're the kind I tend to ask when I've done no prep for an interview. That might seem harsh, but during the back and forth I got several other signals that he really hadn't done *anything* to research me. I'm not exactly famous or anything, but I have written a book specifically related to the work Facebook Reality Labs does. If you google my full name, you are immediately presented with my LinkedIn, GitHub, Twitter and Amazon profiles, all of which contain a fountain of information you could use to personalize an interview session. After the interview I didn't hear back for a full week, at which point they said they wouldn't be moving forward. Unusually, the recruiter did specify that the feedback had been mixed, and that the negatives had come from the two design oriented segments of the interview. Overall it wasn't a horrific experience, but I'm still rating it a negative because * frequent delays * "losing track of me" * trying to setup travel arrangements for a local candidate * setting expectations of interview conditions (being able to code on a computer) and then breaking them on the day * no one, especially the "soft questions" guy, appeared to have any idea who I was or made any reference to my existing history in or contributions to VR

      Questions d'entretien [3]

      Question 1

      Design question: Given an internet server with 12 cores, 60 GB of memory and a big network pipe (he specified, but I can't remember the actual value), how would you implement a caching service with 3 functions that boils down to void set(string key, byte[] data); byte[] get(string key) void delete(string key) where the key is between 1 and 255 characters, and where the data block can be up to 1 MB. Further, how would you design the system to be effective when some key becomes part of something that goes viral, such that there is suddenly a much higher rate of requests for it
      1 réponse

      Question 2

      Imagine a two dimensional NxM grid of boxes. Each box may contain a pipe, which can connect to any of the 4 ordinal directions. Write a function that returns true if the pipe network(s) described by the grid are closed, i.e. there are no pipes connected to edges of the grid, or connected to an adjoining cell that does not have a pipe connecting to the shared side.
      1 réponse

      Question 3

      The last memorable questions were all about vector math (in the sense of geometric vectors, not SIMD optimizations), and most of the time was spent with me trying to implement intersection tests, first sphere/sphere and then sphere/capsule. Note that this interview was at Facebook Reality Labs, so this kind of question wasn't out of left field, and I expected that there would be some level focus on 3D rendering fundamentals.
      1 réponse
      9

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Meta

      Entretien pour Software Engineer

      5 juil. 2026
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta (Londres, Angleterre)

      Entretien

      Generic LeetCode-style questions, many tagged as Meta, so extensive preparation is required to perform well in the technical interview. The experience varies significantly - some interviewers provide hints and guidance, while others expect candidates to solve problems independently with minimal assistance.

      Questions d'entretien [1]

      Question 1

      Find smallest value in BST
      Répondre à cette question

      Entretien pour Software Engineer

      2 juil. 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      Spoke with interviewer over video conferencing. He was very communicative . He answered my questions. Asked me BFS question. A question that involved BFS search. Given a matrix, I am suppose to find a path from top left to down right.

      Questions d'entretien [1]

      Question 1

      A question that involved BFS search. Given a matrix, I am suppose to find a path from top left to down right.
      Répondre à cette question

      Entretien pour Software Engineer

      29 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien facile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      The technical round hit me with a classic array manipulation problem: moving zeroes to the end without disrupting the order of non-zero elements. As I tackled it, I felt a wave of familiarity wash over me; I had just practiced a similar challenge on PracHub. The rest of the interview followed a straightforward path, with some easy behavioral questions sprinkled in. Overall, it felt very easy, but I wasn’t quite the right fit for what they needed, so I didn’t receive an offer.

      Questions d'entretien [1]

      Question 1

      Move zeroes in an array to the end while keeping non-zero element order, in place
      Répondre à cette question