Meta interview notes, page 114 of 238

“My first instinct was brute force all subsets, which is fine given the constraint of at most 16 words, but I wasted time trying to be clever about pruning before I'd even confirmed the basic approach worked.” 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 base case clicked pretty fast: loop over followees, then loop over who they follow, filter out anyone the user already follows and the user themselves, deduplicate.” 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.

“Running it first before reading it carefully was probably the wrong call.” 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 say yes, 10% lift sounds good, ship it.” 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.

“The original post was vague, just a pinyin-obfuscated reference to a LeetCode transactions problem with no detail on the actual prompt or constraints.” 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.

“I got the basic BFS part out fast, that wasn't the issue.” 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.

“My first instinct was prefix sums with a hash set, which works when you have negative numbers in the mix.” 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 tricky part isn't telling the story, it's making sure both sides sound reasonable.” The rest of the author's notes on Software 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.

“Three questions bundled into one, which I didn't fully appreciate until I was halfway through the frequentist part and they asked about sample size.” 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 kind of question is tricky because the obvious answer feels like yes (big audience, social graph, events already exist on the platform) but you have to actually stress-test the business case.” The rest of the author's notes on Technical Program 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.