I applied through college or university. The process took 2 weeks. I interviewed at Meta (Menlo Park, CA) in Oct 2015
Interview
The process was very nice. I met with an engineer at my school's career fair and handed them my resume. After two days, I got an email from a recruiter telling me that they wanted to set me up with an interview on my campus. They also invited me to a dinner with the other students that they got in touch with, which was nice. The interview at my school was a 45-minute interview where they asked me one technical question. It went well and the interviewer was very nice.
After that interview, I heard back within two days that they wanted to move forward. I was then able to schedule an interview on-site at their office in Menlo Park. When it was time, they flew me out to Menlo Park for Facebook University Day. I had one 45-minute interview in the morning, followed by a full day of getting to see what Facebook had to offer, including a tour of the office.
The on-site interview was the final stage of the process for interns. They sent me their final decision within a week.
Interview questions [1]
Question 1
Given an array of integers, determine if there are 3 numbers in the array that sum to zero. It is also valid to use one number in the array more than once, they don't all have to be unique. Time complexity is important.
I applied through college or university. I interviewed at Meta
Interview
I had an on-campus interview and had to answer 2 questions in 45 minutes. The second problem was much shorter than the first one. I spent about 35 minutes on the first, and 10 minutes on the second.
Interview questions [1]
Question 1
Questions about real world practical applications.
I applied through a recruiter. The process took 2 months. I interviewed at Meta in Sep 2015
Interview
The interviewer briefly introduced himself in terms of when he has joined the company and what project he has (lately) worked on.
Then I was required to solve a coding task.
I'd say the task was rather simple, and what the interviewer was looking for was:
-- ability to quickly grasp the task at hand
-- ability to quickly come up with idea how to (efficiently enough) solve it
-- ability to quickly and correctly turn your idea into working code.
Suggestion: once you're done coding -- go through your code, check how it will handle the corner cases, reason out loud about what you're doing. Don't panic :)
Than, at the end you are given the opportunity to ask questions.
As you can expect, they'd like to see you show genuine interest in how things are done there, so showing some excitement helps a lot.
Interview questions [1]
Question 1
Questions I've been asked:
Do you think what you just coded is correct?
Show me (reason) how your code will behave on <this-particular-input>
What is the time/space complexity of what your solution?
Can we do better than that? Are you sure we can't?