Software Engineer applicants have rated the interview process at Meta with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 58.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 37 days.
Common stages of the interview process at Meta as a Software Engineer according to 1 Glassdoor interviews include:
One on one interview: 20%
Personality test: 20%
Skills test: 20%
Presentation: 20%
Group panel interview: 20%
Here are the most commonly searched roles for interview reports -
Submitted my resume online, and got an email about two weeks later setting up an Online Coding Interview with engineer using Skype and collabedit.com. And just some normal coding problem, cost about half or one hour. Write a function to process regular expression with letter, ".", "*".
Interview questions [1]
Question 1
Write a function to process regular expression with letter, ".", "*".
I applied through an employee referral. The process took 4 weeks. I interviewed at Meta (Menlo Park, CA) in Jul 2013
Interview
Application was via an internal referral from a friend who used to work at a start-up I was at. He put me in their system and around 4 days later, a recruiter called for first contact.
The recruiter was quick to assess what I have done and decide to bring me straight in for a 1h30 min interview the next week. In this session I got a quick "hi" from the recruiter and then two 30 min slots, one on architecture and design (so called pirate interview) and the other on coding (ninja). Of the 2, I stormed the coding question but met with an interviewer in the pirate side that had tailored a question from his previous experience in the area I had recently worked in and it didn't work out (mostly as I knew more about the topic and the interviewer wanted to talk about a specific trick he knew). Still, I got called back the next week for a full day.
Lunch, more coding, culture interviews etc... Coding and design were knockouts again, the softer skills were less successful. I think the key here is that you need to present a confident, well rehearsed personality with answers for the usual questions (biggest mistake etc...). DO NOT talk about mistakes and then admit you don't know the root cause for them, even if they were true mysteries. Pick another example!!!
The process took ~4 weeks, the end dragging out by 2 weeks as it seems they could not decide if it was a hire or not. I had multiple offers by this time and had to take one that was expiring and too good to miss. Later I found that there was no hire decision and felt ok about it - I would probably think about going back at some point, but with a stronger prep in the softer skill Q+A side.
Interview questions [1]
Question 1
If you go through the career cup questions, all 3 of my questions were on there. One of them I only had 15 mins to answer (the most difficult one) due to over running.