I have mixed feelings about this recruitment process, specifically the screening.
The recruiter was very nice, the atmosphere was great, and the interview was not stressful.
On the other hand, the screening lasted only an hour, with approximately 45 minutes dedicated to the interview itself, excluding the introduction and the recruiter's explanation of the tasks.
My recruiter offered tips even though I had indicated I wanted a moment to think about the task. I wonder if these tips had a negative impact on the final score of the interview.
In the end, I solved all six tasks (three Python and three SQL), but two of them with the recruiter's help, which I did not request.
I was subsequently rejected.
I wonder if solving five of the six tasks completely on my own would have yielded a better result than solving all six with the recruiter's assistance.
In summary, the tasks were not very difficult, but the time allocated to solve them was very limited.
As for the tasks themselves:
From Python, there are dictionaries, arrays, and sets. They are quite simple, but you have to be careful with edge cases.
As for SQL, it's mostly JOINs and aggregation functions.
One task I had could be solved with a window function, but the recruiter said to do it in a different way (GROUP BY, HAVING, and LIMIT).
Hope that helps you guys :)
The following metrics were computed from 1 interview experience for the Meta Data Engineer role in Warsaw, Masovian Voivodeship.
Meta's interview process for their Data Engineer roles in Warsaw, Masovian Voivodeship is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Meta's Data Engineer interview process in Warsaw, Masovian Voivodeship.