from/prod
← All companies

THE COMPANY INDEX TRACKED BLOG

Lyft

Ideas, decisions, and lessons from the team.

eng.lyft.com (opens on the source site)LinkedIn X
12Posts tracked
last monthLatest publication
1.0Posts / month over the last 12 months

Latest writing

12 of 12 posts

Refreshing the Travel-Time Map Behind Lyft’s Marketplace: Rebuilding Neighborhood Reachability… (opens on the source site)

Refreshing the Travel-Time Map Behind Lyft’s Marketplace: Rebuilding Neighborhood Reachability SignalsEvery time Lyft calculates pricing to balance a market, nudges a driver toward an under-served pocket of a city, or paints a heatmap of where demand is building, there is a quiet lookup table doing work in the background. It answers a deceptively simple question: how long does it take to get from here to there?, for millions of pairs of places, across hundreds of regions.That lookup table is the Neighborhood Reachability Signal, and for years large parts of it were frozen in a snapshot of the…

Read at the source

Rerouting the Stream: How Lyft Moved to the Apache Flink Operator (opens on the source site)

Written by Maheep Myneni, Arda Kuyumcu, and Prem Santosh Udaya Shankar at Lyft.Why We Migrated: Technical Debt Meets Modern Streaming DemandsOver the past several quarters, Lyft’s Streaming Compute team retired our internally developed Flink Kubernetes operator and moved our entire streaming fleet onto the open-source Apache Flink Kubernetes operator. This post is about why we made the switch, how we pulled it off incrementally without disrupting users, and the follow-on work it took to actually get the benefits we were after.Back in 2020, when we first architected the Lyft Flink Kubernetes…

Read at the source

From Day 1 to Production: Building Lyft’s Analytics & Rides Intelligence Assistant as Onboarding… (opens on the source site)

From Day 1 to Production: Building Lyft’s Analytics & Rides Intelligence Assistant as Onboarding ProjectWritten by Sagar Baronia at Lyft.A Different Kind of Day OneMost onboarding journeys follow a familiar arc: orientation sessions, benefits enrollment, setting up your laptop, and gradually finding your footing over the first few weeks. Mine followed that arc too, but with an additional thread running alongside it from the very start.I joined Lyft in March 2026 as a Senior Data Scientist — Algorithm on the Marketing, Business & Ads team, bringing close to a decade of experience in data…

Read at the source

Metric Semantic Layer: How Lyft Governs and Scales Key Data Definitions (opens on the source site)

Written by Rohit Channe and Simran Mirchandani at Lyft.MotivationAt Lyft, data isn’t just a resource — it’s woven into everything we do. Metrics drive key forecasts, steer operational decisions, and put our boldest hypotheses to the test. But as Lyft scaled, products launched and evolved, and team members came and went, we found ourselves at risk of different teams using different definitions for a given metric. What did “Metric ABC” actually mean? The answer often depended on the context and application of the team you asked.The consequences were predictable. Without centralized version…

Read at the source

From Chaos to Clarity: How We Built a Unified, Self-Routing Support Ops Ticketing System at Lyft (opens on the source site)

Written by Atul Gupta, Analytics Manager — LUS Support Ops, LyftAt Lyft, getting operators and riders connected quickly and reliably depends on more than technology — it depends on the teams working behind the scenes to keep that technology running smoothly. For the operators managing Lyft’s fleet across markets, having fast, reliable access to support is what keeps bikes on the road, stations stocked, and issues resolved before they affect riders. Building the infrastructure that makes that support possible is what our team does; this is the story of how we built it.When I first joined Lyft…

Read at the source

How We Built a Smarter Pickup Experience for Gated Communities (opens on the source site)

If you live in a gated community, you’ve been there: You request a ride from your apartment complex, expect your driver to come to you as usual, and then — your driver’s car icon just stops right at the front gate. You watch helplessly as the ETA ticks up. A chat message comes in: “Hey, how do I get in?” You scramble to remember the gate code. They try it. It doesn’t work. You end up meeting them awkwardly on the sidewalk outside while your coffee gets cold — a pickup journey frustrating for both you and your driver.An example gated community in real life, Photo by Bingqian Li on PexelsIt…

