Software Engineer applicants have rated the interview process at Meta with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 59% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 32 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 32 days.
Common stages of the interview process at Meta as a Software Engineer according to 6 Glassdoor interviews include:
Phone interview: 43%
One on one interview: 29%
Skills test: 29%
Here are the most commonly searched roles for interview reports -
good people. Know their stuff. You need to read the job description really well and be sure that you speak to the requirements because *they* may not ask for them precisely in the interview: none the less are expecting you to cover these. They are perhaps more concerned with standard methods than they initially project. Carefree attitude in some employees in interview process, others are VERY interested to hear about process.
This was a phone screen. I said I didn't know html/javascript so they just asked me some programming questions: write a sqrt() function and a strstr() function. I wrote both in java. The sqrt used the bisection method, and strstr was just a nested loop.
I didn't get called back probably because of wrong skill set. Not sure why they wasted the time since it was on my resume.
Interview questions [1]
Question 1
The sqrt() was a bit unusual for an interview question.
I applied through a recruiter. The process took 3 weeks. I interviewed at Meta (New York, NY)
Interview
Started with a phone interview which led to an on-site. I had a coding question at the same level difficulty that you would expect for an on-site in the initial phone interview. The NYC office was really nice and the on-site interview process is about the same as most other tech companies, usually starting with coding questions and then one architecture/design question.
Interview questions [1]
Question 1
Many of the questions exploited data structures for fast running time. Also I'd practice designing features.