Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Meta (Seattle, WA) nel mese di feb 2014
Colloquio
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.
Domande di colloquio [1]
Domanda 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.
Took about a month from start to finish, which felt longer than I expected. After a couple of initial phone screenings, I faced a challenging technical round focused on system design. It was during this round that I was asked to describe overcoming a major career challenge. Interestingly, I had just reviewed a similar framework on PracHub, which helped me articulate my thoughts clearly. Overall, I appreciated the depth of the process and ended up accepting the offer.
Domande di colloquio [1]
Domanda 1
Describe Overcoming a Major Challenge in Your Career
Ho sostenuto un colloquio presso Meta (Seattle, WA)
Colloquio
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.
Domande di colloquio [1]
Domanda 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.
Domande di colloquio [1]
Domanda 1
Given an array of strings, pick a subset whose concatenation contains no duplicate characters, and return the maximum possible length of that concatenation.
