Data Engineer I applicants have rated the interview process at Meta with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 59% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Meta as a Data Engineer I according to 3 Glassdoor interviews include:
One on one interview: 33%
Phone interview: 33%
Skills test: 33%
Here are the most commonly searched roles for interview reports -
Colloquio iniziale con recruiter e poi colloquio tecnico con 3 problemi in python e 3 esercizi in SQL da rivolvere in 60 minuti. Problemi di media complessitá ma difficili da risolvere in così poco tempo.
Interview questions [1]
Question 1
Esercizi classici di leetcode di media complessitá
I applied online. The process took 2 months. I interviewed at Meta in Sep 2025
Interview
Screening call with HR allocated to you.
They will explain you the whole process, provide you with materials and will ask you to choose several dates in your calendar for further technical interview.
Usually, you can take up to 3 weeks to get yourself ready.
Technical interview consist of 2 parts: SQL and Python.
For each block you have 25 mins.
It is recommended to solve 3+ tasks in each section to move forward for a next round which is Data Modeling.
Technical interview tasks are easy/medium tasks from leetcode.
Interview questions [1]
Question 1
Build loop with tuples to extract values.
Dictionary leetcode tasks.
Classes and functions tasks.
I applied through a recruiter. I interviewed at Meta
Interview
The interview was quite time-constrained, so it was important to move through the questions quickly. The interviewer was helpful and gave hints if you got stuck, which made it more collaborative. One key takeaway is to clarify the question upfront especially for SQL since there can be edge cases that aren’t obvious unless you discuss them first.
Interview questions [1]
Question 1
Which books are in good condition and have been renewed exactly twice?
What percentage of books have more than 10 copies in the inventory?
What is the difference in renewal counts between a borrower and the member who referred them?
Given a list of (category, price) pairs for each user, where each user is allowed to borrow items from up to 3 unique categories, how can you calculate the total price of borrowed items per user?
Given log entries for each book where True indicates a checkout and False indicates a return, how would you validate the logs such that:
A book cannot be checked out if it's already checked out.
A book cannot be returned if it's not currently checked out.