I was reached by a recruiter and invited to an online interview.
The interview lasted about 90 minutes, and I was given two problems to solve. The first one was an easy LeetCode-level problem, while the second was a medium-level task about graph traversing. The interviewer was nice and helpful, offering a few tips. I didn't write working code for the second problem, only verbally describing a solution that was probably not the most efficient one. Even though I didn't completely solve the second problem, I was invited for an on-site interview.
There, I had two coding interviews, one system design interview, and one behavioral interview.
The coding problems were easy and medium-level LeetCode tasks involving recursion, string manipulation, and arrays. I managed to solve three out of the four coding tasks.
The system design interview was quite abstract, requiring me to build a system to perform certain tasks. From my experience, one needs either experience in similar tasks or thorough preparation for system design; this interview was the hardest for me.
As a result, I was rejected with feedback stating that I did not pass the system design and one of the coding interviews.
In general, the experience was very positive and useful. The coding tasks were easier than I expected, even though I didn't solve one of them. I would also suggest paying more attention to preparation for system/app design interviews.
Easy/medium level LeetCode questions on recursion and string manipulation.
The following metrics were computed from 6 interview experiences for the Meta Software Engineer role in Netherlands.
Meta's interview process for their Software Engineer roles in Netherlands is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Meta's Software Engineer interview process in Netherlands.