Company
Lyft interview questions
52 practice questions in the style of Lyft's interviews, covering Statistics & Math, Behavioral & Leadership, Coding & Algorithms, System Design, Software Engineering Fundamentals, Analytics & Experimentation, Machine Learning, Data Manipulation (SQL/Python).
5 easy40 medium7 hard
Lyft interview questions by the numbers
Last updated
Katkat has 52 Lyft interview questions. The largest topics are Coding & Algorithms (27%), System Design (15%) and Analytics & Experimentation (13%). By difficulty: 10% easy, 77% medium and 13% hard. The most common round is Onsite (67%). Frequent concepts include Causal Inference, Experimentation, Funnel Analysis and Metrics.
Topics
- Coding & Algorithms27% · 14
- System Design15% · 8
- Analytics & Experimentation13% · 7
- Behavioral & Leadership12% · 6
- Statistics & Math12% · 6
- Machine Learning10% · 5
Difficulty
- Easy10% · 5
- Medium77% · 40
- Hard13% · 7
Interview rounds
- Onsite67% · 35
- Technical Screen31% · 16
- Online Assessment2% · 1
Roles
- Software Engineer58% · 30
- Data Scientist35% · 18
- Machine Learning Engineer8% · 4
Frequent concepts
- Causal Inference4% · 2
- Experimentation4% · 2
- Funnel Analysis4% · 2
- Metrics4% · 2
- analytics2% · 1
- bayes-theorem2% · 1
Most mentioned in interview experiences
- 1.Assign Tasks to the Minimum Number of Workers2 reports
- 2.Wrapper Over a Paginated Page API That Fetches the Next N Words2 reports
- 3.Compute Poisson supply–demand match probability1 report
- 4.Demonstrate leadership under ambiguity1 report
- 5.Design a Distributed Web Crawler1 report
- 6.Design a Globally Versioned Key-Value Store1 report
- 7.Design a One-to-One Chat Service1 report
- 8.Design a scalable real-time chat system1 report
- 9.Design a Wiki Crawler That Keeps Every Stored Page at Most Five Days Stale1 report
- 10.Design experiments for marketplace balance1 report
Counted from 6 candidate interview experiences on Katkat. How we collect and count
Showing 31–52 of 52 results
This question evaluates skills in grid-based propagation modeling and stateful transactional system design, testing concepts such as graph traversal and timed spread dynamics for the grid task and nested transaction semantics, isolation, and state management for the in-memory key-value store.
LyftSoftware EngineerCoding & AlgorithmsOnsiteA live coding exercise that asks you to implement k-means clustering from scratch in Python, with NumPy optional, and make it pass the interviewer's test cases. It tests the assignment and update steps, initialization, convergence, empty clusters and writing runnable code under time pressure.
LyftMachine Learning EngineerMachine LearningTechnical ScreenImplement a stateful fetchN wrapper over a paginated upstream that returns items in source order across repeated calls. Define buffering, page-token progression, exhaustion, empty pages, invalid input, and retry behavior without losing or duplicating items.
LyftSoftware EngineerSoftware Engineering FundamentalsOnsiteImplement an in-memory string key-value store with lookup, assignment, deletion, value counts, and deeply nested transactions. Define visibility plus exact begin, rollback, and inner or outer commit behavior without copying the entire database per transaction.
LyftSoftware EngineerCoding & AlgorithmsOnsiteThis question evaluates a candidate's ability to design efficient in-memory data structures and implement transactional semantics for operations like SET/GET/DELETE/COUNT, including handling nested transactions, rollbacks, and commits.
LyftSoftware EngineerCoding & AlgorithmsOnsiteImplement paginated retrieval of transactions evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
LyftSoftware EngineerCoding & AlgorithmsOnsiteA coding question to implement an in-memory key-value store with begin, set, unset, commit and rollback, where transaction blocks can be nested and committed changes can no longer be rolled back. It tests how state is recorded per block, restoring keys that were absent, nested commit semantics, and operation complexity.
LyftSoftware EngineerSoftware Engineering FundamentalsOnsiteInvestigate Causes of Driver WOW Score Drop evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
LyftData ScientistAnalytics & ExperimentationOnsiteThis question tests your ability to diagnose a sudden drop in a core business metric, distinguish between technical tracking issues and product-driven behavior, and design a strategy to evaluate coupon effectiveness.
LyftData ScientistAnalytics & ExperimentationTechnical ScreenInvestigate Sudden Metric Changes and Design A/B Test evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
LyftData ScientistAnalytics & ExperimentationTechnical ScreenTests your ability to conduct a structured root-cause analysis on simultaneous marketplace metric regressions, decomposing supply-demand dynamics and separating correlation from causation.
LyftData ScientistAnalytics & ExperimentationTechnical ScreenTests the sliding window technique and frequency counting to find the shortest substring containing all required characters with their exact multiplicities in linear time.
LyftSoftware EngineerCoding & AlgorithmsOnsiteThis question evaluates spatial algorithms and real-time optimization for ride dispatch together with interval scheduling and capacity planning competencies, covering skills in computational geometry, routing, demand forecasting, and temporal overlap reasoning.
LyftData ScientistCoding & AlgorithmsOnsiteThis question evaluates mastery of data manipulation and analytics skills in the Data Manipulation (SQL/Python) domain, including SQL aggregation and window functions, time-based joins and grouping, deduplication of status streams, handling late-arriving events, and implementing rolling metrics using both SQL and pandas.
LyftData ScientistData Manipulation (SQL/Python)OnsiteTests understanding of how an additive shift to the intercept of a logistic regression model impacts predicted probabilities, ranking metrics (ROC-AUC), thresholded classification metrics (Recall, FPR, Precision), and calibration.
LyftMachine Learning EngineerMachine LearningTechnical ScreenReconstruct the exact binary search tree represented by a preorder traversal of unique integers. Handle empty and completely skewed inputs at scale while preserving the intended tree rather than balancing it.
LyftSoftware EngineerCoding & AlgorithmsOnsite- Rotting OrangesMedium
Compute how many simultaneous spread steps are needed to rot every reachable orange using multi-source grid traversal.
LyftSoftware EngineerCoding & AlgorithmsOnsite Tests using the two-pointer sliding window pattern combined with frequency counting to find the shortest substring satisfying multiset inclusion constraints in linear time.
LyftSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates proficiency in graph traversal and grid-based simulation, specifically multi-source breadth-first search, state propagation modeling, and algorithmic complexity analysis within the Coding & Algorithms domain, emphasizing practical application of implementation and reasoning.
LyftSoftware EngineerCoding & AlgorithmsOnsiteThis pair of problems evaluates competencies in string processing and multiplicity handling as well as scheduling and resource-allocation for interval tasks, testing the ability to choose and apply appropriate data structures while managing time and space complexity.
LyftSoftware EngineerCoding & AlgorithmsOnsiteA machine learning fundamentals screen that asks you to diagnose models from pairs of training and test error, including the unusual case where the test error is the lower one. It continues with curbing overfitting in linear, tree-based and neural network models, and with setting up validation splits and k-fold cross-validation.
LyftMachine Learning EngineerMachine LearningTechnical ScreenA coding question that wraps an external paginated API, where each page returns a variable number of words, behind a fetch(n) method that returns the next n words in order. It tests handling words left over between calls, requests that span several or empty pages, lazy fetching, the end of the content, and API failures.
LyftSoftware EngineerSoftware Engineering FundamentalsOnsite
Lyft interview experiences
All 9 →- Messenger Design and a Next-Day PassLyft · Software Engineer · Senior+ · Onsite · Sep 2026
The target level was Senior. The process was bizarre, but I'll leave that aside. Overall, the interviews weren't difficult. Surprisingly, the hardest coding problem was in the phone screen. Phone-screen coding: LeetCode 76. VO 1: The behavioral round. They asked about my past projects, which project I was proudest of, how I had moved projects forward with colleagues over the past two years, and s…
- Wiki Crawler Design and a Talent Pool RejectionLyft · Software Engineer · Onsite · Sep 2026Rejected
The phone screen was the typical one: they give you an API that can fetch pages, and you write a wrapper that calls this external API to implement fetching by word count. Onsite, showtime. The system design was wiki crawling: how do you crawl all of the wiki's content and store it, while keeping it updated within a certain time window, for example no more than five days stale. The coding was the…
- 75-Minute Phone Screen with Train/Test Error Analysis and K-Means from ScratchLyft · Machine Learning Engineer · Technical Screen · Jul 2026In progress
75 min. The first part was ML. They gave me 5 sets of training/test error and I had to analyze the possible causes. The cases included training high / test low, training low / test high, both low, and both high. I hadn't prepared for the training high / test low case and got stuck for a bit. The interviewer hinted that the train and test data might have different distributions, or that the traini…
- Lyft Data Scientist interview: probability to causal modelingLyft · Data Scientist · HR Screen · Jul 2026
I began with a recruiter screen of about 30 minutes. It was structured: they checked the basic boxes and explained what would happen next. The process then moved through a general data-science screen on probability, A/B testing, and business sense, followed by four deeper technical rounds. Those covered coding and algorithms, optimization, causal modeling, and business acumen tied back to product…
- Lyft Software Engineer Interview Experience: A transactional recruiter screenLyft · Software Engineer · HR Screen · Jun 2026
The recruiter screen set a rough tone immediately. I came in for a backend engineering role, but the conversation felt overly transactional, as though boxes were being checked instead of discussing the technical impact I had delivered. I shared concrete examples from past work, including architecture decisions, optimizations, and engineering scenarios. I expected the conversation to connect those…
More companies
- Meta666
- Amazon653
- Google486
- OpenAI342
- Capital One268
- Microsoft252
- DoorDash241
- Anthropic225
- Uber217
- Apple177
- TikTok176
- Pinterest161
- ByteDance160
- LinkedIn154
- Stripe139
- Snowflake130
- Databricks122
- Airbnb112
- Rippling106
- Oracle104
- Coinbase99
- Netflix97
- NVIDIA95
- Snapchat94
- Citadel90
- Waymo90
- Instacart87
- Roblox84
- Salesforce77
- Optiver76
- Shopify63
- Robinhood60
- Atlassian55
- Hudson River Trading55
- Two Sigma55
- J.P. Morgan53
- PayPal53
- xAI53
- Tesla52
- Other51
