Went through the DoorDash frontend engineer interview loop in early 2026 for an IC4 (senior) consumer web position. Sharing notes because the frontend-specific content online is thin.
The loop was 5 rounds total:
Coding round 1 (general algorithms): Pretty standard medium-difficulty Leetcode. Mine was a tree traversal with some state tracking. Could use JS or any language. I used JavaScript because I wanted to demonstrate familiarity with the runtime.
Coding round 2 (frontend-specific): This is the interesting one. I was asked to build a small React component from scratch in a shared editor (no JSX tooling, just vanilla JS/HTML-ish environment). The problem was something like rendering a nested comment thread with expand/collapse functionality. They care about component decomposition, event handling, and state management approach. Not UI prettiness.
System design for frontend: Roughly an hour, asked to design a real-time order tracking UI. Topics that came up: websockets vs polling, how to handle stale data, performance on low-end Android devices (huge for DoorDash given the dasher app), and caching strategies on the client. They were genuinely curious about my reasoning, not looking for a specific answer.
Behavioral: Standard DoorDash format. Two interviewers tag-teaming. Heavy on cross-team collaboration and dealing with ambiguous requirements.
Hiring manager: Conversational. Vision for the team, why DoorDash, how I think about technical quality vs. shipping speed.
Strength signals they seemed to respond well to: knowing the browser event loop cold, having opinions on accessibility (not performative opinions, actual a11y experience), and being curious about the mobile web performance work they're doing.
I got an offer at IC4, Bay Area, base was around $185k. The RSU package was meaningful but the vest schedule is 1-year cliff then monthly, which I liked.
Total timeline: 3.5 weeks recruiter screen to offer letter.