I applied through an employee referral. The process took 4 weeks. I interviewed at Meta (Menlo Park, CA)
Interview
- Employee referral to Phone Screen
- Phone Interview with web coding (algorithm + SQL) via coderpad.io
- In-person Interview with data structure/algorithm coding, sql coding, a "lunch" that was essentially a compatibility interview, and then a full stack interview that was basically a combination of all three.
Interview questions [1]
Question 1
in the phone interview:
- pretty basic python algorithm question. Having read the others here, I assumed I'd get pitched a softball and then a harder question. I was able to solve it within the first several minutes, but spent the rest of the session trying to optimize the solution.
- some basic SQL questions on joins and such. I answered probably 5 or 6 questions. Both of these interviews seemed like minimum bar screens.
For the in-person interview:
- more difficult python question and had to code on a white board. It was a pretty simple sorting question that was easy to solve but less trivial to optimize.
- more difficult SQL questions. I struggled here but I was a bit weaker in SQL so I figured as much. This progressed into dashboard design.
- Lunch was at a cafe on campus and delicious. Interviewer was just asking me about work experience and culture and it seemed just like a general personality compatibility test.
- Full Stack interview was my favorite part and a lot of fun. Without giving too much away, I was given a realistic problem and tasked with conceptualizing the solution in real time, from start to finish, on a white board. It was a mix of coding and conceptual and seemed to be meant to test product sense.
5 sql
5 data structure and algorithms
25 mins each
They won't go to the next problem until one is done and expected results are met
Interviewer was very professional and tried to guide to think through the problem
Wen through standard screening call then the TA. The TA was a much higher difficulty then the prep guide. Not so much the difficulty of the question from a technical perspective, but understanding what the question was actually asking for. Example would be a problem like bookstore checkout system, but the explanation of it was sort of vague and the interviewer didn't really help me clear it up.
Starts with a screen, followed by leetcode style SQL+Python questions, Full loop of SQL, Python, SQL plus Python and lastly behavioural round. Every round is also an architecture round in some sense.
Data Engineer applicants have rated the interview process at Meta with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 65% positive. To compare, the company-average is 56.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Data Engineer roles take an average of 35 days to get hired, when considering 365 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 31 days.
Common stages of the interview process at Meta as a Data Engineer according to 365 Glassdoor interviews include:
Phone interview: 41%
One on one interview: 20%
Skills test: 16%
Presentation: 9%
Group panel interview: 5%
Other: 3%
IQ intelligence test: 2%
Background check: 2%
Personality test: 2%
Drug test: 1%
Here are the most commonly searched roles for interview reports -