I applied through a recruiter. The process took 4 weeks. I interviewed at Meta (London, England) in Jun 2020
Interview
In early covid times facebook reached out through their recruiters. I had a conversation with the recruiter and felt that it could be a potential good match. My extensive experience in a particular area of software engineering was spot-on, and I felt I could grow as a manager from the small/medium sized companies I previously had experience in. I had a remote interview with a single senior manager. It was unfortunately very superficial without any actual interest in my profile or competencies. It felt like I was answering a questionnaire with predefined good/bad answering categories reflecting only the way big american companies do management. It was probably a bad attempt at being unbiased in interviews. This approach did not explore my experience or show real interest in me as a person.
After this interview Facebook did not see a good match as a manager. I also did not feel sought after - so the conclusion was mutual.
Facebook did ask if I wanted to interview for an IC position, which I agreed to - just to see what that would be like. They never did return as promised, so my verdict is still negative when it comes to the process at Facebook.
Interview questions [1]
Question 1
Facebook will provide lots of material on the interview process itself. I was asked about
* The type of engineering leader I am
* Handling conflict, decisions, build consensus, etc.
* Defining my own success and teams success
* Professional failures and learnings
*1:1s, personal development of your team, coaching and mentorship
* Career management
* Technical decisions
* Design tradeoffs, constraints, learnings in systems
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.
Interview questions [1]
Question 1
System design question + to tell and explain situations from previous experience
I applied online. The process took 2 months. I interviewed at Meta
Interview
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.
Interview questions [1]
Question 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.
