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

      22 juin 2017
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Meta (New York, NY) en juin 2017

      Entretien

      Was contacted by a Facebook recruiter on Linked In for my expertise in Android. We conversed on and off over a few weeks as I am on business travel a lot, and he was able to setup a phone-based technical interview for me that met my scheduling needs. This recruiter was incredibly professional and interpersonal, provided plenty of prep resources, and made me feel like he was really rooting for me. Awesome! Technical phone interview went poorly. The interviewer introduced himself and immediately asked me a very vague Android question. I feel that I handled my responses very well in an attempt to narrow down what he may be fishing for while demonstrating myself to be adept with Android. Yet I was given very little positive feedback, and he seemed to ask the same question several more times. Apparently, I have no clue what he was asking. At this point, I felt like an item on his to-do list. He denied the compile and run time capabilities of coderpad, making for a much more theoretical text-only based environment. So the solution would have to be proven to work via tracing it, which wastes time and renders coderpad pointless in my opinion. It was difficult enough for me to understand the thick accent that it turned me off to asking clarifying questions during the coding problem. Instead, I felt that I had to voice every thought, which did not allow me to think more deliberately. I became a bit flustered and floundered for a moment, despite the question being relatively simple. I recognized this, and had prepared for it by having a white board at the ready. I requested to have a moment to collect my thoughts and draw on my board quick. I am a visual person and there are things that are just more easily drawn than typed out. He declined, telling me to stick to the editor. At this point, it was game over. Typing my thoughts in the editor was making a mess as I traced my logic over the examples because the cursor was jumping all over. I believe this was because the editor was technically set to Java, and I should have made a comment block around his question and my typing. I also was not allowed to create a runnable Java class to put my code in. So I was cut off before long. I tried to exchange some more pleasantries but he was clearly done. In any case, I had asked him why he chose Facebook and I got a dissatisfying answer. I would gander a guess that he was not nearly as stoked about the mission and impact of Facebook as I am, and I don't even work there! I think I had most of the main working principles and demonstrated that I could code Java, but the solution was not complete. (To be honest, I think I suffered a small panic attack.) It does not matter if you invented a robot that defeats the Turing Test, the technical interviewer may not care to even read your resume and will shut you down if you do not perform flawlessly. With these tech giants, you won't be hired without a perfect performance. The recruiter sent me a canned rejection two days later with no response to my reply. I completely understand and respect the decision to be cutoff. But I feel like it took two to make this a waste of everyone's time.

      Questions d'entretien [1]

      Question 1

      Balance a string with parentheses. "a(b)" -> "a(b)"; "(((((" -> ""; "(()())" -> "(()())"; ")ab(()" -> "ab()"; etc...
      3 réponse(s)
      8

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

      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

      Entretien pour Software Engineer

      23 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      1 leetcode med, 1 leetcode hard. make sure you know your DSA and leetcode questions. I wasn't able to get an offer bc i didnt complete the second question. Got a reply 2 days later saying they would move on

      Questions d'entretien [1]

      Question 1

      Leetcode med. Cant remember the exact question
      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