Interviewed on March 29th. It was a standard interview process, and the interviewer was helpful. They assisted with minor code changes when I was about 80% there, which helped me move to the next question. Overall, it was a great experience. The interview seemed easy because I was aware of the potential questions. Otherwise, under a time constraint, it would have been tough.
I performed well and completed four SQL and three Python questions.
However, the recruiter contacted me stating that the questions had been repeated from my previous interview, which was a year ago. At that time, I was only able to solve one Python and three SQL questions. They wanted me to take a phone interview again, but with a different set of questions this time.
I have yet to give the interview but expect a new set of questions.
Python:
None with the next element in the list.SQL:
2 questions on CASE,
1 on ORDER BY/LIMIT/RANK/TOP (whatever you want to use),
percentage/ratio calculations/joins.
The following metrics were computed from 347 interview experiences for the Meta Data Engineer role in United States.
Meta's interview process for their Data Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Meta's Data Engineer interview process in United States.