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:
Presentación: 20 %
Prueba de aptitud: 20 %
Entrevista personal: 20 %
Prueba de personalidad: 20 %
Entrevista en grupo: 20 %
Aquí tienes los puestos más buscados para informes de entrevistas -
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 3 meses. Acudí a una entrevista en Meta (New York, NY) en sept 2019
Entrevista
I was approached by a recruiter, but she didn't get back to my reply. I later went through employee referral.
I had one phone interview and (although I believed I was good), the interviewer was not confident in advancing me to the next round. I had another follow up phone interview and then advanced to the on site interviews. The results of the on site interviews had some mixed signals in the coding section and I went for a follow up on site coding interview. I received the feedback in one week after the final interview.
My recruiter was very open and communicated every step clearly. I was amazed by how he skillfully managed my process and was ready to help. The whole process was very smooth and I had a very good experience talking to the interviewers and the rest of the team.
Preguntas de entrevista [1]
Pregunta 1
The coding questions are on average mid level questions. They are not tricky and they are fairly straightforward. Yet, it seems important that you need to solve the coding questions completely to the end, find the optimal solution and cover all the edge cases carefully. For my case, I solved two coding questions in each of the 45 minute coding interviews. The behavioral, system design and machine learning questions were straightforward and manageable.
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
Envié una solicitud electrónica. 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