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

      2 déc. 2023
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Offre refusée
      Expérience positive
      Entretien difficile

      Candidature

      Le processus a pris 2 mois. J'ai passé un entretien chez Meta (Londres, Angleterre) en févr. 2023

      Entretien

      The sun dipped below the skyline as I walked out of the sleek glass doors of the company's headquarters, my mind buzzing with the energy of a successful interview. The day had started with a mixture of nerves and excitement, but as I made my way through the welcoming lobby and into the interview room, those initial jitters transformed into a focused determination. The interview panel, consisting of experienced engineers and the tech lead, greeted me warmly. We began with the customary introductions, setting the stage for a conversation that would delve into my technical skills, problem-solving approach, and cultural fit within the company. The atmosphere was professional yet friendly, creating an environment where I felt comfortable showcasing my abilities. The technical questions were challenging, but I approached them with confidence, drawing upon my years of experience and the knowledge I had gained through various projects. The interviewers were not just interested in the right answers; they wanted to understand my thought process and problem-solving strategies. I appreciated the opportunity to discuss the nuances of different technologies and share my insights into software design principles. One particularly engaging part of the interview was a coding exercise. We gathered around a shared screen, and I was presented with a real-world problem the team had recently encountered. As I navigated through the code, explaining my thought process and making live modifications, I could see the nodding heads of the interviewers. It was a collaborative experience, and I felt a sense of camaraderie as we worked together to arrive at an elegant solution. Throughout the interview, I was also given the chance to learn more about the company culture and the projects they were currently undertaking. The team spoke passionately about their work, and their enthusiasm was contagious. It became evident that this was not just a job; it was an opportunity to contribute to something meaningful and be a part of a team that valued innovation and collaboration. As the interview drew to a close, we discussed my aspirations and how they aligned with the company's vision. The conversation felt more like a dialogue than an interrogation, and I left the room with a genuine sense of connection. The interviewers were not just evaluating my technical prowess; they were looking for a person who could bring not only skills but also a positive attitude and a collaborative spirit to the team. Walking out of the building, I couldn't help but feel a surge of optimism. The interview had been a two-way street, and I was just as excited about the prospect of joining this dynamic team as they seemed to be about welcoming a new member. As I headed home, I reflected on the meaningful exchange of ideas, the challenges overcome, and the genuine enthusiasm that permeated the entire process. The company wasn't just looking for a software engineer; they were looking for someone to be a part of their journey, and I was eager to take on that role.

      Questions d'entretien [1]

      Question 1

      One of the pivotal technical questions during the interview involved a complex coding scenario related to optimizing a critical component of their existing system. The challenge revolved around enhancing the efficiency of a data processing algorithm that the team was currently using. I was presented with a snippet of code and asked to identify potential bottlenecks, propose optimizations, and implement changes on the spot. The scenario demanded a deep understanding of algorithmic efficiency, data structures, and a keen eye for detail. As we collaboratively delved into the intricacies of the code, I discussed my thought process, identified areas for improvement, and implemented modifications to demonstrate how I would tackle real-world challenges within their technology stack. This technical question not only tested my coding skills but also highlighted my problem-solving approach and ability to think critically in a dynamic coding environment.
      Répondre à cette question

      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