Facebook Interview Questions & Reviews in Seattle, WA
Getting an Interview
- Popular Job Titles:
- Software Engineer (318)
- Software Engineer Intern (81)
- User Operations Analyst (45)
- Intern (37)
- Product Manager (30)
- Account Manager (21)
- Software Engineering Intern (18)
- Software Engineering New Grad (17)
- Data Scientist (15)
- Senior Software Engineer (15)
- Analyst (14)
- Production Engineer (14)
- Online Sales Operations (14)
- Engineering (11)
- Software Engineering (10)
- Software Developer (10)
- Marketing (9)
- Product Designer (7)
- Product Analyst (6)
- Product Specialist (5)
- Data Engineer (5)
- User Experience Researcher (5)
- Client Partner (5)
- Internet Marketing Analyst (5)
- Developer Support Engineer (4)
- Data Analyst (4)
- Operations Engineer (4)
- Human Resources (4)
- Recruiting Coordinator (4)
- Executive Assistant (4)
Software Engineer Interview (Negative Experience; Average Interview)
I applied online - interviewed at Facebook in April 2013.
Interview Details – A recruiter contacted me. After a few days of back and forth we set up a phone interview. In the phone interview we discussed a possible problem that involved trees. I struggled to implement the necessary algorithm.
Eventually, I got to ask a couple of questions about facebook.
Received a decline a couple weeks later.
Product Manager Interview (Positive Experience; Average Interview)
I applied through other source and the process took 2+ weeks - interviewed at Facebook in March 2014.
Interview Details – Great interview process, recruiters and interviewers. The recruiter does a prep session with you beforehand that is very handy. They basically want to ensure a candidate does his best. I didn't do well on the interviews, but this is entirely my fault (FB did a great job to help me prepare). I connected with a recruiter through linkedin, i had a phone screen with a recruiter and then was brought in for 1st round of onsite interview - 2 interviews (one on Product and one on Execution) in the Seattle office. I wasn't called back for the second round.
Interview Question – - Design a product to help people find apartments
- Investigate a Metric anomaly Answer Question
Software Engineering New Grad Interview (Negative Experience; Average Interview)
I applied online and the process took 4 months - interviewed at Facebook.
Interview Details – I initially applied in early November, 2013. I got a reply from one of the recruiters about a week later. After talking to the recruiter on the phone and emailing back and forth for a while, she realized that I was still in school (graduating mid 2014) and transferred me to another recruiter.. or rather a bunch of different recruiters who couldn't seem to figure out who I should be talking to. Eventually we got everything sorted out (now in January 2014) and I did two phone interviews. They both went well and shortly after, they arranged for me to fly to Seattle for a "university day". They put me up in a nice hotel across the street from the office and, of course, paid for meals and everything. They even set up direct deposit for the reimbursement, which was nice.
The day of the interviews, I arrived in the morning and signed in and then I was met by a couple recruiters. There were also a few intern candidates but no other full time candidates. I had 3 interviews that were all fairly interesting. The first one was mostly a fit interview, the second was the in depth coding interview and the third was a combination of talking about experience and doing some coding.
After the interviews, we did a tour of the office and then we met with a bunch of engineers for a Q&A session. This was a really great way to learn about the company and see how everything works there. It seemed like a really great place to work with lots of really smart engineers though I was mildly concerned about the apparent lack of organization.
In the afternoon, one of the recruiters took us downtown for Seattle's "Underground Tour" which was really neat and later they took us out to a super fancy Italian restaurant which was excellent. Overall, it was a really great day.
About a week later, I got an email from one of the recruiters asking for references and my transcript. I have an almost perfect transcript (straight A's) and I was certain that my references would say nice things about me so I felt that I had the job in the bag at this point. One of my references forwarded me the questionnaire they sent him. It was just generic questions like "How did you know him?", "Would you hire him again?", "What were his strongest/weakest attributes?" This reference included his answers which were all extremely positive, re-enforcing the idea in my mind that I was going to get an offer.
A week or so after this, I heard from the recruiter again asking me to do more phone interviews. Supposedly, it was "great news that [they] still [wanted] to move forward with [me]" but I didn't really take it that way. Frankly, I find it rude and unprofessional that they would waste the time of my references if they weren't already prepared to make an offer. However, I, of course, went through with the phone interviews, uncertain what they could possibly learn about me that they hadn't already figured out in the first five interviews.
The first of the second round of phone interviews (6th interview overall) went very poorly as the interviewer has a very strong accent and a horrible phone line (lots of static). I could barely understand what he was asking which made it very difficult. I contacted the recruiter about this and she seemed at least somewhat understanding. She then booked another phone interview which went quite well, as far as I could tell.
Finally, the week after this (now into March), I got a rejection letter which I was rather dumbfounded by. I can't for the life of me figure out where I went wrong or why they would bother contacting references if they weren't prepared to make an offer.
Interview Question – I signed an NDA so I'm not sure that I am allowed to talk about it. Mostly fairly general questions, e.g. data structures, algorithms. Sometimes there's an emphasis on large data. Answer Question
Software Engineer Interview (Neutral Experience; Difficult Interview)
I applied through a recruiter and the process took 4+ weeks - interviewed at Facebook in February 2014.
Interview Details – Was contacted by recruiter in LinkedIn and started interview process. He was transparent, prompt and supporting during the process. He updated me every on every step and details and he was prompt: getting feedback after 3 hours from phone interview speaks for itself. Then I had on-site interview, three interviewer liked my answers, system design really like my design and thinking, but apparently one of the interviewer didn't like my coding style and I was asked to come for one more interview just to check the coding part again. So tip: use whiteboard better, apparently working and clean code is not enough it needs to look clean on board as well :) Overall process was positive. But, I had a feeling that some interviewers are really un-experienced and focus on wrong things. Also big difference from other companies: they expect you to be really fast (read - you need to know answer upfront). If you don't know answer upfront, but come up with solution after thinking, trying, making misatkes and optimizing - it doesn't count, at least it didn't in my case. Try to solve my problem below (if you don't know answer already), implement, test it on board in 15-20 minutes.
Advice for FB: train your interviewers to focus on skills, NOT memorized skills.
I have offer from big companies/competitors, so I will just go with them.
Interview Question – Question is verbose, uses search engine, string matching etc., but at the end boils down to this: There is two dimensional array where each sub array (row) is sorted, i.e.
[[1 1000 2000]
[20 10001 5000]
[55 10002 222222]]
Find a minimum range contain a number from each row. For above array it should be (1000-1002) range. View Answers (4)
Software Engineer Intern Interview (Positive Experience; Difficult Interview)
I applied online and the process took 2 weeks - interviewed at Facebook in February 2014.
Interview Details – Originally applied as a Production Engineer Intern, but the recruiter thought I was a better fit for SE. Interview consisted of the usual personal question and a coding problem in collabedit. It's a twist on the classic palindrome question. After following up about 5 or 6 days later, I was rejected.
Interview Question – Check if two strings (including caps, whitespace, punctuation) are palindromes without doing any preprocessing. I wrote my code in Java. View Answer
Software Engineer Interview (Neutral Experience; Easy Interview)
I applied through a recruiter and the process took a day - interviewed at Facebook in February 2014.
Interview Details – After I talked through phone with recruiter, I got interview for coding question. The coding question is easy, just use recursion to solve it. But time is quite tight, I could not finish the code in time as I talked too much with the interviewers.
Administrative Assistant Interview (Positive Experience; Easy Interview)
I applied online - interviewed at Facebook in November 2013.
Interview Details – I saw the job online and I applied for it immediately. Within 2-3 2 days I received a call from Marc, the recruiter. He was very nice and professional. Asked me questions about my work experience and background. Said that he was drawn to my resume based on my length of service with my employer and achievements. He explained that it was a 3 step process, first with him, then the team members, then finally the director that would be supported by the new AA. Marc decided during our call that he wanted to move me to step 2, the interview with the staff. Within a week I was contacted and had a 1:1 interviews with the office manager, and the 2 admin assistants. They were courteous and very professional and asked basic questions. The interview wasn't intimidating or threatening and I was relaxed and comfortable from the start. Beautiful offices with a breathtaking view of the Emerald City! This was probably one of the best interviews I ever had.
Interview Question – None of the questions were difficult. Answer Question
Software Developer Interview (Negative Experience; Easy Interview)
I applied online and interviewed at Facebook.
Interview Details – Applied online, was contacted by a recruiter. Had one phone screen then was asked to come in for a full loop at the Seattle campus.
The culture is unusual for a tech company. It is both good and not so great. The interview was amateur grade. All of the people who interviewed me, except one, had significantly less experience than I did. It's not an ego issue. In most cases, they had a little more than 1 year of experience. The problem with someone like that interviewing you is that they might not know of a good way to do it. For example, I was constantly interrupted. I let them know that I was thinking out loud and that everything I say might not be the best way to do something. When I have something concrete I'll set it forward and we can discuss that. That didn't stop the interruptions. I'd lose my train of thought and would have to start again. Again, while writing code, the same thing. I said that the code isn't optimized, i'll optimize it later. I'm trying to get it right, then tweak it later. Every few lines, I was asked if something was necessary.
I was pretty frustrated by the end. I wish I could tell them that you're interviewing me- meaning you want to see how I think, check my problem solving ability and NOT show how much you know. You're probably good at what you do, else you wouldn't have been there. Can we please focus on me solving the problem?
In other interviews, at other companies, I've noticed the more experience a person has the more patient and observant they are during an interview. They will ask questions and prod, but almost never interrupt unless you're heading down a seriously questionable line of thinking path.
Interview Question – Questions were quite straight forward. It wasn't a difficult interview. Just... good luck getting good interviewers. Answer Question
Software Engineer Interview (Positive Experience; Difficult Interview)
I applied through an employee referral and the process took 3 weeks - interviewed at Facebook in October 2013.
Interview Details – Started with a friendly talk with the recruiter, had 1 phone screen and then 4 on-site interviews. Everyone I talked to (including the recruiter!) was very Smart, friendly and engaging. I definitely felt a commitment to their role - even as interviewers!
There was nothing unexpected on the interviews, so don't be afraid about the horror stories out there. If you're good you should do OK.
Interview Question – Nothing unexpected. Keep Reading, studying, solving problems, and coding on your daily job and you should be able to get it. Answer Question
Negotiation Details – There was not much room for negotiation. The offer was a lot higher than my current salary+equity at a top-notch software company.
Software Engineer Interview (Positive Experience; Average Interview)
I applied through an employee referral and the process took 2+ months - interviewed at Facebook in July 2012.
Interview Details – I had a great feeling of solid communication with recruiters. The recruiters kept me accurately informed about interview progress. In order to establish an appropriate level of compensation, they seek information about my current employment without being invasive. I have felt interview process can be described by integrity and maturity, making Facebook a great place to work.
This is in stark difference with my experience I have interviewing for other companies (namely Google) where after I passed the technical interviews, the recruiters pushed for very detailed compensation information, even though they in the end failed to provide an offer, missing deadlines in communication causing me to miss a competitive exploding offer.
Interview Question – What would be the most interesting job description ?
Design end 2 end, Facebook's messaging infrastructure . Answer Question