Meta interview notes, page 54 of 238

“Knew it was BFS pretty fast, that part wasn't the issue.” 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 create and deposit parts went fine.” 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 derivation part was fine, I remembered enough calculus to get through it.” The rest of the author's notes on Machine Learning 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 flatten everything and filter, which works but I kept second-guessing myself on the dedup step.” 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 spent the first couple minutes just trying to figure out who the user even is, someone in crisis, someone casually browsing, a parent looking for a kid's therapist.” 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 had a solid story here but rambled a bit on the technical details when I should've stayed on the impact side.” 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.

“This is the kind of question where you think you're doing fine and then the follow-ups expose all the stuff you glossed over.” 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 scope of this one is enormous.” 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 started with namespacing because it felt like the safest entry point, something like service/environment/feature_flag as a hierarchical key.” 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.

“The first part I handled okay.” 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.