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 67% positive. To compare, the company-average is 74.2% 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 3 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 43 days.
Common stages of the interview process at Meta as a Software Engineer according to 3 Glassdoor interviews include:
Skills test: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2+ months. I interviewed at Meta
Interview
I applied online, and a recruiter reached out to me almost two months after. She asked me for some info and my availability and within two or three days scheduled one technical phone call with an engineer. The engineer was extremely helpful and you could tell he genuinely wanted me to do well (study prior), good after convo don't be afraid to ask questions! It's not everyday you get to talk to an engineer working for facebook.
I applied through a recruiter. The process took 2 months. I interviewed at Meta
Interview
contacted thru linkedn , if I was interested in facebook. Pondered whether to give a try or not . As my impression was facebook being php shop and me being a scala developer it would not match my skillset(Not interested in going back to dreaded c++ either). Meandered and then agreed for phone interview.
I have pretty good exp (10+) most of these interviews are not cakewalks but not hard either. Only concern being absolutely neat monkey coding text book soln in 30-40mins. Most of the interviewers are nit picky and want perfect code. So you have 10 mins to think and 30 mins to code in a collabedit. Unless you are able to monkey code the soln while talking to interviewer , just simply avoid its nothing but sheer nonsense. But if you want to practice then ;-)
Interview questions [3]
Question 1
The interview called up 30 minutes late and rushed thru.
Given a string break it up into meaningful sentence "thesystemisrunning" => the system is running
Got a call saying they need to take another interview, was nearly about to say thanks but no thanks but ended up taking it just for practice.
LRU cache which gives latest accessed element.
Applied through a referral. It was just the initial phone screen. Interviewer was calm and nice. Started with introductions and then we proceeded to coding on the online collaborator. After two questions, the interviewer asked if I had any questions. Spoke for a while and realised we were out of time.