Capital One interview notes, page 35 of 39

“I went straight into user acquisition channels and kind of forgot to anchor on what 'growth' even meant for this product specifically.” The rest of the author's notes on Product Manager interview at Capital One, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty mechanical once you lay it out.” The rest of the author's notes on Data Scientist interview at Capital One, 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 tripped me up because my first instinct was to pick a story where I 'won' the disagreement, which is the wrong move.” The rest of the author's notes on Software Engineer interview at Capital One, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one took me a minute to even figure out where to start.” The rest of the author's notes on Data Scientist interview at Capital One, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the classic secretary-ish stopping problem and I'd seen something like it before, so I wasn't totally lost.” The rest of the author's notes on Data Scientist interview at Capital One, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The swap and reverse stuff was pretty mechanical.” The rest of the author's notes on Software Engineer interview at Capital One, 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 minimum spend thresholds and felt pretty good about it, but then kind of stalled when trying to get specific.” The rest of the author's notes on Data Scientist interview at Capital One, 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 knew the formulas but fumbled the pooled variance denominator at first, mixed up whether you use nA+nB-2 or something else.” The rest of the author's notes on Data Scientist interview at Capital One, 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 listing revenue and costs which felt right, but I kept second-guessing whether to include acquisition costs as a fixed or variable item.” The rest of the author's notes on Data Scientist interview at Capital One, 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 I actually felt decent about.” The rest of the author's notes on Data Scientist interview at Capital One, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.