I applied through an employee referral. The process took 2 weeks. I interviewed at Meta (Palo Alto, CA) in Feb 2015
Interview
The process took about 2 weeks. Referred by a friend. The interview questions are not hard. I had only phone interview. Firstly, we spoke about my background and my projects. After that I had one coding task - the similar of LeetCode. I managed with it, but not optimal way. And after hint from interviewer I resolved it correctly.
I had a positive experience from the interview. But my English level is not high and my explanation was awful.
Interview questions [1]
Question 1
Given a huge file about several terabytes. File contains different words. You should remove duplicate from file.
Thanks for sharing your feedback. We're glad to hear that your interview experience was positive. Please stay connected with us through our talent communities! Facebook Careers on facebook.com/facebookcareers/ and on Instagram @facebooklife
I applied through a recruiter. The process took 4 weeks. I interviewed at Meta (Menlo Park, CA) in Apr 2016
Interview
My conversation with Facebook started when recruiter send me an email, we scheduled a call where she asked about my interests and background. Surprisingly recruiter asked me a technical question, it was not hard (Fibonacci function and its optimizations), but it was unexpected. Anyway I answered her question in details (bottom up solution, top down, DP) and she replied that it's exactly what she expected to hear.
Since I'm local to Bay Area I had an opportunity to have 1:1 onsite screen instead of phone screen. I choose that option and we arranged the interview in a week. Onsite screen was good, the interviewer was very nice and friendly, he was very helpful during the interview and there was an impression that we wanted to see my process of thinking. Eventually I solved the problem that was average difficulty. I started with brute force and then optimized it. In 2 days I got a call from the recruiter, she told I did well and we scheduled onsite interview.
There were 5 interview for onsite: whiteboard programming -> whiteboard programming -> resume discussion with coding -> architecture discussion -> whiteboard programming. The problems were average difficulty. I was kind of slow on the first and last coding, I think it was expected to solve a couple of problems instead of one. All interviewers were very friendly and helpful, at the end all of them shared that I solved the problem correctly and in an efficient way and that it was OK that we solved only one problem.
I already wanted to say that regardless the result my experience was positive, but after the interview I got a pretty bad experience. I didn't have any response or feedback for 2 weeks after the interview. I expected the rejection, but the silence in the first week gave me some hope that they are thinking about me (I was slow on the interview, but I didn't fail it completely). After the first week of silence I tried to contact me recruiter and eventually I figured out that she left Facebook and didn't move my case to anyone. I tried to contact Facebook careers page on Facebook, but it was helpless, they didn't reply to me. So, I found coordinators email (who scheduled my interview) and she finally shared the decision with me.
Interview questions [1]
Question 1
I used leetcode and hackerrank for preparation, but some interview questions were new for me. 3SUM, Intervals intersection, palindrome, BST to linked list conversion.
I would recommend to solve as much questions as you can, any slowness in your thinking is not welcomed.
I applied through a recruiter. The process took 3 weeks. I interviewed at Meta (San Francisco, CA) in Mar 2016
Interview
Contacted by a recruiter and an online screening of an algo problem. The whole process was very positive and everyone was very professional.
The technical questions were easy and the interviewer extremely helpful.
On the first call they tell you about the company in general and some of the benefits, they also explain the whole process of the interview (generally 3 steps).
Then the technical interview is on a shared text editor.