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

      14 ene 2015
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Meta

      Entrevista

      I was contacted by a recruiter, I came onsite for an initial screen. I thought the interviewer was very nice, and the question was reasonable. However, the frustrating part for me was that for the given question, there were a few different ways to solve it. From my perspective, it seemed that the approach I used to solve the question was not what the interviewer had in mind. I understand that you should listen to an interviewer when they interrupt you or give you hints, but to me it seemed like the "hints" were basically from the perspective of "you're not solving this the way I would solve it, even though both of our solutions are O(n)". The result was that I was basically having to write out a problem on a white board and constantly have my train of thought interrupted. The interruptions were unnecessary, and I had to clarify to the interviewer that my intent would indeed work. Example interruption: Interviewer: "That array index is giving you the same result as the other value" Me: "No, that's a different variable name" Interviewer: "Oh, oops. Continue" or Interviewer: "Wait, why are you replacing the for loop with a while loop?" Me: "Because I want to be able to manipulate the cursor directly" Interviewer: "Oh, ok. Continue" In the above statement, it's clear that the usual method of solving the problem did not involve a while loop (but it could be done to solve the problem). After my solution, the interviewer explained the most straightforward solution to the problem which basically leveraged the constraints of the problem itself, and after seeing that then of course the problem was trivial to implement. So to me, it seemed like the question was more of a riddle than a coding exercise, which I believe to be a bad interview question, and at my current company it's accepted as the WORST type of interview question. It was rather embarrassing for me to be turned down, especially on just the initial screen, but another qualm I had was that screens are generally meant to filter out candidates that can't code at all, not candidates who are questionable in their skills (from my perspective my skills aren't questionable, but clearly I did not give my best performance in this screen). To me it felt as though the interviewer in this case did not have much experience. While I was answering the questions that were given to me, I was having to explain a few quirks to the python language that the interviewer clearly did not know i.e. "Oh, I didn't know you could compare dictionaries like that". For that to be said, I can only infer that the ONLY thing this interviewer was looking for is if I answer the question that was given to me in the exact way they wanted it solved.

      Preguntas de entrevista [1]

      Pregunta 1

      Basically an array manipulation problem
      Responder pregunta
      8

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

      Entrevista para Software Engineer

      10 jun 2026
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      Took about a month from start to finish, which felt longer than I expected. After a couple of initial phone screenings, I faced a challenging technical round focused on system design. It was during this round that I was asked to describe overcoming a major career challenge. Interestingly, I had just reviewed a similar framework on PracHub, which helped me articulate my thoughts clearly. Overall, I appreciated the depth of the process and ended up accepting the offer.

      Preguntas de entrevista [1]

      Pregunta 1

      Describe Overcoming a Major Challenge in Your Career
      Responder pregunta

      Entrevista para Software Engineer

      5 jun 2026
      Candidato de entrevista anónimo
      Seattle, WA
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Meta (Seattle, WA)

      Entrevista

      The entire process usually takes 3–8 weeks, depending on scheduling and the specific role. Coding interviews heavily emphasize common DSA topics such as arrays, strings, trees, graphs, BFS/DFS, heaps, hash maps, and dynamic programming. System design becomes increasingly important for E4+ positions.

      Preguntas de entrevista [1]

      Pregunta 1

      Given an array of integers and a target value, return the indices of two numbers that add up to the target
      Responder pregunta

      Entrevista para Software Engineer

      1 jun 2026
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      Unexpectedly, the first question in the technical round felt familiar. It was about finding a subset of strings with unique character concatenation — same problem I had worked through on PracHub a few days earlier. The interview included a recruiter screen followed by a rigorous pair of technical interviews where I tackled data structures and algorithms alongside system design concepts. After successfully answering a few more challenging DSA questions, I received an offer. The entire experience was intense but ultimately rewarding, and I happily accepted the position.

      Preguntas de entrevista [1]

      Pregunta 1

      Given an array of strings, pick a subset whose concatenation contains no duplicate characters, and return the maximum possible length of that concatenation.
      Responder pregunta

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

      avatar
      Maze
      4.5★Remuneración y prestaciones