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

      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

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Meta | Ofertas de empleos en Meta | Sueldos en Meta | Beneficios en Meta
      Entrevistas de MetaEntrevistas para el puesto de Software Engineer en MetaEntrevista de Meta


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Software Engineer

      14 ene 2015
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 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 opiniones sobre las entrevistas para el puesto de Software Engineer en Meta

      Entrevista de Software Engineer

      16 jun 2026
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia neutra
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      Got a referral through a friend who worked at Meta, which sped up the entire process. After a casual initial chat, I went through a technical interview where I faced a DSA question about validating palindromes. The interviewer was friendly but rigorous. During prep, I had spent time with the coding challenges on PracHub, and it was funny to see a similar palindrome question pop up. Overall, I received an offer, but ultimately decided to decline it after careful consideration.

      Preguntas de entrevista [1]

      Pregunta 1

      Given a string s, return true if it can be a palindrome after deleting at most one character (Valid Palindrome II).
      Responder pregunta

      Entrevista de Software Engineer

      16 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      Recruiter call was pretty standard, first round was 2 Meta tagged LC mediums in 45 minutes. On-site was 2 coding sessions of 2 LC mediums, a system design interview and a behavioral interview with an engineering manager.

      Preguntas de entrevista [1]

      Pregunta 1

      How do you answer if someone asks how long a deliverable or project will take?
      Responder pregunta

      Entrevista de Software Engineer

      5 jun 2026
      Candidato de entrevista anónimo
      Seattle, WA
      Sin oferta
      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

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      Google
      4.5★Remuneración y beneficios
      avatar
      Amazon
      3.7★Remuneración y beneficios
      avatar
      Fiverr Inc.
      3.5★Remuneración y beneficios
      avatar
      Booking.com
      4.2★Remuneración y beneficios