J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Meta (Seattle, WA) en févr. 2014
Entretien
Was contacted by recruiter in LinkedIn and started interview process. He was transparent, prompt and supporting during the process. He updated me every on every step and details and he was prompt: getting feedback after 3 hours from phone interview speaks for itself. Then I had on-site interview, three interviewer liked my answers, system design really like my design and thinking, but apparently one of the interviewer didn't like my coding style and I was asked to come for one more interview just to check the coding part again. So tip: use whiteboard better, apparently working and clean code is not enough it needs to look clean on board as well :) Overall process was positive. But, I had a feeling that some interviewers are really un-experienced and focus on wrong things. Also big difference from other companies: they expect you to be really fast (read - you need to know answer upfront). If you don't know answer upfront, but come up with solution after thinking, trying, making misatkes and optimizing - it doesn't count, at least it didn't in my case. Try to solve my problem below (if you don't know answer already), implement, test it on board in 15-20 minutes.
Advice for FB: train your interviewers to focus on skills, NOT memorized skills.
I have offer from big companies/competitors, so I will just go with them.
Questions d'entretien [1]
Question 1
Question is verbose, uses search engine, string matching etc., but at the end boils down to this: There is two dimensional array where each sub array (row) is sorted, i.e.
[[1 1000 2000]
[20 10001 5000]
[55 10002 222222]]
Find a minimum range contain a number from each row. For above array it should be (1000-1002) range.
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.