Preguntas frecuentes sobre las entrevistas de Meta
Los candidatos al puesto de Software Engineer han valorado el proceso de entrevista en employer] con una puntuación de 4 sobre 5 (donde 5 indica el máximo nivel de dificultad) y han valorado su experiencia en la entrevista como positiva en un 100 %. En comparación, la valoración media de la empresa es positiva en un 58,1 %. Estos datos corresponden a las valoraciones de los usuarios de Glassdoor.
La duración media del proceso de contratación de los candidatos que solicitan puestos de Software Engineer es de 14 días, según las 1 entrevistas enviadas por los usuarios para este puesto. En comparación, la duración media del proceso de contratación en general en Meta es de 37 días.
Entre las etapas habituales del proceso de entrevista en Meta para el puesto de Software Engineer según 1 entrevistas en Glassdoor se incluyen las siguientes:
Entrevista en grupo: 20 %
Prueba de personalidad: 20 %
Entrevista personal: 20 %
Prueba de aptitud: 20 %
Presentación: 20 %
Aquí tienes los puestos más buscados para informes de entrevistas -
Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Meta
Entrevista
Facebook reached out to me via email to gauge my interest in a position on a SW Engineering position in Menlo Park. I replied positively, and spoke to a kind recruiter who described the role to me. I continued to be interested, so I scheduled a technical phone screen with an engineer thru the recruiter. I was also then referred to work on this team via a developer who currently worked on it, and that's how I submitted my formal application.
The recruiter sent me an email containing several resources including a link to LeetCode ("focus on the 'medium' to 'hard' problems) and two videos, each longer than an hour. The email also contained information beyond the initial technical interview process. I was then sent an email containing information about who I'd be interviewing with and when.
The call came. The pre-interview resources, for being so detailed, felt like a waste of time with respect to this initial phone screen. My introduction felt completely unimportant. As one may expect, we spent a majority of the time on the programming challenge questions.
If you do not absolutely nail these questions, the follow-up optimization questions, and the big-O-notation questions, Facebook will decide not to move forward with your application.
I received no feedback during or after the review regarding what the interviewer was expecting from me, or what they thought of my answers to the questions. My previous employment experience was completely irrelevant. The programming questions I was asked were not relevant to the role for which I was applying.
The time between Facebook reaching out to me and the no-go call from them was one month.
4
Otras opiniones sobre las entrevistas para el puesto de Software Engineer en Meta
The process is straightforward and designed to help us get to know each other. It moves through a few stages at a comfortable pace, involves conversations with several team members, and focuses on making sure it's a good mutual fit.
Solicité el puesto a través de un captador. Acudí a una entrevista en Meta
Entrevista
Had an initial recuriter call and then scheduled a coding round with 2 leetcode questions. Practicing Meta-tagged leetcode questions would help prepare for this round. Interviewers expect clear communication and code.
Acudí a una entrevista en Meta (Londres, Inglaterra)
Entrevista
Generic LeetCode-style questions, many tagged as Meta, so extensive preparation is required to perform well in the technical interview. The experience varies significantly - some interviewers provide hints and guidance, while others expect candidates to solve problems independently with minimal assistance.