Candidatei-me por meio de recrutador(a). O processo levou 3 meses. Fui entrevistado pela Meta (New York, NY) em mai. de 2020
Entrevista
A Facebook recruiter reached out to me in December to see if I would be interested in interviewing, based on my LinkedIn profile. Initial conversation was pleasant and recruiter was helpful in explaining the process.
About 2 months later I had an initial 45 min phone screen/interview with an existing engineering manager. The recruiter gives you all the necessary materials to prepare and they tell you the types of questions you need to have answers for. They follow the typical “tell me about a time when you had to...” format.
The recruiter followed up within a couple days to say they wanted to move on to the full day interviews. Due to Covid-19 I had to reschedule multiple times which wasn’t an issue.
The main set of interviews consisted of 6 x 45 min sessions with different interviewers. 1 is focused on your history. 1 on programming skills which included the standard algorithm type questions for which a quick google will give you plenty of examples (like sliding window, memorization, etc). 2 are focused on design where you walk through designing a theoretical system that scales to Facebook/Instagram levels of users. 2 are focused on soft skills and managerial style.
All interviewers were on time and pleasant. Interviews are back to back with a 45 min break for lunch. The interviews are done over video app as there are currently no onsite interviews.
Perguntas de entrevista [1]
Pergunta 1
Design a real-time comment system for under a Facebook post which may have millions of concurrent active users
Fiz uma entrevista na empresa Meta (Tel Aviv-Yafo).
Entrevista
Initial telephone call with a recruiter, followed by 2 zoom interview (system design + behavioral), followed with 5 zoom interviews (system design, behavioral and AI-coding-assistance). Process and recruiter were very transparent, supportive and well structured.
Perguntas de entrevista [1]
Pergunta 1
System design question + to tell and explain situations from previous experience
Candidatei-me online. O processo levou 2 meses. Fiz uma entrevista na empresa Meta.
Entrevista
Standard 2 interview screening + 5 interview if you pass the screening. You can prepare for the interview by looking up resources online - Meta has a fairly consistent process.
The only reason for me writing this report is that despite the recruiters' professionalism throughout, it was quite galling that after a long process and even after "passing" the hiring bar, I was told they were going to pause the role (though my 'pass' is good for 12 months). I'll post an update if I have one.
Do not trust the recruiter ...
TL;DR ...
The screening interview was swift. The recruiter was 15 minutes late and asked only one question to validate that I had one of the expected experience. There was no qualification of how much I knew about it. The first loop consisted in a behavioral interview with the hiring manager as well as a system design interview. The recruiter communicated the topic that will be analyzed in the design interview - a highly technical topic - as well as the name of the interviewers. I studying intensely to be prepared. I validated that the name of the interviewers three days before the interview. The recruiter confirmed them. Nevertheless, the design interview was on a different topic, not relevant to the field I was applying for. This is nonchalant from the recruiter. As a takeaway for other candidate as engineering managers, out of caution, I would suggest to prepare not only on your subject matter, but also on "generic" system design. Do not trust what the recruiter says. It would be better they say nothing rather than guide in the wrong direction.
Perguntas de entrevista [1]
Pergunta 1
A design question for a hardware-software system. The interviewer kept it generic, which added to the difficulty of the interview. I had to (1) switch from an end-to-end system design (EM level) to a low-level system design, (2) account for the super generic question while giving enough technical trade-offs, (3) not lose time time building a make-believe scenario as the interviewer was not looking for spec collection but rather a generic deep-dive.
