Solicité el puesto a través de un captador. El proceso duró 1 día. Acudí a una entrevista en Meta en jun 2013
Entrevista
I was contacted by a recruiter via telephone. The phone conversation was simple enough to warrant a trip to the office. The office was nice- catered food, and unlimited soda and candies. The first round interview lasts about 1 hour and consists of questions (no surprise) asking about time complexities calculation and data structures. Make sure you at LEAST know tree traversals before you go into the interview. Given the short time limit, feel free to ask your interviewer for help to speed up your answering.
Preguntas de entrevista [1]
Pregunta 1
Questions were purely academic, nothing unexpected.
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.
