Meta interview notes, page 164 of 238

“Classic Meta product sense question and I still felt underprepared.” The rest of the author's notes on Product Manager interview at Meta, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is where I spent the most time and probably where I lost the most points.” The rest of the author's notes on Data Scientist interview at Meta, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The 36% number is a gift because it maps directly to variance reduction.” The rest of the author's notes on Data Scientist interview at Meta, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one is deceptively big.” The rest of the author's notes on Machine Learning Engineer interview at Meta, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the main prompt and it ballooned fast.” The rest of the author's notes on Software Engineer interview at Meta, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I fumbled this a bit.” The rest of the author's notes on Product Manager interview at Meta, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the naive thing, single-source BFS from each gate separately, and the interviewer let me finish before asking what the complexity was.” The rest of the author's notes on Software Engineer interview at Meta, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This was basically five questions glued together and they expected a coherent answer, not five separate answers.” The rest of the author's notes on Data Scientist interview at Meta, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to retention and re-engagement because acquisition felt too obvious, but looking back I probably should have structured it more before diving in.” The rest of the author's notes on Software Engineer interview at Meta, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty simple linear scan, just iterate and accumulate when the element is between S and E.” The rest of the author's notes on Software Engineer interview at Meta, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.