Candidates applying for Data Engineer I roles take an average of 30 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 27 days.
Common stages of the interview process at Meta as a Data Engineer I according to 1 Glassdoor interviews include:
One on one interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Meta in Dec 2017
Interview
The Hr reached me out through the email. I first thought that it was some spam email so I double checked the Hr's details and then contacted her back. Soon enough there was a small 15-20 min call with her and we got to know each other during the call. She was very interested in knowing if I use SQL on a daily basis. Since i didnt use it daily i told her and she asked me to prepare for it for the interview. Next she emailed me a bunch of study material for both sql and python. I didnt make it to an onsite interview since I was slow. There were 30-30 minute sessions for python/sql and the interviewer was quite particular with the time.
I could solve 2 python and 2 sql questions in the given time. Though I struggled in the second sql question a little bit.
The overall experience was good as the interviewer helped me with my thought process throughout.
tips:
1.Please communicate your thoughts to the interviewer
2. once you build a rough algorithm , just start executing it without too much thought. you will get to know the errors in the compiler and u can change the syntax, or logic accordingly. This will save you a lot of time.
3.Try to complete more questions in less time (ofcourse they should show the correct output)
4. be confident in whatever you are doing. If you cant figure out a way to write a logic by yourself, just ask the interviewer quickly. They will definitely help
Interview questions [1]
Question 1
Python
1.given an ip address as an input string, validate it and return True/False
2.count the neighbors of each node in a graph. input graph is a multi dimensional list
SQL
1. Display the most common name in the table
2. a case statement related question. pretty straightforward
I applied through a recruiter. The process took 3 weeks. I interviewed at Meta (Seattle, WA) in Dec 2017
Interview
HR approached via Linkedln. Then asks me more details by referring with another person's name. I realized it must be typo so simply notified him. He corrected my name and Set up a call to understand my background and then set up a 1st coding interview with a junior SDE.
The process took 2 months. I interviewed at Meta (Menlo Park, CA) in Dec 2017
Interview
Recruiter reached out to me on LinkedIn. Gave me enough material to prepare over a month and then scheduled a two-part phone interview (SQL and Python).
Phone interview was pretty much exactly as everyone else explained. Just focus on easy & medium complexity problems. It is fine even if you struggle on some problem, just take the hints and communicate your though process (It is tough when you have limited time).
I got the phone call from HR on the same day about the result and was invited for onsite interview. The onsite interview is like a working session with a colleague. I would say the most important skill is designing the table to get desired result followed by SQL and then python. The recruiter offered me the job 2-3 days later.
You will be given enough material at each stage, just dig into that information and keep on practicing. Try to practice on whiteboard to get comfortable with the on-site interview experience. One more advice - please do not neglect SQL even if you have a good experience on it as it becomes difficult on whiteboard.
Overall the best interview process i ever had. Everyone is really nice and want you to succeed.
Interview questions [1]
Question 1
Phone Interviews - covered by other interviews on glassdoor
Onsite - 3 full stack interviews and 1 lunch interview - focus on the material given by recruiter.