Facebook Interview Questions in San Francisco, CA

Updated Aug 31, 2015
211 Interview Reviews

Interview Experience

Interview Experience

61%
18%
19%

Getting an Interview

Getting an Interview

22%
19%
19%
3
1
0
0

Interview Difficulty

3.4
Average

Interview Difficulty

Hard

Average

Easy

211 Candidate Interview Reviews Back to all Interviews

Sort: Popular Date Difficulty
  1.  

    Sourcer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through an employee referral. The process took a week. I interviewed at Facebook (Menlo Park, CA).

    Interview

    Good group of interviewers- easy to speak with and informative. Quick response times which made for a painless experience :) Enjoyed meeting the team and being shown around their space. Hope to touch-base again in future.

    Interview Questions

  2. Helpful (4)  

    User Experience Researcher Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through other source. The process took 2+ months. I interviewed at Facebook (Menlo Park, CA).

    Interview

    I met some researchers at a conference. From there I had a phone interview with a recruiter and then a screening with a market researcher. They flew me in to the campus for a day of four interviews and a presentation. The presentation topic was fairly open so that I could put my own spin on it. The interviews were very case-based and hypothetical. The recruiter was very prompt throughout the two-month process in getting back to me after each step was completed.

    Interview Questions

    • Name one feature/component of the Facebook interface that a competitor does better. Why?   Answer Question
  3. Helpful (3)  

    Human Resources Role Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied online. I interviewed at Facebook (Menlo Park, CA).

    Interview

    Process moved fairly quick; 1 week or so. Recruiter reached out via email and we set up a call interview to discuss the role and my background within a couple of days. I was then referred to the hiring manager. The conversation with the hiring manager was great; simple questions about experience. However, I never heard back from the recruiter on status updates. I had to follow up a couple of times via email. I finally heard back, and they decided to move forward with another candidate. FB appears to be growing a lot, thus many more roles within HR opened up. I reached out the recruiter via email to discuss potential roles. I was over-qualified for some and others I had the sufficient experience. I never heard back. After a week or so, recruiter responded stating that they are moving forward with other candidates. I recently had interest for another role, and I received feedback that according to the same recruiter, they had an internal fit for it. This was an interesting experience, and it is unfortunate that the recruiter did not take the proper time to explore a potential candidate with professional, valuable conversations. A simple conversation to better understand their needs and how my background would fit, would have made sense. At times, I wonder if these recruiters should be required to have more experience, given the excellent pool of candidates out in Silicon Valley?! You just never know who you may be putting to the side. It appears as if the process is put at a "stop" based on the recruiters bias towards a candidate they have never met before or never personally worked with. It is a loss for FB if the candidate could have been one to make a huge positive impact (who would know?) I was left with a sour taste of their culture, and that is unfortunate.

    Interview Questions

  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5. Helpful (13)  

    Software Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a staffing agency. The process took 5 days. I interviewed at Facebook (Menlo Park, CA) in May 2015.

    Interview

    Phone Screen 45 min duration in total, the interviewer said a little bit about himself and went straight to a technical question. No background questions. The interview process went as expected, no surprises. The interviewer seemed to be a nice guy.

    Interview Questions

    • Given a sequence of numbers (34128) and an input map such as a dial pad on a phone (2->[a,b,c], 3->[d,e,f], 4->[g,h,i]) write an algorithm to return all possible words from the sequence. E.g. Input: 232 Output: [ada, adb, adc, aea, aeb, aec, afa, afb, afc, bda, bdb, bdc, bea, beb, bec, bfa, bfb, bfc, cda, cdb, cdc, cea, ceb, cec, cfa, cfb, cfc]   10 Answers
  6. Helpful (3)  

    Software Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Neutral Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 3 weeks. I interviewed at Facebook (Menlo Park, CA) in June 2015.

    Interview

    I started off with a standard technical phone screen with a Facebook engineer. It was a simple coding exercise with two questions of surprisingly low difficulty. I cleared this easily. Facebook's on-site interview process is far more rigorous, though. Each 45-min interview has a clearly defined role, intended to test you from multiple different angles. Specifically, I went through: - 2 "Ninja" interviews (coding & algorithms) - 2 "Pirate" interviews (system design) - 1 "Jedi" interview (behavioral & simple coding) plus lunch with a Facebook engineer. The "Ninja" and "Jedi" interviews were straightforward. I hadn't seen the coding questions before, but they were not particularly hard. I would rate them as being of just average difficulty, pretty similar to the whiteboard coding questions asked at most other major Silicon Valley tech companies. And the behavioral section of the "Jedi" interview was just a friendly chat about my resume and my past experiences. However, the "Pirate" interviews were what killed me. Both "Pirate" interviews involved being asked to propose and discuss a design for existing features on Facebook. The interviewers were extremely meticulous and questioned me on virtually every last detail of my design decisions. In particular, they focused a lot on how huge datasets should be stored and accessed to support extremely large-scale distributed systems. Even though I am already working on web-scale systems in my current job, I was nonetheless still way under-prepared for this level of technical challenge and scrutiny. My advice to all prospective candidates is to spend most of your time preparing for the "Pirate" interviews. The coding questions aren't hard, but the system design questions will likely stretch you to your limit! (Unless you're a fresh grad--they don't ask "Pirate" questions to fresh grads. Lucky folks!) Additional side note: interestingly, my Facebook recruiter actually gave me detailed post-mortem feedback on each and every one of my interviews. They are the only major Silicon Valley company I know that does this, so major kudos to them for being so considerate.

    Interview Questions

    • Can't disclose due to NDA. But as mentioned above, the coding questions are really straightforward and of merely average difficulty. It's the system design ("Pirate") questions that can be really, really challenging. Definitely spend a good portion of your time preparing for the latter!   Answer Question
  7. Helpful (2)  

    Software Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a recruiter. The process took a week. I interviewed at Facebook (Menlo Park, CA) in June 2015.

    Interview

    Recruiter contacted me on Linkedin. I requested for in person interview in place of telephonic. Arranged a 1 hour interview at Menlo park office. Cleared the interview and was called for a six round interview. Interview was strange. Easy and not so complex algorithmic rounds. Not sure what is so special about those rounds or whether they were even part of the decision making. Interviewers were happy with the answers and not much corrections. Then there were these design rounds. One of the rounds was about designing location services. The interviewer was very knowledgeable. Pointed out my in-efficiencies with the choice of data-structure. Enjoyed it. Then started the real fun in the final round. An awesome interviewer with an awesome attitude. He spoiled my interview experience though. Asked me to design a messaging app system. Once the interviewer breaks the comfort zone, it would be a difficult place to stand. His expressions were horrible and sometimes I felt like saying "shut-up and listen first" which I didn't say obviously. When I mentioned that the server knows the ip address of client only when the server receives a packet from client. He said, there are a lot other ways it happens. I mentioned the only way is clients packet to the server. He made it an argument and finally I had to ask him to mention a way. He skipped the part and asked me to move on :-D Ignoring the final round, I actually enjoyed the interview process. No offer though :-)

  8. Helpful (11)  

    Software Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through an employee referral. The process took 2 weeks. I interviewed at Facebook (Menlo Park, CA) in May 2015.

    Interview

    First, there was a phone screen with the recruiter, a technical screen (either phone or on site, candidate's choice), and an on site. The recruiter was very professional and helpful, describing the process and the engineering culture at Facebook. They were very flexible in scheduling both the phone screen and onsite. The phone screen was a standard technical phone screen, with the difficulty dialed up slightly. The solutions allowed were constrained (typically, constant space). After I presented my solution, we discussed its complexity. The on site was very similar. The interview was very CS heavy. The questions asked relied on the knowledge of the properties of many data structures, including ones that are less often used. I can't recall any technical trivia questions being asked; all the questions surrounded a problem with an implementation that had to be coded on the white board. Parallelism and threads were also covered. I gave my answers in Python, and except for one interviewer that asked for a solution using Java, all accommodated. There was one design and architecture review which as different and a lot of fun. I was asked to design a system for a current feature of Facebook. The interviewers were great to interact with. I had a couple offers that were exploding, and they said they would be able to get a decision back quick. But there was an offsite, so the decision was delayed a few days. I withdrew when I accepted another offer. To put it in context, my other offers were exploding within 72 hours of the on site, so it was a tall order and it's to their credit that they tried. I left very impressed. When I'm looking for a position in the future, I'll definitely check them out.

  9. Helpful (1)  

    Software Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through a recruiter. The process took 4+ months. I interviewed at Facebook (Menlo Park, CA) in June 2015.

    Interview

    Took multiple months as I was not available. The recruiter did an excellent job in making sure that I take the interview. The interview took 45 mins and started with details about my previous work experience. That took about 20 mins and then I was left with 20 mins for the programming question. He gave me a problem related to BST. Obviously I need to draw the tree etc and he cannot see that on phone interview. I started with multiple approaches and he told specifically what I need to do eg. give only recursive solution, you can only store few things no extra space. In the end i was able to solve with a minor hint and he was also telling me to fix bugs as I was coding as well indent code as per his standards. Overall it was a good experience but I did not get the offer as they are looking for people who can code in like 10 mins as I was able to code in 15-20 mins. They want bug free code and will only go forward with the best candidate. I think even if you do a minor mistake you are out as there is someone else who will solve it perfectly so try to solve it perfectly :) Another important lesson is if you get option of phone v/s in person interview, I will say go for in person interview as it gives the interviewer the chance to see what you are doing on paper verses imagining that over phone.

    Interview Questions

    • serialize and serialize a BST   1 Answer
  10. Helpful (1)  

    IOS Developer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through a recruiter. I interviewed at Facebook (Menlo Park, CA) in June 2015.

    Interview

    Similar to some others, I first got a LinkedIn message from a Facebook HR staff based in India. We scheduled the first phone interview, which is a simple quiz with 5 multiple choice questions, conducted by the HR staff. Afterwards, I had the 2nd and 3rd interview with Facebook iOS engineers, different people but the format is pretty much the same. Each is about 45 min to 1 hour, asked me to do live coding on coderpad.io. I progressed and Facebook flied me from Sydney to Silicon Valley for a face to face interview. It's from 10am-3pm. Touched on many areas including behavioural questions, iOS app architecture, write code on whiteboard, time and space complexity, etc. I did not get an offer in the end but very impressed by the process.

    Interview Questions

    • Given a number e.g. 234, print all combinations of their dial pad letters e.g. "adg", "adh", "adi", "aeg", "aeh", "aei"...   Answer Question
  11.  

    Performance and Capacity Engineer Interview

    Anonymous Employee in Menlo Park, CA
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied online. The process took 3+ months. I interviewed at Facebook (Menlo Park, CA) in June 2015.

    Interview

    I applied online, and within a few weeks a recruiter followed up with me to do an initial screen. After the screening, I had a phone interview with a team lead for the performance and capacity engineering group. After that phone call, they decided to fly me out to Menlo Park for a full day of interviews. I met with 6 people at Facebook's main campus. Each interview was about 45 minutes and had a different focus: - Coding interview, where the goal is to come up with a solution as fast as possible (on a whiteboard). - System design. - Probability and statistics. - Culture fit. Everyone I met was very pleasant and friendly, and the recruiters were quite helpful throughout the process, almost acting as a sort of coach. Less than a week after the on-site interview, the recruiter contacted me to tell me they would be moving forward with other candidates. When I asked for feedback, I was told I didn't perform well enough on the coding exercise (though I did solve both problems, but perhaps I wasn't fast enough?).

    Interview Questions

    • Given a sorted set of numbers, find the first sequence of numbers that add up to a specified value.   Answer Question
Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.