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 Senior 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 Senior Software Engineer

      19 juill. 2010
      Candidat à l'entretien anonyme
      Palo Alto, CA
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez Meta (Palo Alto, CA) en avr. 2010

      Entretien

      This was probably one of the longest interview processes I had to go through. The recruiter was wonderful. She was always very professional and responsive. First I had a phone interview with the hiring manager. It was a very straight forward conversation and he asked me to give him some pseudo code on how to square a number using their online tool. Standard algorithm questions which I answered correctly. Afterward, the recruiter said it went well and that she would be in contact with me about what the next steps are. A week goes by and she calls me back telling me I have to write an Adobe Air or Java application using the Facebook API's. I thought it was a little bit much for them to ask me to spend my time writing something I would not be getting paid for. I really wanted to get the job and impress the hiring manager though so I spent my free time, over a two week period making something that looked great and worked really well. It then took them two months to review the application. To me this was totally unprofessional and kind of a slap in the face. The recruiter was in contact with me the whole time and told me they were all busy with their big change to the privacy features. Finally the hiring manager looked at the application but the recruiter told me they wanted someone else internal to look at the code as well. She told me they were impressed with the application and had rejected a lot of other candidates applications right away. I sat in limbo another few weeks while another person looked at the application. The recruiter then calls me back to tell me that the position I was applying for was dropped. Not that they hired someone else, but that they changed the role I was applying for completely. I think the software engineering interview process has hit an all time low. First they make the engineer jump through hoops of logic games. Then spout out algorithms and uses of design patterns like robots. Finally you have to spend your free time writing something that they are only going to throw in the garbage. We have all really fallen to a sad state.

      Questions d'entretien [1]

      Question 1

      Write some pseudo code to raise a number to a power.
      10 réponse(s)
      7

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

      Entretien pour Senior Software Engineer

      12 avr. 2026
      Candidat à l'entretien anonyme
      Menlo Park, CA
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta (Menlo Park, CA)

      Entretien

      I went through Meta's full interview loop for an E5/E6 Software Engineer role. The process included the standard four-round onsite: two coding rounds, a system design round, a behavioral round, and an AI coding round that Meta has added to their loop. I prepared extensively for each stage — grinding LeetCode-style problems for the coding rounds, building a library of system design references, and writing out STAR-format behavioral answers calibrated to Meta's E5/E6 expectations, drawing on my Oracle Cloud Infrastructure work across the Multicloud Observability team (control plane unification, data plane migration to Oracle Managed Kubernetes, and the Oracle Database at AWS buildout). Ultimately, I received a rejection with a one-year cooldown before I can reapply. Looking back honestly, a few weaknesses stood out: Coding execution under time pressure. While I could solve the problems, I wasn't always optimal on the first pass. I spent time re-deriving approaches instead of pattern-matching quickly, which cost me on the second problem in at least one round. System design depth vs. breadth tradeoff. My background is deep in cloud infrastructure and observability, so when the design prompt pulled toward consumer-scale product systems (feed ranking, social graph type problems), I leaned on general principles rather than Meta-specific intuition. I covered the fundamentals but didn't always drive the conversation into the nuanced tradeoffs interviewers wanted to hear. Behavioral calibration to Meta scale. My STAR stories were strong on technical substance, but a few of my impact framings were sized for Oracle's context rather than translated into the scale and cross-org influence language Meta's bar expects at E5/E6. AI coding round unfamiliarity. This was a newer format for me and I hadn't practiced it as deliberately as the traditional rounds, so my workflow with the AI tooling wasn't as fluid as it could have been. The cooldown gives me a clear runway to address each of these before reapplying.

      Entretien pour Senior Software Engineer

      7 avr. 2026
      Candidat à l'entretien anonyme
      Menlo Park, CA
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

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

      Entretien

      Reached out to a recruiter via a friend. Directly got the invitation to schedule full loop interview. Completed Meta full loop interview process, with one reschedule. Participated in system design, behavioral, coding, and AI-enabled coding rounds, covering core software engineering and problem-solving skills.

      Entretien pour Senior Software Engineer

      25 mars 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Meta

      Entretien

      started first round with 1 phone interview (2 questions), then second round with 2 onsite technical (4 questions), after one system design question and lastly 1 behavioral interview, here they asked quite alot of questions

      Questions d'entretien [1]

      Question 1

      merge 3 ordered lists together
      Répondre à cette question