Lyft Senior Data Engineer Interview (L5)
The Lyft Senior Data Engineer interview (L5) is built around Rideshare marketplace with scrappier culture than Uber and bike/scooter/AV diversification. Successful candidates show independent technical leadership and cross-team influence over 5-8 years of data engineering.
Compensation
$195K–$240K base • $350K–$490K total
Loop duration
4 hours onsite
Rounds
5 rounds
Location
San Francisco, NYC, Seattle, Toronto, Minneapolis
Compensation
Lyft Senior Data Engineer total comp
Offer-report aggregate, 2022-2023. Level mapped: L5. Typical experience: 13-20 years (median 16).
25th percentile
$370K
Median total comp
$399K
75th percentile
$428K
Median base salary
$209K
Median annual equity
$190K
Tech stack
What Lyft senior data engineers actually use
Frequency of each tool across Lyft's open DE postings. The ones with interview prep pages are live links.
Walk into Lyft knowing the Python pattern they'll test.
Round focus
Domain concentration by round
Lyft's round-by-round focus, inferred from 6 active senior data engineer job descriptions. Use this to calibrate which domains to drill for each round.
Online Assessment
Phone Screen
Onsite Loop
Practice problems
Lyft senior data engineer practice set
Lyft-tagged practice problems for the senior data engineer level. Click any to start practicing.
Honeymoon Phase
We track customers as signup cohorts, one per registration year, to gauge how sticky each class was right after joining. Walk the cohorts from the oldest signup class forward, and for each signup year take the transactions made by that year's cohort and report the share that landed in the same calendar year the customer registered, as a percentage rounded to two decimals.
The Disputed Fare
A rider disputed a single charge that our billing system actually assembled from two separate ride legs, and finance needs to point to exactly which legs. Given `fares`, the leg charges in the order they were billed, and a disputed `target` total, give back the positions of the two legs whose charges add up to it, with the earlier leg first. When more than one such pair exists, return the one that completes earliest as you read left to right, and return `None` when no two legs account for the total.
The Other Seat
We run a ride-hailing marketplace where the same person can sign up to drive and to ride, so the model has to capture both roles without splitting one human into two records. Design the entities for drivers, riders, vehicles, and the trips that connect them, knowing that every completed trip records the fare charged, the surge multiplier that was in effect, the specific vehicle used, and a separate rating in each direction. A driver may switch vehicles between trips, and each person's displayed rating is derived from the individual ratings captured on their trips, so the per-trip ratings stay the source of truth even if a current average is also cached on the profile for fast reads.
The Path Not Taken
The product team is measuring organic adoption of the new editor, which shows up in the page views under the URL 'new_editor' while the old one appears as 'classic_editor'. Find the users who reached the new editor without ever having opened the classic editor before their first new editor visit.
Rolling 7-day active users
Count distinct users active in the trailing 7 days for each date. Product analytics staple.
The Spaces Between
Every voided trip leaves a hole in the sequence. Find the one that matters.
Pulled from debriefs where Python parsing was the gate.
The loop
How the interview actually runs
01Recruiter screen
30 minLyft is smaller than Uber and has gone through cost-cutting. Expect direct questions about your ability to operate with fewer resources.
- →Don't expect Uber-scale infrastructure; Lyft is leaner
- →Driver experience is a differentiator Lyft markets heavily
- →Bikes, scooters, and autonomous add complexity over pure rideshare
02Technical phone screen
60 minSQL with rideshare data: driver-rider matching, surge, cancellation analysis, cohort retention.
- →Practice geospatial SQL (H3 or similar hex-based)
- →Time-window analytics (peak-hour patterns) common
- →Know: ETA, supply/demand ratio, utilization, contribution margin
03Onsite: marketplace / data system
60 minDesign a rideshare system: surge pricing, driver incentives, fraud detection, ETA prediction.
- →Cost-consciousness matters; Lyft watches infrastructure spend
- →Simpler architectures beat elaborate ones at Lyft's scale
- →Acknowledge the competition with Uber directly
04System design (pipeline architecture)
60 minDesign a production pipeline end-to-end: ingestion, transformation, storage, consumers, SLAs, failure modes, backfill strategy, and cost trade-offs. At senior level, you drive the conversation without prompting. Expect follow-ups about scale, cross-team coordination, and operational load.
- →Anchor on the SLA and data shape before diagramming
- →Discuss idempotency, partitioning, and backfill explicitly
- →Estimate cost: 'This pipeline will cost roughly $X/month at this volume'
05Onsite: behavioral
45 minLyft's culture has been community-focused since the early 'pink mustache' days. Humility and collaboration signals land well.
- →Stories about helping teammates beat solo-hero stories
- →Driver empathy (not just rider) is a differentiator
- →Avoid Uber-style hustle-culture framing
Level bar
What Lyft expects at L5 Senior Data Engineer
Independent technical leadership
Senior DEs drive pipeline designs without engineering manager involvement. Interviewers probe whether you can decompose ambiguous requirements, make architecture trade-offs, and defend your choices under scrutiny.
Cross-team coordination
Senior scope regularly spans multiple teams. Expect scenarios about a downstream team missing an SLA because of a change you made, or negotiating a schema migration with the team that owns the upstream source.
Production operational rigor
Fluent in on-call, alerting, data quality checks, and incident response. Dive-deep stories at this level should include correlating a metric drop to a specific commit or a timezone bug or a subtle ordering issue, not 'I looked at the logs.'
Lyft-specific emphasis
Lyft's loop is characterized by: Rideshare marketplace with scrappier culture than Uber and bike/scooter/AV diversification. Calibrate your preparation to that, generic FAANG prep will not close the gap on company-specific expectations.
Behavioral
How Lyft frames behavioral rounds
Be yourself
Lyft's 'authenticity' value. They want genuine candidates, not corporate performers.
Uplift others
Lyft's community framing. Mentorship and teammate-enablement stories.
Make it happen
Lyft's leaner ops require engineers to ship without perfect resources.
Create fearlessly
Lyft's diversification into bikes, scooters, AV requires engineers comfortable with new domains.
Prep timeline
Week-by-week preparation plan
Foundations and gap analysis
- ·Do 10 medium SQL problems. Note which patterns feel slow
- ·Write out 2-3 behavioral stories per value, Lyft weights this round heavily
- ·Read Lyft's public engineering blog for recent architecture patterns
- ·Review your prior production work, pick 3-5 projects you can discuss in depth
SQL and coding fluency
- ·Practice window functions until DENSE_RANK, ROW_NUMBER, LAG, LEAD are reflex
- ·Do 20+ Lyft-style problems in their domain
- ·Time yourself: 25 min per medium, 35 min per hard
- ·Record yourself narrating your approach aloud. Interviewers weigh how you explain it, not only what you write
Pipeline system design
- ·Design 5 pipelines on paper: daily aggregation, clickstream, CDC, ML feature store, real-time alerting
- ·For each, write SLA, partition strategy, backfill plan, and cost estimate
- ·Practice with a friend, senior-level system design is 50% driving the conversation
- ·Review Lyft's open-source and engineering blog for in-house patterns
Behavioral polish and mock loops
- ·Rehearse every story out loud. Cut to 2-3 minutes each
- ·Run 2 full mock loops with a senior DE or coach
- ·Identify your 3 weakest behavioral areas and draft additional stories
- ·Review recent Lyft news or earnings call for fresh talking points
Taper and logistics
- ·No new content. Review your notes only
- ·Sleep. Mental energy matters more than one more practice problem
- ·Confirm logistics: laptop charged, shared-doc tool tested, snack and water nearby
- ·Remember: the loop is rooting for you to raise the bar, not to fail
See also
Related pages on Lyft's loop
FAQ
Common questions
- What level is Senior Data Engineer at Lyft?
- On Lyft's ladder, Senior Data Engineer sits at L5. Expectations center on independent technical leadership and cross-team influence.
- How much does a Lyft Senior Data Engineer make?
- Across 4 offer samples from 2022-2023, Lyft Senior Data Engineer total compensation lands at $370K (P25), $399K (median), and $428K (P75), median base $209K and median annual equity $190K. Typical experience range: 13-20 years..
- How is the Senior Data Engineer loop different from other levels at Lyft?
- Round structure is shared across levels; what changes is what each round tests. For Senior Data Engineer the emphasis is independent technical leadership and cross-team influence, with particular attention to independent system design and cross-team influence.
- How long should I prepare for the Lyft Senior Data Engineer interview?
- 8-10 weeks of focused prep is typical for candidates already working as a DE. Less than 4 weeks is tight; the behavioral story bank usually takes longer than candidates expect.
- Does Lyft interview data engineers differently than software engineers?
- Yes. DE loops at Lyft weight SQL heavier, include pipeline/system-design rounds tuned to data workloads, and probe for production data experience (ingestion patterns, data quality, backfill) that generalist SWE loops skip.
50+ guides covering every round, company, and role