Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 semanas. Acudí a una entrevista en Meta en feb 2015
Entrevista
One phone screen and two technical phone interviews. The phone screen had some basic questions about networking and systems. The first technical interview was a basic text processing question suitable for any scripting language, and the second was more of a systems design question that tested technical depth and troubleshooting. There was no coding involved on the second interview.
Preguntas de entrevista [1]
Pregunta 1
Given a database with slow I/O, how can we improve it?
Acudí a una entrevista en Meta (California City, CA)
Entrevista
The interview experience at Meta is a structured and rigorous process designed to thoroughly assess both technical skills and cultural fit. It typically begins with a recruiter screening, followed by multiple rounds of technical interviews that focus on coding, system design, and problem-solving abilities.
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Meta (Menlo Park, CA) en abr 2025
Entrevista
Initially there is a recruiter screen describing the interview process and discussing my background, experience, and interest in the role at Meta. The rounds thereafter are to discover technical skills as it relates to troubleshooting and debugging, networking and coding skills.
Preguntas de entrevista [1]
Pregunta 1
Describe how I would identify and resolve an issue with a service you support is no longer responding to requests
Solicité el puesto a través de un captador. El proceso duró 3 meses. Acudí a una entrevista en Meta en nov 2024
Entrevista
After passing the initial 20 minute phone screen with HR I was setup for the next round - which was a screening interview split into two parts: 1) Two leetcode style coding questions in 45 minutes; 2) Completely verbal discussion focused on troubleshooting a new to you linux hosted website with known and new issues
Preguntas de entrevista [1]
Pregunta 1
Q1."what happens when you write in the web browser", then quite many follow ups on tcp/ip , tcp syn, and the whole process itself.
Q2.server side optimizations like load balancing, fault tolerance and so on.
