This lightning lesson, given by the presenter with the hosts handling the chat and the presenter calling it lesson 9, argues that analytics interviews reward structured thinking more than knowledge. Its method is an AI loop: an agent pipeline in Claude Code researches the target company and builds a prep pack and a paced plan, then a mock-interview copilot runs practice, and its feedback goes back into the plan. DoorDash is the worked example, prepared for a staff data scientist role.
What interviewers score. An opening poll describes a free trial with signups 40% above target and revenue 50% below, and most attendees picked clarifying questions. The presenter says that is right. From hundreds of hiring-manager interviews, the presenter says strong candidates fall down on structure: scope, metric, decomposition, trade-offs and decision. They ask clarifying questions only for form, skip decomposition, and give no recommendation at the end. The worked answer asks whether "revenue" means total or per trial user and whether the signup lift was organic or paid. It splits revenue into trial starts × conversion × ARPU, forms hypotheses with a check for each (source mix, adoption in the first 7 days, checkout abandonment), asks the interviewer which branch to pursue, weighs cannibalization and ROI, and ends on a decision. The presenter says this matters more the more senior the role.
Question types. Five types, each with a DoorDash example: measuring success, diagnosis (orders down 15%), experiment design, launch-or-not, and improvement. A single interview may chain them. The advice is to classify the question, know which dimensions it calls for, and then structure the answer.
The pipeline demo. The demo ran in Claude Code inside an IDE. A company intel builder skill calls three agents (earnings researcher, blog synthesizer, competitive analyst). A metric tree builder and an experimentation researcher run in parallel, then come cheat sheets and an HTML stage, ending in 12 files. The GOV tree goes from orders × AOV down to new, retained and churned consumers split by acquisition channel and DashPass status. A delivery-time tree runs from dasher matching to restaurant prep-time prediction. Other files cover the earnings metrics, including adjusted EBITDA, a 16-page staff-interview deep dive on network effects, and the public talks of DoorDash's analytics leader. The presenter says companies with little public material are researched through similar companies in their sector.
The copilot. The copilot is a Claude project with practice, coach, simulate and full-answer modes. It holds a smaller generic set of documents, because the full 15 files would not load under Claude Pro. In simulate mode Claude played both a fictional Meta interviewer and the candidate, in chunks. Coach mode listed clarifying questions, frameworks and a recommendation template.
Q&A. Asked about Perplexity deep research, the presenter said the difference is the course's own methods built into the pipeline, while admitting to not having tried Perplexity recently. For long reports, a co-host advised choosing a length you will actually read and reading critically, citing a research report that AI use causes atrophy in people who take one-shot output but sharpens people who use it as an interactive peer. On privacy, the host said to treat Claude Code like any vendor (procurement, legal and security), noting that zero-data-retention contracts can permit customer data. On sycophancy, the host guessed that chat products are tuned to engagement metrics and said Claude Code can be made to push back. On hallucination, a co-host believed the pipeline ends in a fact-checker step.