Read at the source

Predicting Rider Conversion in Sparse Data Environments with Bayesian Trees (opens on the source site)

At Lyft, understanding how riders go through our user experience is fundamental to operating a healthy marketplace. Specifically, it is important to have a robust model determining if a rider will actually request a ride after entering a destination and viewing a price and ETA. Accurately predicting this decision, that we call conversion, informs countless decisions across our platform. Whether it is to better balance supply and demand, improve user experiences, optimize recommendations and advertisement, understand long-term engagement, decide how to distribute coupons… rider conversion…

Read at the source

Beyond A/B Testing: Using Surrogacy and Region-Splits to Measure Long-Term Effects in Marketplaces (opens on the source site)

Image generated with Gemini 3 Pro (Google), 2026.Written by Amber Wang and Yoonji Kim at Lyft.BackgroundWhenever you use the Lyft app, there is a complex balancing act happening behind the scenes. Various levers are used to keep the marketplace running smoothly; Base prices and coupons for riders affect demand, while driver pay and bonuses impact the level of available supply. Since every change to prices and payments impacts Lyft’s costs and revenue, they lead to key optimization problems, such as:How should we allocate budget between driver incentives and rider incentives?How do we invest…

Read at the source

Scaling Localization with AI at Lyft (opens on the source site)

Written by Stefan ZierFor years, Lyft’s localization infrastructure relied exclusively on human translation. While this model usually ensured excellent quality, it was bound by multi-day turnarounds and costs that scaled linearly with every new language. For the few languages Lyft initially supported (Spanish, Portuguese, and French), these limits were acceptable.However, Lyft’s expansion goals quickly outpaced what traditional workflows could support. Lyft’s recent Québec launch required compliance with Bill 96 (legislation mandating French-first user experiences) which demanded faster…

Read at the source

Trusting the Untestable: Validation and Diagnostics for the Doubly Robust Models (opens on the source site)

written by Ross Chu and Shima NassiriThe Causal Frontier: Measurement Beyond RandomizationThe gold standard for determining the causal impact of a policy or product change at a company like Lyft is the A/B test (randomized experiment). By randomly assigning users to a treatment or control group, A/B tests inherently eliminate bias, providing clean estimates of the Average Treatment Effect (ATE). However, many critical business questions and large-scale initiatives simply cannot be randomized. This forces scientists to move past traditional experimentation and leverage quasi-experimental…

Read at the source

Lyft’s Feature Store: Architecture, Optimization, and Evolution (opens on the source site)

Written by Rohan Varshney, with support from Devon Mittow & Janice Lee.This article expands upon a presentation from the Feature Store Summit 2025, which can be viewed in full here. There is also another video available on the evolution of Lyft’s Feature Store from DE4AI 2024.Introduction and Core PurposeLyft’s Feature Store stands as a core infrastructural pillar within its Data Platform organization, designed to optimize the management and deployment of Machine Learning (ML) features at massive scale. Its primary objective is to centralize feature engineering efforts, guaranteeing…

Read at the source

From Python3.8 to Python3.10: Our Journey Through a Memory Leak (opens on the source site)

Image generated with ChatGPT (OpenAI), 2025.IntroWhen working with Python, memory management often feels like a solved problem. The garbage collector quietly does its job, and unlike C or C++, we rarely think about malloc or free. This doesn’t mean that there are no memory leaks in Python. Reference cycles, unreleased resources like connection pooling, global caches, etc can slowly inflate your process’s memory footprint. You might not notice it at first, until your worker starts OOM-ing, latency creeps up, or container restarts become mysteriously frequent.In this post, we’ll share the story…

Read at the source

Privacy choices

Reading never requires analytics. These choices last 90 days on this browser.

Essential sign-in and security storage always stays on. Read the privacy notice.