Candidatei-me de outra forma. O processo levou 2 semanas. Fui entrevistado pela Meta (Menlo Park, CA) em mar. de 2012
Entrevista
A short initial phone chat with the recruiter (Who was excellent, even offering tips for the main interview) and then a technical phone interview with a developer.
The developer I spoke to was great, seemed like a nice guy and managed to pose some tough technical questions without seeming combative.
They got back to me within a couple of days to let me know they wouldn't be taking it further.
Perguntas de entrevista [1]
Pergunta 1
Worked through a few coding questions using a shared document, getting progressively more complicated and then went through a sort of thought exercise regarding the limits of the proposed solution in terms of constraints like bandwidth, CPU speed, memory and how performance could be improved without re-writing the basic algorithm.
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.
Perguntas de entrevista [1]
Pergunta 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.
Perguntas de entrevista [1]
Pergunta 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.
Perguntas de entrevista [1]
Pergunta 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.
