Lyft interview notes, page 3 of 10

“The core read-and-count loop took me maybe five minutes to sketch out.” 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.

“Classic problem, I've done this before, and yet I still fumbled the part where you have to keep the doubly linked list and the hashmap in sync on every operation.” 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.

“Ran out of time before I had a clean solution.” 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.

“This is the kind of question where you can spiral fast if you don't anchor on something concrete first.” 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 knew the formula but fumbled the intuition part.” The rest of the author's notes on Data Scientist 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 started with a sorted map per key and binary search, which is the right instinct, but fumbled a bit explaining why sorted insertion is still O(log n) amortized versus a naive array.” 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.

“This question has so many branches that I spent the first few minutes just trying to figure out where to start.” The rest of the author's notes on AI 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.

“I jumped straight to 1 minus (1-P)^N which is right, but I fumbled explaining why for a second.” 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 started with the rider experience because I figured ads in a captive in-car context are different from, say, a feed.” 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 started with fit and just stored sorted unique categories in a list.” The rest of the author's notes on Machine Learning 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.