Preguntas frecuentes sobre las entrevistas de Meta
Los postulantes al puesto de Software Engineer calificaron el proceso de entrevista en employer] con una puntuación de 4 sobre 5 (donde 5 indica el máximo nivel de dificultad) y valoraron su experiencia en la entrevista como positiva en un 67%. En comparación, la valoración promedio de la empresa es positiva en un 74,2%. Estos datos corresponden a las calificaciones de los usuarios de Glassdoor.
La duración promedio del proceso de contratación de los candidatos que se postulan para cargos de Software Engineer es de 14 días, según las 3 entrevistas enviadas por los usuarios para este cargo. En comparación, la duración promedio del proceso de contratación en general en Meta es de 43 días.
Las etapas comunes del proceso de entrevista en Meta para el cargo de Software Engineer según 3 entrevistas en Glassdoor incluyen las siguientes:
Entrevista personal: 50%
Prueba de habilidades: 50%
Aquí tienes los cargos más buscados para informes de entrevistas -
Me postulé a través de un reclutador. El proceso tomó 2 meses. Acudí a una entrevista en Meta (Menlo Park, CA)
Entrevista
It took me 1 phone interview followed up with 2 onsite interview. First onsite interview has 5 interview sessions and second has 2 sessions.
The interview went good, and interviewers are nice. And I answered all the questions fluently and definitely sure that most of interviewers feel love to talk with me. Since two interviewers mentioned how would I expected for new hire camp and another one worked me to the patio on top of the building.
But the strange thing is that the recruiters get totally silent after that although I sent 3 emails out after last onsite interview until one day they called me when I was driving without notice after hour and said I was not selected. I asked for the reason and what part I can improve, and they just said there is no reason and everything is good, and team is impressed by me, and it is just a hard decision.
A week later I learned FB employee suicide event and it makes sense to me that why FB made the decision because they just has issues inside without let people know, and best luck for the software engineers in FB!
Spoke with interviewer over video conferencing. He was very communicative . He answered my questions. Asked me BFS question. A question that involved BFS search. Given a matrix, I am suppose to find a path from top left to down right.
Preguntas de entrevista [1]
Pregunta 1
A question that involved BFS search. Given a matrix, I am suppose to find a path from top left to down right.
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
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