Capital One interview notes, page 8 of 39

“My first instinct was a plain GROUP BY on customer and month, which works, but I almost forgot to extract the month from the date field properly and nearly handed in something that grouped by the full date.” The rest of the author's notes on Data Scientist interview at Capital One, Take-home Assignment round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic 'fix a broken product' question and I went straight to the obvious stuff like appointment scheduling and wait times.” 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.

“Set up the revenue side first: 20 users times (15 GB at $1 each) gets you $300 in usage revenue.” 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 recognized the MGF form eventually but took an embarrassingly long pause before connecting it to a normal distribution with mean 0 and variance 2.” 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.

“Pretty open-ended and I kind of rambled at first.” The rest of the author's notes on Product Manager interview at Capital One, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty approachable once you see it's just a conditional aggregate and a sort.” 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 basically 'design a bank' and I underestimated how much ground they wanted to cover.” The rest of the author's notes on Software Engineer 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.

“This is a meaty one and I underestimated how structured they wanted it.” 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.

“Solved it pretty much immediately.” The rest of the author's notes on Software Engineer interview at Capital One, Online Assessment (OA) round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty straightforward join between the summary table and the types table, multiply units by price and then divide each row's revenue by the total.” 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.