Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso Meta (Kirkland, WA) nel mese di ago 2015
Colloquio
Asked a friend to refer me. Was contacted by a recruiter within two days. Quickly scheduled a tech-screen (essentially mini-ninja interview). After that came the on-site loop.
2 ninja, 2 pirate and 1 jedi interviews. Can't share specific questions, but plenty of other people did already. Unlike Google (interviewed with them also), Facebook seems to have a smaller question pool as one of the system design questions I got I've also seen on Glassdoor before.
I recommend going through the information recruiters provide for interview preparation. Since Google and Facebook use very similar processes, "Stevey's Blog Rants: Get that job at Google" post is also quite relevant and useful. Know your data-structures, algorithms, practice solving problems for a few weeks and you should be in good shape.
For system design questions, you will be asked to design Facebook-scale systems. Think data way beyond the scope of one machine, billions of items, thousands of requests per second. Hands on experience with such systems is of course "the king". In the absence of that - study distributed NoSQL systems, MapReduce and similar things and you should be in good shape.
Overall I was very happy with the on-site interviews and the level of support Facebook recruiters and engineers provided me. This was probably the best interview experience that I've had.
Having a competing offer handy will surely help you negotiate better compensation. Facebook seems to have an awesome culture. Deciding to reject their very generous offer for another one wasn't an easy call. One really can't go wrong by joining Facebook.
Facebook is the only company that I know that provides interview feedback. Regardless whether you pass or not I recommend asking for it as it will help you get better.
Domande di colloquio [1]
Domanda 1
Data-structures, sorting, Big-O notation, large system design.
Recruiter call was pretty standard, first round was 2 Meta tagged LC mediums in 45 minutes. On-site was 2 coding sessions of 2 LC mediums, a system design interview and a behavioral interview with an engineering manager.
Domande di colloquio [1]
Domanda 1
How do you answer if someone asks how long a deliverable or project will take?
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.
