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

      16 sept. 2015
      Candidat à l'entretien anonyme
      Seattle, WA
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Meta (Seattle, WA) en juill. 2015

      Entretien

      If you're a solid developer with years of experience working on high visibility products used by millions of people (and references to back it up) don't expect the interview process at Facebook to just work. It really comes down to how much you prepare yourself mentally to code within the context of an interview, and how much you study Career Cups as well as the other resources given to you by the recruiter. Sadly, you don't have to be a great developer at all. What's interesting is that none of these skills have been necessary during my 17 years of real world experience. I never had to write code on a whiteboard (except for other interviews) and I don't see how "writing code fast" should be considered a measurement of someone's productivity and code quality. That sort of thinking seems naive and haphazard to me. What frightens me is that I think Facebook truly believes they're "raising the bar" with this system. But they're not always hiring good people, and they're probably turning down a lot of great folks. The coding tests were super easy. Two were questions I've actually asked myself while conducting interviews for another company which was aimed towards entry level developers. I really wish they would have asked more challenging questions. I was able to finish them before the end of each panel, and with optimal solution. The design question they gave me actually aligned with something I developed and designed for a product used by millions. I felt good with how everything went at the end of the day, but somehow I failed at *both* coding and design. Interesting... whatever. Two of my friends--whom of which I mentored at my last company--were able to get offers at Facebook (same office, same interview process) but they were *not* the best coders nor the top performers, so if you get turned down at Facebook, don't take it seriously. They say there is some "randomness" in the interview, but it just seems strange that common sense didn't kick anywhere to question the obvious, or just the fact I was interviewed by a few people with only 5 years experience. Smart, but inexperienced (and somewhat arrogant) wanting to judge you with entry level coding questions. Half of the people that interviewed me didn't go through the interview process themselves. They were brought in by acquisitions. Specifically for a product that isn't doing very well right now. I was excited about the idea of working there initially, but after the interview, I wasn't so sure anyway. They do try to put a lot of emphasis on finding great developers, but many of the folks who interviewed me mentioned the codebase was a mess (probably from writing code so quickly and not thinking through it) And their open office (no cubes, no walls, just wires and computers everywhere) is a bit distracting. Not something genuinely appreciated by the people working there who used to have their own office. When you need to focus and get quality work done, there are only so many dedicated rooms to use and they're usually taken. Coupled with the fact that they're Seattle office is located in one of the worst traffic areas, I wasn't so sure I would have accepted anyway.

      Questions d'entretien [1]

      Question 1

      Signed an NDA but just check the resources given to you by the recruiter
      Répondre à cette question
      5

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

      Entretien pour Software Engineer

      24 juin 2026
      Employé (anonyme)
      Offre acceptée
      Expérience neutre
      Entretien facile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      Overall, the process took a little over two weeks, which felt a bit longer than I anticipated. After a quick screening, I went through two technical rounds focusing on coding and DSA concepts. One of the questions was a classic palindrome check; mid-way through, I realized it was something I had practiced on PracHub just days earlier. The final step was a casual behavioral interview. I was relieved to get an offer shortly after, which I happily accepted.

      Questions d'entretien [1]

      Question 1

      Given a string, determine if it is a valid palindrome considering only alphanumeric characters and ignoring case.
      Répondre à cette question

      Entretien pour Software Engineer

      24 juin 2026
      Employé (anonyme)
      Menlo Park, CA
      Offre acceptée
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Meta (Menlo Park, CA)

      Entretien

      It's honestly striaght from leetcode tagged There are no surprises if you do tagged you would be good and do well. System design is much harder. Would recommend using hello interview.

      Questions d'entretien [1]

      Question 1

      Design Twitter and consider if it was suddenly an extremely low latency env
      Répondre à cette question

      Entretien pour Software Engineer

      24 juin 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      Grateful doesn't even begin to describe how I feel about landing this role. The interview loop was smooth and friendly. They kicked things off with a technical round where I faced a DSA question about verifying an alien dictionary. Lucky for me, the time I'd spent on PracHub paid off, as it had the same type of problem just days before. After that, I had a system design discussion and a behavioral interview. Everything felt very collaborative, and by the end, I received an offer that I was thrilled to accept.

      Questions d'entretien [1]

      Question 1

      Given a list of words written in an alien language and the order of letters in that language's alphabet, determine whether the words are sorted lexicographically (Verifying an Alien Dictionary). Walk through the comparison approach using a character-to-index map, the O(C) time complexity where C is total characters, and how you'd extend it to handle words with mixed-case letters or words containing characters outside the given alphabet.
      Répondre à cette question