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

      22 de jun de 2017
      Candidato de entrevista anónimo
      New York, NY
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. Acudí a una entrevista en Meta (New York, NY) en jun 2017

      Entrevista

      Was contacted by a Facebook recruiter on Linked In for my expertise in Android. We conversed on and off over a few weeks as I am on business travel a lot, and he was able to setup a phone-based technical interview for me that met my scheduling needs. This recruiter was incredibly professional and interpersonal, provided plenty of prep resources, and made me feel like he was really rooting for me. Awesome! Technical phone interview went poorly. The interviewer introduced himself and immediately asked me a very vague Android question. I feel that I handled my responses very well in an attempt to narrow down what he may be fishing for while demonstrating myself to be adept with Android. Yet I was given very little positive feedback, and he seemed to ask the same question several more times. Apparently, I have no clue what he was asking. At this point, I felt like an item on his to-do list. He denied the compile and run time capabilities of coderpad, making for a much more theoretical text-only based environment. So the solution would have to be proven to work via tracing it, which wastes time and renders coderpad pointless in my opinion. It was difficult enough for me to understand the thick accent that it turned me off to asking clarifying questions during the coding problem. Instead, I felt that I had to voice every thought, which did not allow me to think more deliberately. I became a bit flustered and floundered for a moment, despite the question being relatively simple. I recognized this, and had prepared for it by having a white board at the ready. I requested to have a moment to collect my thoughts and draw on my board quick. I am a visual person and there are things that are just more easily drawn than typed out. He declined, telling me to stick to the editor. At this point, it was game over. Typing my thoughts in the editor was making a mess as I traced my logic over the examples because the cursor was jumping all over. I believe this was because the editor was technically set to Java, and I should have made a comment block around his question and my typing. I also was not allowed to create a runnable Java class to put my code in. So I was cut off before long. I tried to exchange some more pleasantries but he was clearly done. In any case, I had asked him why he chose Facebook and I got a dissatisfying answer. I would gander a guess that he was not nearly as stoked about the mission and impact of Facebook as I am, and I don't even work there! I think I had most of the main working principles and demonstrated that I could code Java, but the solution was not complete. (To be honest, I think I suffered a small panic attack.) It does not matter if you invented a robot that defeats the Turing Test, the technical interviewer may not care to even read your resume and will shut you down if you do not perform flawlessly. With these tech giants, you won't be hired without a perfect performance. The recruiter sent me a canned rejection two days later with no response to my reply. I completely understand and respect the decision to be cutoff. But I feel like it took two to make this a waste of everyone's time.

      Preguntas de entrevista [1]

      Pregunta 1

      Balance a string with parentheses. "a(b)" -> "a(b)"; "(((((" -> ""; "(()())" -> "(()())"; ")ab(()" -> "ab()"; etc...
      3 respuestas
      8

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

      Entrevista para Software Engineer

      29 de jun de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Move zeroes in an array to the end while keeping non-zero element order, in place
      Responder pregunta

      Entrevista para Software Engineer

      23 de jun de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      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

      Preguntas de entrevista [1]

      Pregunta 1

      Leetcode med. Cant remember the exact question
      Responder pregunta

      Entrevista para Software Engineer

      24 de jun de 2026
      Empleado anónimo
      Menlo Park, CA
      Oferta aceptada
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Meta (Menlo Park, CA)

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Design Twitter and consider if it was suddenly an extremely low latency env
      Responder pregunta