← Back to Directory

Lyft interview notes, page 4 of 10

Large Enterprises

Most of these Lyft write-ups come from Software Engineers (41), then Product Managers (28) and Data Scientists (19). The most reported rounds are the technical phone screen (42), the product sense round (29), the system design round (12) and the behavioral / leadership round (4).

97 interview notes · updated Sep 2026

Lyft·Software Engineer·Hiring Manager Screen

May 2026
Interviewed at Lyft for a SWE role, and it was pretty much a standard screen with a culture-fit angle thrown in.
  • What do you look for in a company you're considering joining?

“Blanked a little on this one.”

View Post

Lyft·Software Engineer·Technical Phone Screen

May 2026
Lyft software engineer interview that was basically one long design problem dressed up as a coding question. More depth than I expected for what started as a simple key-value store.
  • Design and implement a nested key-value store supporting set, get, and delete operations using dot-delimited paths like 'a.b.c'. It should create intermediate nodes automatically, handle overwrites, and return meaningful errors for missing paths.
  • Add an iterator that lists only the immediate children under a given path prefix.
  • Implement a flatten method that converts the entire nested structure into a single-level map using full dot-path keys.
  • Add optional type checking to prevent overwriting a value with an incompatible type at the same path.
  • What are the time and space complexities for each operation, and how would you serialize and deserialize this structure?

“Started fine, built a trie-like nested map structure and the basic operations clicked pretty quickly.”

View Post

Lyft·Data Scientist·Technical Phone Screen

May 2026
Second round coding interview for a Data Scientist role at Lyft. Just one problem but it was more involved than I expected going in.
  • Implement stratified k-fold cross validation from scratch.

“I knew the concept well enough to explain it but actually coding it up is a different story.”

View Post

Lyft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Lyft product interview, one question about dynamic pricing. Short but deceptively tricky if you haven't thought through the edge cases before.
  • How would you design a dynamic pricing system for Lyft?

“I went straight to supply and demand levers, talked about surge multipliers, geographic zones, time-of-day patterns.”

View Post

Lyft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Lyft product interview, one meaty question about dynamic pricing and how you'd run an experiment around it. Not a lot of context given upfront which made it tricky to scope.
  • How would you design a dynamic pricing system and then A/B test it?

“Two questions in one, which I didn't fully appreciate until I was halfway through talking about surge multipliers and realized I hadn't even touched the experimentation side.”

View Post

Lyft·Software Engineer·Technical Phone Screen

May 2026
Lyft SWE interview with a backtracking problem, pretty focused on algorithmic thinking. Nothing too wild but it required more depth than I expected for what seemed like a straightforward search task.
  • Implement a search algorithm that finds multiple matching records using backtracking.

“My first instinct was to reach for a simple BFS and call it done.”

View Post

Lyft·Software Engineer·Onsite - System Design / Architecture

May 2026
Lyft system design round for a software engineer role. The question was a full-on real-time chat system design covering basically everything you could think of, and I mean everything. Left feeling like I'd only scratched the surface on half the topics.
  • Design a scalable real-time chat system that supports both 1:1 and group messaging. Walk through API design, message ordering, read receipts, online presence, storage, sharding, consistency trade-offs, offline delivery, rate limiting, encryption, capacity estimates for 100M DAU, and observability.

“This was basically a 45-minute gauntlet.”

View Post

Lyft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Lyft PM interview with a product design and monetization case focused on healthcare transportation. Single question, pretty open-ended, and the monetization piece is where things get interesting.
  • How would you design a Lyft product to improve transportation for patients, and how would you monetize it?

“The product side felt manageable once I anchored on a specific patient segment, I went with non-emergency medical transport since it's a real pain point and Lyft already has some traction there.”

View Post

Lyft·Data Scientist·Technical Phone Screen

May 2026
Lyft data science interview with a meaty product analytics case about coupon targeting. Single question but it went deep fast, covering segmentation, causal inference, and experiment design all in one thread.
  • A ride-sharing company wants to run a coupon campaign to grow commuter rides but has a limited budget. How would you figure out which users should actually get the coupon?

“The part I fumbled initially was jumping straight into segmentation without anchoring on what 'success' even means.”

View Post

Lyft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Lyft product interview, one question about designing the product for a commuter use case. Pretty open-ended and I wasn't totally sure how deep they wanted me to go on the user segmentation side.
  • How would you design Lyft specifically for commuters?

“I started by trying to define what a commuter actually needs versus a casual rider and that part felt okay.”

View Post