The entire interview was supposed to be one hour, with 5 SQL and 5 Python questions.
While the questions were generally available online, there were slight differences in the details, possibly due to minor tweaks. The interviewer was Indian, a senior Data Engineer with 10 years of experience.
I mentioned that I wasn’t familiar with Codepad, and he gave me a short demo — but it was counted within the timer for my first SQL question.
When I got stuck and asked if he could give me a hint, I noticed he seemed completely disengaged, so I had to figure things out on my own. Later during the Python portion, he said there was a web tech issue and couldn’t give me the question immediately. He had to restart his computer, and it took more than 10 minutes to get the question. In the end, the whole interview dragged from one hour to an hour and a half.
Group by payment type to calculate total sales and the number of unique customers.
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.