J'ai postulé via la recommandation d'un employé. Le processus a pris 1 semaine. J'ai passé un entretien chez Meta (Menlo Park, CA) en mars 2012
Entretien
Got the interview referred by an employee. The interview process was very impersonal, with canned e-mail responses and literally no connection between the recruiter and the applicant. The recruiter persistently ignored my questions regarding team assignments. Had only one interview, with the "collaborative" coding question asked within the first 15 seconds of picking up the phone. Poor English skills of the interviewer and unwillingness to provide any hints were extremely unexpected. Despite providing the complete theoretical solution to the problem, the interviewer toyed with me not finding a small mistake in the code. After "deciding to move forward with other candidates" the recruiter declined to provide any feedback on the application. Undeniably it's a great place to work, but the recruiting process left a bad taste in my mouth.
Questions d'entretien [1]
Question 1
Question selected from the ones already provided. Revise your data structures and their implementation in your language of choice.
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.
Questions d'entretien [1]
Question 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.
Questions d'entretien [1]
Question 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.
The interview felt more straightforward than I anticipated for a well-known tech giant. After a recruiter screen, I faced a technical round that included a DSA question about finding the lowest common ancestor in a binary tree. I was pleasantly surprised when I realized the exact problem had popped up in the algorithm practice section on PracHub during my prep. Ultimately, the experience was decent, but I chose to decline the offer as it didn’t align with my current goals.
Questions d'entretien [1]
Question 1
Given a binary tree, find the lowest common ancestor of two given nodes in the tree.