← DoorDash Interview Insights

DoorDash·Frontend Engineer·Onsite - System Design / Architecture·Intermediate

IntermediateRejected
May 2026

Summary

Applied for a frontend role at DoorDash and got thrown into a system design round first, which already felt off. The focus on database internals was brutal for someone coming from a frontend background, and I never heard back after.

Questions Asked (1)

Q1

Design a photo-sharing platform like Instagram, with particular attention to how the system handles posts from accounts with massive follower counts.

System DesignData ModelingTechnical Trade-offs
Author's notes

Not what I was expecting as a frontend engineer.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then focus on the fan-out problem for high-follower accounts. Propose a hybrid approach (push for normal users, pull for celebrities) and discuss frontend implications like feed consistency, loading strategies, and caching.

Pro tip: Emphasize that the frontend must handle eventual consistency gracefully—e.g., showing a 'loading' state for celebrity posts—and discuss how to prioritize content to avoid overwhelming the client.

1. Clarify requirements and scale

Ask about expected user count, follower distribution, and read/write patterns. Establish that the core challenge is delivering posts from high-follower accounts efficiently.

2. Explain the fan-out problem

Describe push (write fan-out) vs pull (read fan-out) models and why neither alone works for celebrities. Highlight the trade-offs in latency, storage, and consistency.

3. Propose a hybrid approach

Suggest push for normal users and pull for high-follower accounts, with a threshold. Discuss how the frontend merges these sources into a single feed.

4. Address frontend implications

Cover feed loading strategies (pagination, infinite scroll), caching, optimistic UI, and handling eventual consistency (e.g., placeholder for celebrity posts).

5. Discuss trade-offs and optimizations

Mention caching layers (CDN, Redis), precomputation, and how to prioritize content. Summarize key trade-offs and potential bottlenecks.

Key Points to Mention

  • Fan-out on write vs read and the celebrity problem
  • Hybrid approach with a follower threshold
  • Feed merging and ranking on the client
  • Caching strategies (CDN, in-memory) for hot content
  • Handling eventual consistency and loading states in UI
  • Pagination and infinite scroll for large feeds

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.