I found a Facebook recruiter on LinkedIn and sent her a connection request. The next day, I received a reply asking for my contact details and if I was interested in Data Engineer positions.
Three days later, I received a call from another recruiter who asked five SQL and five Python questions. The SQL questions covered topics like left joins and having clauses, while the Python questions focused on linked lists and stacks (e.g., what data structure is FIFO). These were true/false type questions.
Following this, I was given 14 days to prepare for a telephonic interview, which consisted of 30 minutes of SQL and 30 minutes of Python.
The telephonic interview was good, but again, it's a matter of how comfortable and fast you are. I was able to answer three out of three SQL questions and two out of three Python questions. Due to time constraints, the interviewer kindly suggested closing the call.
I believe I could perform better in direct interviews where design questions are asked. However, these timed coding interviews make me nervous. If you focus on that aspect, you can easily pass this round. Most of the questions are similar to those found on Glassdoor.
SQL questions on promotions and sales schema:
MySQL was used, and the interviewer asked if these could be done without subqueries.
Python:
[1, None, 1, 2, None] --> [1, 1, 1, 2, 2]
Ensure you take care of inputs like [None], which means a None object.
Find 's' in 'mississippi'.
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.