Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Meta

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Meta | Empleos en Meta | Sueldos en Meta | Prestaciones en Meta
      Entrevistas en MetaEntrevistas para el cargo de Senior Software Engineer en MetaEntrevista en Meta


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Senior Software Engineer

      4 feb 2022
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Me postulé en línea. El proceso tomó 2 meses. Acudí a una entrevista en Meta en ene 2022

      Entrevista

      - First contact First Recruiter called to confirm. Asked salary expectation. HERE's where you shouldn't give a number, look for youtube videos on "how to negotiate your offer" for why) Recruiter gives a very precise walkthrough of the whole process and gives you a lot of material to study and a timeline. - Create profile Next step you create a profile in their recruiting site and confirm availability for the interview. There are plenty of material to study there, even better than Leetcode because here you know what to expect. - First Interview (45 mins, video conf) 1 easy problem 1 medium Didn't hear anything for a week so I emailed the recruiter and they responded they liked me and my availability for a second round of interviews and you get passed to another recruiter. - Second interview(s) round. You have to schedule a full day for the next round. Interview day 5 x 45 min interviews. Coding: 2 x 45 min video conf with Sr Engineers from the department I was applying for. 2 question each, 1 medium 1 hard Behavioral: 1 x 45 min with one of the managers of the org you're applying. System Design: 2 x 45 min with Staff or higher Engineers (8+ years in Facebook) The recruiter also gives you details on how to answer these System Design interview, be sure to read those PDF's they even can give you temporary codes for some practice sites. - Resolution I interviewed on Friday, on Monday Recruiter told me they'll review the application during the week and will let me know. On Wednesday they told me my application is going to be reviewed and asked for a day when we can talk, we agreed on Thursday. Thursday I was super ready to bring my negotiation skills as I was certain I was going to get an offer (otherwise why didn't they tell me on Monday right?) Sadly it was to inform me I wasn't selected and I can re-apply within 6 months. Overall process: Everybody was super kind and welcoming 10/10 will apply again. The recruiters were excellent and they know their stuff. They are super transparent and they tell you what to expect and give you all kinds of resources. I studied 2 weeks, for 3 hrs every day for the coding and it seems it was still not enough. A colleague of mine said they studied for 6 months, they got the job. So my recommendation: - Do study, study hard and seriously (I know this is hard if you already have a job) - Learn that process to solve questions by hearth, Facebook gives you at least two 30+ minutes long on what a successful coding session interview looks like - The coding doesn't even have to compile, most of the time is ok if you say "here I create a `validate(input)` function that does xyz and the interviewer it's ok with that. Don't waste time typing how you get a sublist or something just call "`sublist = sublist(arr, i, j, etc)`" - Do learn that O notation by heart is not that hard. - Listen to the interviewer. Unfortunately in my case I was listening but couldn't come up with an answer "How would you improve this part here" Me: "uhmm well I would... (says something not really relevant)" - On the System Design, focus on the meat, the relevant part of the problem, not so much on the scaffolding. - Rehearse your behavioral answers with a human. The first time I practice I was just babbling, after a few rounds I was able to answer concisely and favorable (again, recruiter tells you to follow the STAR method) - I would say spend 40% on coding interviews, 35% on System Design (gosh, I choked trying to multiply 50k x 1 million users x days x years ) and 25% behavioral. I see a lot of people complaining about LeetCode type of questions, but they give you a guide with at least 20 problems, they explain you thoroughly how to solve them, and they give you a lot of time to practice. If you can’t learn that, maybe you’ll struggle in the real job.

      Preguntas de entrevista [1]

      Pregunta 1

      Signed NDA. But read description for an idea.
      Responder pregunta
      8

      Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Meta

      Entrevista para Senior Software Engineer

      12 abr 2026
      Candidato de entrevista anónimo
      Menlo Park, CA
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Meta (Menlo Park, CA)

      Entrevista

      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.

      Entrevista para Senior Software Engineer

      7 abr 2026
      Candidato de entrevista anónimo
      Menlo Park, CA
      Sin ofertas
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. Acudí a una entrevista en Meta (Menlo Park, CA)

      Entrevista

      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.

      Entrevista para Senior Software Engineer

      25 mar 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      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

      Preguntas de entrevista [1]

      Pregunta 1

      merge 3 ordered lists together
      Responder pregunta

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      Maze
      4.5★Remuneración y prestaciones