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. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      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

      14 janv. 2015
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Meta

      Entretien

      I was contacted by a recruiter, I came onsite for an initial screen. I thought the interviewer was very nice, and the question was reasonable. However, the frustrating part for me was that for the given question, there were a few different ways to solve it. From my perspective, it seemed that the approach I used to solve the question was not what the interviewer had in mind. I understand that you should listen to an interviewer when they interrupt you or give you hints, but to me it seemed like the "hints" were basically from the perspective of "you're not solving this the way I would solve it, even though both of our solutions are O(n)". The result was that I was basically having to write out a problem on a white board and constantly have my train of thought interrupted. The interruptions were unnecessary, and I had to clarify to the interviewer that my intent would indeed work. Example interruption: Interviewer: "That array index is giving you the same result as the other value" Me: "No, that's a different variable name" Interviewer: "Oh, oops. Continue" or Interviewer: "Wait, why are you replacing the for loop with a while loop?" Me: "Because I want to be able to manipulate the cursor directly" Interviewer: "Oh, ok. Continue" In the above statement, it's clear that the usual method of solving the problem did not involve a while loop (but it could be done to solve the problem). After my solution, the interviewer explained the most straightforward solution to the problem which basically leveraged the constraints of the problem itself, and after seeing that then of course the problem was trivial to implement. So to me, it seemed like the question was more of a riddle than a coding exercise, which I believe to be a bad interview question, and at my current company it's accepted as the WORST type of interview question. It was rather embarrassing for me to be turned down, especially on just the initial screen, but another qualm I had was that screens are generally meant to filter out candidates that can't code at all, not candidates who are questionable in their skills (from my perspective my skills aren't questionable, but clearly I did not give my best performance in this screen). To me it felt as though the interviewer in this case did not have much experience. While I was answering the questions that were given to me, I was having to explain a few quirks to the python language that the interviewer clearly did not know i.e. "Oh, I didn't know you could compare dictionaries like that". For that to be said, I can only infer that the ONLY thing this interviewer was looking for is if I answer the question that was given to me in the exact way they wanted it solved.

      Questions d'entretien [1]

      Question 1

      Basically an array manipulation problem
      Répondre à cette question
      8

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

      Entretien pour Software Engineer

      10 juin 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      Took about a month from start to finish, which felt longer than I expected. After a couple of initial phone screenings, I faced a challenging technical round focused on system design. It was during this round that I was asked to describe overcoming a major career challenge. Interestingly, I had just reviewed a similar framework on PracHub, which helped me articulate my thoughts clearly. Overall, I appreciated the depth of the process and ended up accepting the offer.

      Questions d'entretien [1]

      Question 1

      Describe Overcoming a Major Challenge in Your Career
      Répondre à cette question

      Entretien pour Software Engineer

      5 juin 2026
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta (Seattle, WA)

      Entretien

      The entire process usually takes 3–8 weeks, depending on scheduling and the specific role. Coding interviews heavily emphasize common DSA topics such as arrays, strings, trees, graphs, BFS/DFS, heaps, hash maps, and dynamic programming. System design becomes increasingly important for E4+ positions.

      Questions d'entretien [1]

      Question 1

      Given an array of integers and a target value, return the indices of two numbers that add up to the target
      Répondre à cette question

      Entretien pour Software Engineer

      1 juin 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      Unexpectedly, the first question in the technical round felt familiar. It was about finding a subset of strings with unique character concatenation — same problem I had worked through on PracHub a few days earlier. The interview included a recruiter screen followed by a rigorous pair of technical interviews where I tackled data structures and algorithms alongside system design concepts. After successfully answering a few more challenging DSA questions, I received an offer. The entire experience was intense but ultimately rewarding, and I happily accepted the position.

      Questions d'entretien [1]

      Question 1

      Given an array of strings, pick a subset whose concatenation contains no duplicate characters, and return the maximum possible length of that concatenation.
      Répondre à cette question