Data Engineer I 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 74.2% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 5 weeks. I interviewed at Meta (Palo Alto, CA) in Jul 2018
Interview
The recruiter reached out to me. Then took the remote coding interview. Lastly went through the on site interview. People are really nice and smart. They tried to discuss with the candidates and helped them through the questions.
Interview questions [1]
Question 1
SQL: joins, aggregations
Python: basic data structures
I applied through a recruiter. The process took 1 day. I interviewed at Meta (San Francisco, CA) in Jan 2018
Interview
This was a tech screen using CoderPad. 1 hour and a problem set of about 5 SQL questions and 5 Python questions. Generally allocate about 5 minutes per question. The interviewer is helpful, so be sure to work with him and her.
Interview questions [1]
Question 1
There was a string parsing question via Python. Just know how to parse a string into words or even letters and to apply some sort of logic to the string.
The process took 4 weeks. I interviewed at Meta (Menlo Park, CA) in May 2018
Interview
I was contacted on LinkedIn by a recruiter. Recruiter was extremely professional and helpful. He gave me the good advice to prepare for 1 or 2 easy/medium leetcode q's for phone round everyday for 3 weeks and I did exactly that. I bought the leetcode premium package where i was able to do the Facebook track and a lot of questions i got throughout the process were similar to one there.
For phone round, i was asked 3sum + bunch of SQL questions related to department/salary and applied/recruiter data sets which you can find on glassdoor and leetcode. Some SQL questions were slightly tricky and I was glad i prepared. The interviewer was passionate about his job and answered a lot of questions.
I setup onsite soon after phone, recruiter sent me a lot of material and also did a phone call to help prepare. As I started preparing for the onsite interview and reading a little bit about the role, it appeared that the data engineer role at facebook is not as appealing as the Software engineer role and it was validated during the interview where i learnt that 2 of the interviewers were transitioning to software engineering roles - this was a red flag for me because I have a long and solid background in CS and data eng. The product sense question was confusing because I wasn't sure what the interviewer wanted but i guess they just wanted ERD and database schema, maybe they should call it that? because i started with client-server diagrams etc which was not needed. I like some of the ETL questions, it was fun to solve. The behavior round was also fun. I was skeptical but the time went by quickly.
The recruiter had sent some very good material which helped me with other interviews as well. I should add that I interviewed for the Enterprise engineering team which i learnt during the process supports the Product team. If it was more clear to me, I would have probably tried to interview in the Product team , because looked like people were trying to move from Enterprise engineering to product >< haha
Overall good process, i did not get an offer but i was hooked up with another recruiter in Facebook where they thought I might be a good match. I chose not to pursue that .