Loop on leadership and technical competencies. All the interviewers were white males, only the person I ate lunch with was a woman. The recruiter was a complete nightmare, and they booked me in a hotel that was miles away from the campus, and beyond the campus from the airport, resulting in me spending a LOT of time in transport that was unnecessary.
Interview questions [1]
Question 1
Questions about machine learning breadth and depth
I applied through a recruiter. The process took 7 weeks. I interviewed at Meta (San Francisco, CA) in Oct 2020
Interview
Recruiter reached out and proposed a role that looked fairly interesting. First step was to talk to the hiring manager, I gave my availability the first day but eventually took 4 weeks for that to be scheduled. The talk with Hiring manager was just a chat, its more like he sells you the role rather than you need to sell him yourself. Then its the first round technical phone interview. Which also took two weeks to schedule, extremely slow I don't know if its because of Covid and everyone moved out of california.
Technical phone interview was with another DS manager, its the same system you read here: data and then product sense. They don't really care about your background or fit, just run through the lines. They are actually fairly basic data questions, just that you don't have much time to think and you can't be wrong at any point. It does feel quite intense if your interviewer is trying to question you every 5 seconds, and confirm you are not wrong. I used Python but the interviewer didn't know any python, I had to explain what the syntax means when I try to think at the same time, and keep in mind of the time. They will push you to stop when its time even if they interrupted you most of the time. So you have to find a balance between you speaking out your mind to him and actually coding.
The product sense question was standard too, I prepared some structure to answer those questions, but my interviewer didn't let me go through them, he kept jumping in with side questions while I was trying to lay out the steps and getting to the answer. I don't think I handled that too well, as I was constantly interrupted with questions that I was going to answer or to clarify with him. Again you can't be wrong at any stage. I think what killed my chances was that either I misunderstood his question or he asked the question wrong, he said something happened and metrics spiked and what would you do. Its a very typical question and I prepared for it. But half way answering he started to question part of it, and then I started to realize what he said was not the same as what he asked. I tried pointing out the misalignment but it was already too late. When you try to clear things up over a video call with lag it just turns into an argument. Received a no the next morning.
Interview questions [1]
Question 1
A table with posts and a table with reactions to posts. Find the avg number of likes per post for the past 28 days.
For context, I've been Director level at other Fortune 500 companies. Right now I'm in a start-up.
The process was long, boring and point-less. The recruiter reached out themselves, and then promptly started ignoring my emails the minute I actually began to show interest. Twice I had people forget to get on the phone at the time they'd scheduled.
They spend a lot of time covering the "interview process at Facebook". It just feels like a marketing pitch and to do decently you have to spend a bunch of time researching the company and their process. Unless you're just in it for the money, I'd say skip this biased process that only measures your "Facebook fit" and not your true job skills.
Interview questions [1]
Question 1
Asked me about product metrics. They insist they are just looking for your "thought process", but the interviewers are inexperienced and thus looking at a check box on the side. My interviewer kept prodding me to cover a very specific metric and didn't care at all about the framework I outlined. The specific metric they finally disclosed would have given a very biased outcome - something they would have known if they had any experience at all. 2 yrs working in 1 company and a PhD that doesn't cover any true business scenarios doesn't qualify you to interview an industry veteran.