Getting an Interview
Getting an Interview
Interviews for Top Jobs at Facebook
- Software Engineer (460)
- Software Engineer Intern (80)
- Intern (55)
- User Operations Analyst (47)
- Product Manager (40)
- Software Engineering (31)
- Account Manager (27)
- Data Scientist (27)
- Production Engineer (26)
- Software Engineering New Grad (26)
- Product Designer (19)
- Senior Software Engineer (18)
- Software Engineering Intern (17)
- Online Sales Operations (15)
- Analyst (15)
- Software Developer (14)
- Front End Engineer (11)
- Engineering (11)
- Marketing (9)
- Data Engineer (8)
- Product Analyst (8)
- Product Specialist (7)
- Client Partner (7)
- Android Developer (6)
- Internet Marketing Analyst (5)
- Technical Program Manager (5)
- User Experience Researcher (5)
- Recruiter (5)
- Recruiting Coordinator (5)
- Engineer (5)
Helpful (38)No OfferPositive ExperienceEasy InterviewNo OfferPositive ExperienceEasy Interview
I applied through college or university – interviewed at Facebook (Menlo Park, CA).
This is for undergrad full-time software candidates in USA. Submitted resume at college career fair. Got email about on-campus interviews. At this stage, there are 3 possible outcomes: onsite invitation, a phone interview for an additional chance, or reject. I was invited to onsite interview.
Onsite was a "University Day" that included three interviews (not four like they said in the email) before lunch and then a tour, new-hire panel, etc after lunch.
All interviews were 45-mins length.
On-campus interview: 3 coding questions. I don't remember signing any NDA at this point so, the questions were k-Nearest Points to Origin, finding a substring, and 3-sum.
On-site interview: 3 interviews, 45 mins each. 1st interview: 2 coding questions. 2nd interview: behavioral questions (about team conflict, etc.) and a coding question. 3rd interview: 2 coding questions. Coding questions were easy and required *no knowledge* of special algorithms or data structures (such as graphs, DP, trees, etc). Recursion and strings were common.
I did not get an offer from Facebook; however, I received offers from other companies. The interview questions themselves were considerably easier at Facebook than those asked at Google, LinkedIn, MS, Amazon, etc.
Since the questions are not very hard, my guess is the decision is based upon fit and most importantly how *quickly* you were able to arrive at your solution and how *perfect* your code was. Make sure you focus and are confident.
Advice: practice the easier questions and practice coding them. Also, looking at some of the other experiences on Glassdoor, it looks like a majority of the questions are re-used.
- Just prepare for some common behavioral questions. Answer Question
I applied online – interviewed at Facebook.
applied online. Contected by recruiter for initial screening in facebook office. When to local fb office, where I waited for few minutes after getting to reception. First, recruiter gave tour of center and talked about perks and then took me to conference room, where I met interviewer whole first discussed about my past projects and then jumped on coding question.
- Multiply two big ints. Answer Question
I applied through an employee referral. The process took 2 weeks – interviewed at Facebook.
Referred by school mate and got the phone interview. Failed in the first round interview. No questions on resume. Just two coding questions. First one is easy. I just said minHeap solution, then the recruiter directly said next. I was stuck at the second problem and that is the reason why I failed.
- 1. Given 1 billion numbers, find 100 largest numbers
2. Prefix notation +*123 = 5 Answer Question
- 1. Given 1 billion numbers, find 100 largest numbers
- No OfferNeutral ExperienceEasy InterviewNo OfferNeutral ExperienceEasy Interview
I applied through an employee referral – interviewed at Facebook.
I applied through employee referral. I got an email from a recruiter with a questionnaire asking about my experience, why facebook, etc. Next step was a phone interview. The interviewer was very nice and helpful. The interview question was not difficult. I gave an optimal solution with some help, also finished coding in time. I don't know what they don't like about the interview, but probably I was not very fast coding and testing the code. I got an email after a few hours that they do not want to move forward.
- Problem related to binary search tree. Answer Question
Helpful (1)No OfferPositive ExperienceAverage InterviewNo OfferPositive ExperienceAverage Interview
I applied online. The process took 2 weeks – interviewed at Facebook (Menlo Park, CA).
I applied online through their website. I was contacted after one week and scheduled an interview for the following week. They flew me out and although the interview only lasted 4 hours, I was in California for the weekend. Great experience. Wonderful company. Although I did not get an offer, I will definitely apply again.
- Lots of behavioural questions Answer Question
I applied through a recruiter. The process took a week – interviewed at Facebook (Seattle, WA).
Onsite tech screen followed by 4 1:1 rounds. Three of the technical rounds were on coding questions and one of them had a design problem. Most of the technical problems were easy but I didn't code well probably because I didn't take enough time to practice whiteboard coding. The design round had an interesting problem. I'll probably appear in this once more in a year. All interviewers were good and well-behaved. The process was smooth as well. The recruiter communicated my area of weakness (coding) and I concur with what they found.
- Convert a tree to a doubly linked list. Answer Question
- No OfferNeutral ExperienceAverage InterviewNo OfferNeutral ExperienceAverage Interview
I applied through college or university. The process took 3 days – interviewed at Facebook in April 2015.
I first had a portfolio review at a school portfolio review event then got emails for a next rounds of interviews. Had to pick 1 or 2 projects and share with them in details. Asked me how I would further develop some projects and asked about thinking process as well.
- how would you develop this further Answer Question
- No OfferPositive ExperienceAverage InterviewNo OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 2+ weeks – interviewed at Facebook (Menlo Park, CA) in April 2015.
They recruited me at a conference. I had a recruiter phone screen followed by two engineering phone screens. One was focused on coding and the other on systems. This was followed by an all-day interview at the Facebook Campus. The all-day interview was 5 sessions with different engineers, 45 minutes each. Each interview focused on a different area like Architecture, Coding, Networking, and Systems.
- How would you design Facebook? Answer Question
I applied through an employee referral. The process took 3 weeks – interviewed at Facebook.
My friend referred me, and then a recruiter contacted me after several days. A phone screen interview was scheduled two weeks later. About 1 week, the recruiter told me I didn't pass the interview.
- write a algorithm to calculate the running time for a sequence of tasks. Answer Question
I applied through an employee referral. The process took 1+ week – interviewed at Facebook (West Seattle, WA) in April 2015.
I went campus career fair and give the resume. I wait one month and got nothing. So I changed to ask for reference and got a interview after one week.
- build a large number structure with add function 2 Answers
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review