It was quite hard, but at the end of the day, it was reasonable. Meta is a sought after workplace and therefore the interview was very hard. I would definitely recommend giving it a go.
Did a phone-screening, and then a virtual code interview a bit later. The code interview was better set up than a lot of other companies I’ve seen: you don’t have access to a compiler, but the interviewer did encourage you to talk through your process + seemed aware that things like “forgot minor syntax detail” are not representative of what a programmer might be like in a real environment when they could quickly Google something like that.
Interview questions [1]
Question 1
Fairly standard C++ coding exercises, like the ones you’d see on LeetCode.
My interview process consisted of six stages:
Initial Coding Interview
– Solved 2 loop-focused algorithm problems.
Second & Third Coding Interviews
– Two rounds, each with 2 algorithmic problems.
Behavioral Interview
– Discussed past experiences, teamwork, and problem-solving approach.
System Design Interview
– Designed a scalable architecture for a given scenario.
Follow-Up System Design Session
– Dug deeper into trade-offs and data modeling from the previous design.
Interview questions [1]
Question 1
After designing the system using Kafka, Flink, and ClickHouse, the interviewer asked how I would solve the problem without using any of those technologies, building everything from scratch. He gave me a generic queue and a generic database.