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

      28 de abr de 2025
      Candidato de entrevista anónimo
      Seattle, WA
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

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

      Entrevista

      My Meta E4 Interview Experience All the rounds were 45 minutes long, but you actually get only 35-40 minutes for the main task, as the first 5-10 minutes are spent on introductions and answering any questions. Round 1 – Screening (DSA Coding) (45 min) The first round was a 45-minute coding interview with two questions—one easy and one medium. I managed to solve both within time, though I initially missed some points. The interviewer gave me a hint, and I quickly adapted to arrive at the correct solution. Clearing this round, I got a call the next day from the recruiter to schedule further interviews. Round 2 – Product Architecture Design (System Design)(45 min) In this 45-minute round, I had 40 minutes to design a system, covering API design, database schema, and high-level architecture. I explained the full application flow, covering both functional and some non-functional requirements. The discussion was structured, and I felt confident about my explanations. Round 3 – DSA Coding (45 min) This round had one easy and one medium-level coding question, both with follow-ups. I discussed edge cases and ensured my approach was optimal. I managed to solve both questions in time. Round 4 – System Design (45 min) A medium-level design problem where functional requirements were given. I covered APIs, schema, and high-level design but felt the discussion could have been structured better. Overall, this round went just average. Round 5 – DSA Coding (45 min) Two medium-level questions, both with variations. I solved the first but made a small mistake in time complexity. The second was quite tricky—without prior exposure, solving it would’ve been tough. I managed to crack it but made coding errors, which I believe hurt my performance. Round 6 – Behavioral Interview (45 min) This round had 3-4 standard behavioural questions based on Meta’s core values. I used my prepared stories to answer, but in hindsight, I feel it was an average performance. Final Outcome – Rejected 💔 A week later, the recruiter called me back and told me the panel is not moving forward with me. It was heartbreaking because I felt so close. Key Takeaways At Meta, speed, accuracy, and correct syntax matter a lot. The experience also depends on who interviews you, seasoned interviewers structure discussions well, while newer ones may unintentionally make it harder. Hard work + luck both play a role. While this rejection stung, I’ve learned a lot and will come back stronger. Bonus 😉 – If your Meta interview is scheduled and you need any help preparing, feel free to DM me. I’d be happy to share resources and my experience!

      Preguntas de entrevista [1]

      Pregunta 1

      3 rounds DSA 2 rounds System Design 1 Behavioural
      Responder pregunta
      4

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

      Entrevista para Software Engineer

      1 de jun de 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

      Entrevista para Software Engineer

      28 de may de 2026
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      Standard cookie cutter interview with a coding interview, a system design interview and culture interview. The coding part is basically leetcode. The system design is what you can find on many youtube videos. The culture one is more tricky as they want to see that you fit Meta's culture, not that you were doing great at your existing company. So skills like dealing with conflict without calling in managers is sought after.

      Preguntas de entrevista [1]

      Pregunta 1

      coding: I forgot, sorry system design: design ticketmaster culture: talk about past project; when you disagreed with a peer; how I resolved dissagreements, etc.
      Responder pregunta

      Entrevista para Software Engineer

      28 de may de 2026
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Meta

      Entrevista

      The interview felt more straightforward than I anticipated for a well-known tech giant. After a recruiter screen, I faced a technical round that included a DSA question about finding the lowest common ancestor in a binary tree. I was pleasantly surprised when I realized the exact problem had popped up in the algorithm practice section on PracHub during my prep. Ultimately, the experience was decent, but I chose to decline the offer as it didn’t align with my current goals.

      Preguntas de entrevista [1]

      Pregunta 1

      Given a binary tree, find the lowest common ancestor of two given nodes in the tree.
      Responder pregunta

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

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      Google
      4.5★Remuneración y prestaciones
      avatar
      eBay
      4.0★Remuneración y prestaciones
      avatar
      Amazon Web Services
      3.9★Remuneración y prestaciones