Meta interview notes, page 99 of 238

“Classic majority vote problem extended to two candidates instead of one.” 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 knew the stack approach pretty quickly, split on slashes, skip empty strings and dots, pop on double-dots, done.” 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 went with a BFS approach, tracking (node, col, depth) tuples and dumping everything into a map from column to list of (depth, value) pairs.” 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 joined the two tables on copy_id, filtered for condition = 'good' and return_date IS NULL, then used COUNT(*) for the first column.” 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 log y part is the hint they're basically handing you.” 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 knew the prefix sum trick going in, which saved me.” 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 core idea clicked pretty fast for me, you want a sliding window but maintaining the running min and max efficiently is where it gets annoying.” 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.

“BFS, straightforward.” 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 to go straight to health and wellness use cases, which in hindsight felt a bit predictable.” 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 was basically a marathon question.” 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.