Me postulé a través de un reclutador. El proceso tomó más de 1 semana. Acudí a una entrevista en Meta (Menlo Park, CA) en feb 2008
Entrevista
The hiring process was pretty smooth. You operate through a recruiter as your aid on the other side. Mine was friendly and quick to respond to a lot of my questions and kept me up to date with the whole process.
The initial process was a brief phone meeting with the recruiter. She asked me a few easy questions which I assume were to check if I was competent and then set up a call with an engineer at Facebook. On the phone we talked for a while and he explained the company culture, asked me some softball questions about my resume and then asked technical questions and had me write code in a shared editor from my computer. Your basic CS-200 algorithms questions.
A few days later I was invited to the Facebook HQ and met with a half dozen people including my recruiter. She took me to lunch at the cafe and then I went through a number of interviews. Most of which were asking me coding questions to write out on the whiteboard. More CS-200 algorithm style questions. One part of the interview that was fun was more of a architecture question where I designed a system for serving news feed.
A couple days later I had an offer over the phone from my recruiter and a full packet came in the mail a few days after that.
Preguntas de entrevista [1]
Pregunta 1
There was one coding question I had to answer that was particularly difficult was I was given a big chunk of Objective C code and asked to find the bugs in it. It was a bit like Where's Waldo where there's more than one Waldo but they don't tell you how many Waldo's there really are. I found a bunch of bugs but was nervous I didn't find them all.
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.
Preguntas de entrevista [1]
Pregunta 1
System design question + to tell and explain situations from previous experience
Me postulé en línea. El proceso tomó 2 meses. Acudí a una entrevista en 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.
Preguntas de entrevista [1]
Pregunta 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.
