Decent, but not as pent up as expected
Decent, but not as pent up as expected
Nice people, some autonomy for contractors. Looks good on a CV. Workload is okay, though one can get very lucky or unlucky. Some people are drowning in work while others are doing nigh nothing.
The KX (King's Cross) office is nice.
Most DEs are in product-specific teams, which very specifically drives what needs doing. There is no movement likely within the company for contractors (likely, as the only time I heard that happen was during reorgs when people were forced to move around. This, of course, doesn't apply to permies; their situation is different.) Actually, a lot (read: almost all) of the tech Meta uses is either in-house or a customized version of in-house. For example, they use a custom version of Airflow and an older version of Presto, whereas the rest of the tools are almost exclusive to Meta only. This makes some of the knowledge more difficult to transfer, and for contractors, it makes it more complicated to put relevant tech on their CVs. Most DEs are glorified BI developers. There is relatively little data engineering going on for most DEs, and it's more about building visualizations and some pipelines feeding into those. Lower/immediate management is nice, but middle/upper management doesn't really give a fig about almost anything apart from their own KPIs.
Additional Ratings
Was this helpful?
Meta Interview Questions
Meta Interview Experiences
Data Engineer
Initial interview with a recruiter, followed by a technical interview. There are 3 problems in Python and 3 exercises in SQL to solve in 60 minutes. The problems are of medium complexity, but difficult to solve in such a short time.
Data Engineer
It was the initial interview. It was a coding interview on a platform with a shared screen with the interviewer. It was around 45 minutes, half Python and half SQL. The interviewer was super helpful. Difficulty was medium.
Data Engineer
It started with a recruiter call. The recruiter was friendly. They gave a time to choose from for the next round. The next round was 3 Python and 3 SQL questions in 25 minutes each. I solved 5 and got rejected.
Data Engineer
London, England, United KingdomOctober 23, 2025Initial interview with a recruiter, followed by a technical interview. There are 3 problems in Python and 3 exercises in SQL to solve in 60 minutes. The problems are of medium complexity, but difficult to solve in such a short time.
Data Engineer
New York, New York, United StatesNovember 17, 2025It was the initial interview. It was a coding interview on a platform with a shared screen with the interviewer. It was around 45 minutes, half Python and half SQL. The interviewer was super helpful. Difficulty was medium.
Data Engineer
United StatesNovember 15, 2025It started with a recruiter call. The recruiter was friendly. They gave a time to choose from for the next round. The next round was 3 Python and 3 SQL questions in 25 minutes each. I solved 5 and got rejected.
