DoorDash Senior Data Engineer Interview (L5)
At DoorDash, the (L5) Senior Data Engineer interview is characterized by Marketplace logistics with last-mile optimization and fast-paced consumer engineering. To clear this bar you need independent technical leadership and cross-team influence, built on 5-8 years of production DE work.
Compensation
$210K–$260K base • $380K–$530K total
Loop duration
4 hours onsite
Rounds
5 rounds
Location
San Francisco, NYC, Seattle, Tempe, Toronto
Tech stack
What DoorDash senior data engineers actually use
What DoorDash currently advertises as required for data engineer roles. Chips link into tool-specific interview guides.
Round focus
Domain concentration by round
Per-round concentration of each domain in DoorDash's interview, derived from the skills emphasized across 6 current senior data engineer postings. Higher bars mean more questions of that type in that round.
Online Assessment
Phone Screen
Onsite Loop
Walk into DoorDash knowing the Python pattern they'll test.
Practice problems
DoorDash senior data engineer practice set
DoorDash senior data engineer practice set, mapped from predicted domain emphasis. Tap into any problem to work it in the live environment.
Subscribers Without Premium
Pull basic-plan subscribers who never upgraded to premium from the subscriptions data. The retention team wants to run a winback campaign targeting this group.
The Overlap
Your monitoring system logs server maintenance as `[start, end]` minute ranges, and windows that overlap or sit back-to-back really describe one continuous outage. Collapse the `windows` so any that overlap or touch at an endpoint become a single range, and return them ordered by start time. Two windows touch when one ends exactly where the next begins.
Nth Largest Value
The compensation team needs the second-highest unique metric value in the performance table as a benchmark for setting the next salary band. Return that single value, or NULL if the data does not have enough unique values.
Letters in the Noise
A text-cleaning step in your pipeline needs a per-letter tally of the raw strings flowing through it. For a given `s`, return how many times each letter appears, treating uppercase and lowercase as the same letter and ignoring any character that is not a letter. Give the results as `[letter, count]` pairs in lowercase, ordered alphabetically.
Daily signup-to-purchase funnel
Count signups and first-time purchases per day. Product-company favorite.
Where the Line Breaks
Every batch has a last piece. Mark it right.
Pulled from debriefs where Python parsing was the gate.
The loop
How the interview actually runs
01Recruiter screen
30 minDoorDash operates at marketplace + logistics scale. Track splits: Consumer, Merchant, Dasher (driver), Logistics, Ads, International.
- →Three-sided marketplace (consumer, merchant, dasher) — acknowledge the complexity
- →Logistics teams are the most data-intensive
- →DoorDash ships fast; Amazon/Uber-comparable velocity
02Technical phone screen
60 minSQL + Python with marketplace + logistics data. Order funnels, dasher earnings, restaurant performance, delivery time analysis.
- →Marketplace matching SQL (assigning orders to dashers) appears
- →Time-window calculations (estimated delivery time vs actual) are common
- →Know three-sided-marketplace metrics: take-rate, fill-rate, contribution margin
03Onsite: marketplace design
60 minDesign a pipeline for a marketplace or logistics problem: ETA prediction, surge pricing, dasher routing, merchant analytics.
- →Real-time is central; batch is backup
- →Geospatial data (H3 hexagons, route optimization) is fair game
- →Discuss marketplace incentive design alongside technical design
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 + fit
45 minDoorDash's culture is high-velocity, operator-minded, and quantitative. Stories about moving fast and measuring everything land well.
- →DoorDash's 'One DoorDash' framing — stories about cross-team wins
- →Acknowledge dasher/consumer/merchant tradeoffs explicitly
- →Avoid stories about slow, methodical work
Level bar
What DoorDash expects at 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.'
DoorDash-specific emphasis
DoorDash's loop is characterized by: Marketplace logistics with last-mile optimization and fast-paced consumer engineering. Calibrate your preparation to that, generic FAANG prep will not close the gap on company-specific expectations.
Behavioral
How DoorDash frames behavioral rounds
Make room to grow
DoorDash's culture explicitly rewards career ambition and skill-stretching.
Seek truth, speak candidly
DoorDash values direct communication even when uncomfortable.
Think outside the room
Marketplace engineering requires thinking about unseen stakeholders (dashers, customers, restaurants).
Take smart risks
DoorDash's growth came from calculated bets. They want calibrated risk-taking.
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, DoorDash weights this round heavily
- ·Read DoorDash'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+ DoorDash-style problems in their domain
- ·Time yourself: 25 min per medium, 35 min per hard
- ·Record yourself narrating approach aloud, communication is graded
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 DoorDash'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 DoorDash 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 interview guides
FAQ
Common questions
- What level is Senior Data Engineer at DoorDash?
- Senior Data Engineer maps to L5 on DoorDash's engineering ladder. This is an individual contributor level; expectations focus on independent technical leadership and cross-team influence.
- How much does a DoorDash Senior Data Engineer make?
- Total compensation for DoorDash Senior Data Engineer ranges $210K–$260K base • $380K–$530K total. Ranges shift by team and negotiation.
- How is the Senior Data Engineer loop different from other levels at DoorDash?
- The rounds look similar, but the bar calibrates to seniority. Senior Data Engineer is evaluated on independent technical leadership and cross-team influence. Questions at this level probe independent system design and cross-team influence.
- How long should I prepare for the DoorDash Senior Data Engineer interview?
- Plan for 8-10 weeks of prep if you're already a working DE. Under 4 weeks rushes the behavioral prep, which takes the most time.
- Does DoorDash interview data engineers differently than software engineers?
- They differ meaningfully. DoorDash's DE loop has heavier SQL, replaces the general system-design with a data-specific one (pipelines, warehouse design), and expects production data ops experience.