Meta interview notes, page 101 of 238

“My first instinct was to just concat everything and sort, which works but feels lazy for a Meta interview.” 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.

“My first instinct was to just walk both nodes up to the root and collect the paths, then compare.” 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.

“The key insight is you only count a cell if its top neighbor and left neighbor are both not 'X', meaning it's the top-left corner of a ship.” 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.

“Market sizing.” The rest of the author's notes on Product Manager 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 started with engagement stuff like view-through rate and skip rate, which felt obvious, but then I got a bit tangled trying to separate advertiser-side metrics from user experience metrics.” 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.

“I jumped straight into features without anchoring on the problem first, which I could tell didn't land well.” 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.

“I went with user-level randomization pretty quickly and they pushed back asking why not session.” 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 was essentially a dissertation prompt compressed into 45 minutes.” The rest of the author's notes on Machine Learning 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.

“The O(n) constraint is the whole point of the problem.” 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.

“This was a level 3 extension of a simpler key-value store problem, so you had to build on top of existing add/remove/scan logic and layer in expiration semantics.” The rest of the author's notes on Software Engineer interview at Meta, Online Assessment (OA) round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.