Lyft interview notes, page 2 of 10

“I started with US population, tried to narrow down to people likely to go out on Halloween, then layered in what fraction might use Lyft vs drive or walk.” The rest of the author's notes on Software Engineer interview at Lyft, 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 supply-demand ratios and talked about things like average delivery time and order fulfillment rate.” The rest of the author's notes on Product Manager interview at Lyft, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Spent the first few minutes just trying to nail down what 'identity' even meant in this context.” The rest of the author's notes on Software Engineer interview at Lyft, 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 scope on this is huge and I think that's the point.” The rest of the author's notes on Product Manager interview at Lyft, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Multi-source BFS, seeded with all initially compromised servers at once.” The rest of the author's notes on Software Engineer interview at Lyft, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Multi-source BFS, pretty standard once you recognize the pattern.” The rest of the author's notes on Software Engineer interview at Lyft, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“You have to resist the urge to just throw out a number.” The rest of the author's notes on Product Manager interview at Lyft, 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 where I fumbled a bit.” The rest of the author's notes on Product Manager interview at Lyft, 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 went with a plain hashmap first, which felt obvious, and it was.” The rest of the author's notes on Software Engineer interview at Lyft, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The text-only output constraint is what makes this interesting and also where I kind of stumbled.” The rest of the author's notes on Product Manager interview at Lyft, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.