Lyft Interview Questions — Page 7

Lyft·Data Scientist·Technical Phone Screen

Jun 2026

Lyft data scientist interview with a probability-heavy modeling problem built around a ride-hailing commuter scenario. Five parts, all chained together, and the whole thing lives or dies on whether you set up the per-trip independence correctly at the start.

A commuter takes two trips per day (morning and evening) with independent probabilities p and 2p of using the ride-hailing service. What is the probability the commuter takes at least one ride on a given day?
What is the probability that a commuter takes both the morning and evening rides on the same day, making them a 'committed' rider?
A rider uses the service on Day 1. What is the probability they take at least one ride again on Day 2, given that days are independent and follow the same model?
What is the probability that a new rider becomes a 'permanent' rider within two days, defined as being a committed rider (both trips) on at least one of Day 1 or Day 2?
Given that a rider took at least one ride on Day 2, what is the probability they took no evening (high-priced) ride on Day 1?
How would the answers change if morning and evening trip decisions within a day were positively correlated rather than independent?
Across N independent commuters, what is the distribution of the number who become committed riders on a given day? What are its mean and variance?
If you observed the empirical fraction of committed riders in real data, how would you estimate p and construct a confidence interval around it?

“Complement is the move here, 1 minus the probability of skipping both trips.”

View Post

Lyft·Data Scientist·Technical Phone Screen

Jun 2026

Lyft data science interview with a probability/Markov chain question built around their dynamic pricing feature. The setup was clever and felt more applied than the usual brain teaser, but it still required you to actually know your probability fundamentals under pressure.

Lyft is running a dynamic pricing trial. A rider takes two rides on day one, and each ride has probability P of being priced reasonably. Based on their day-one experience, what is the probability they take exactly one ride the next day? And what is the probability they become a permanent daily rider?

“The setup took me a minute to parse.”

View Post

Lyft·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Lyft system design round focused entirely on a pagination API problem. Pretty deep dive, more than I expected for a single question.

You have a large table of transaction records with fields like id, userId, amount, and createdAt. Design APIs to fetch transactions in reverse chronological order with pagination. You need to support both offset-based and cursor-based pagination using (createdAt, id) as the cursor. The response should include metadata like hasNext, nextCursor, and total count for offset mode. Also handle timestamp ties, and explain how you'd keep results stable when new records are inserted between page requests.

“The cursor-based part is where I spent most of my time and honestly where things got interesting.”

View Post

Lyft·Software Engineer·Technical Phone Screen

Jun 2026

Lyft software engineer coding round with two algorithm problems. Both were medium-to-hard difficulty and felt like they were testing whether you actually think through edge cases rather than just knowing the pattern.

Given two strings s and t, find the shortest contiguous substring of s that contains every character in t with at least the same frequency. Return an empty string if no such substring exists.
You have a list of jobs, each with a start time and duration occupying a half-open interval. Assign all jobs to workers such that no worker has overlapping jobs, using the minimum number of workers. Return the worker assignment for each job in the original input order.

“Classic sliding window but the multiplicity part tripped me up at first.”

View Post

Lyft·Software Engineer·Technical Phone Screen

Jun 2026

One coding round for a software engineer role at Lyft, about an hour long but reportedly wrappable in half that time. Just the one problem, no follow-ups, pretty low-pressure as these things go.

Design and implement an LRU cache with O(1) get and put operations, including eviction of the least recently used entry when capacity is exceeded.

“Classic hashmap plus doubly linked list combo.”

View Post

Lyft·Data Scientist·Onsite - Product Sense / Strategy

Jun 2026

Third round at Lyft for a Data Scientist role was a business case study, and I walked out pretty sure I'd bombed it. HR confirmed shortly after that they weren't moving me forward.

Prime Time pricing is stable across three consecutive weekends, then suddenly spikes in week 4. How do you investigate the root cause?

“I think I went too narrow too fast, jumped straight to demand-side stuff like a big local event and didn't structure it well before talking.”

View Post

Lyft·Data Scientist·Onsite - Behavioral / Leadership

Jun 2026

Lyft data scientist interview that covered two pretty different areas: handling a vague, poorly guided case with a hard-to-understand interviewer, and a full comp negotiation scenario. Both felt more like situational judgment tests than anything technical.

Walk me through a time you worked on an open-ended project or interview where the other person had a strong accent and gave very little direction. How did you figure out what the actual problem was, set measurable success criteria, and avoid wasting time on things that didn't matter?
Describe a situation where your salary expectations didn't match what the role was offering. How did you prepare your range with data, handle the moment when they anchored low, and negotiate things like signing bonus or equity without damaging the relationship?

“This one was uncomfortable to answer because you have to be careful not to sound like you're complaining about the interviewer's accent.”

View Post

Lyft·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

Lyft PM interview with a single product sense question about driver tipping behavior. Pretty focused session, no fluff.

Only 1 in 5 riders tips their driver after a ride. How would you improve this?

“My first instinct was to jump straight into feature ideas, which was probably wrong.”

View Post

Lyft·Data Scientist·Technical Phone Screen

Jun 2026

Interviewed for a Data Scientist role at Lyft. One probability question that sounds straightforward until you realize you need to set up the conditional correctly.

A rider takes Lyft home. What's the probability they also took Lyft to work?

“I knew this was a Bayes setup but fumbled the direction of conditioning for a second.”

View Post

Lyft·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Lyft ML engineer interview that went deep on model diagnostics. The core question was a multi-part case study on bias-variance tradeoffs and remediation strategies, which sounds manageable until you're actually in it trying to reason through five different error scenarios on the fly.

You're given five pairs of train and test error measurements from different models. For each pair, identify whether the model is underfitting, overfitting, well-fit, or producing noisy/unreliable results, and explain your reasoning. Then walk through concrete techniques to fix overfitting and connect each fix back to the specific error pairs.

“This one took longer than I expected to set up mentally.”

View Post