Me postulé a través de una recomendación de un empleado. El proceso tomó 4 semanas. Acudí a una entrevista en Meta (Menlo Park, CA) en may 2012
Entrevista
I was contacted by recruiter via employee referral. Chose to go on site for initial interview. This was followed by onsite day of interviews a few weeks afterwards (I asked for some time to prepare for coding tests). The second set of interviews comprised of 2 coding tests, one design, one behavioral, lunch with hiring manager and one interview related to my technical specialization. Received offer within a week of final set of interviews.
Preguntas de entrevista [1]
Pregunta 1
Coding tests were the hardest part for me since I have been out of school for a long time now :) Prepare for questions related to trees, graphs, strings, dynamic programming and practice writing code on paper.
The entire process usually takes 3–8 weeks, depending on scheduling and the specific role. Coding interviews heavily emphasize common DSA topics such as arrays, strings, trees, graphs, BFS/DFS, heaps, hash maps, and dynamic programming. System design becomes increasingly important for E4+ positions.
Preguntas de entrevista [1]
Pregunta 1
Given an array of integers and a target value, return the indices of two numbers that add up to the target
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.
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.
