RepostedDoorDash logo

DoorDash · Phone screen

Rejected

DoorDash SWE Phone Screen: Bootstrap API in Java: 1 Experience

Software engineer · Full-timeMaster's degreeReported Nov 18, 2026
Shared byjanebeingjane

A 2026 DoorDash code craft phone screen in Java: merge three upstream APIs into one bootstrap response; status codes and partial failures are the hard bit.

At a glance

  • Process: one code craft phone screen after a recruiter reached out (report 01)
  • Asked recently: the bootstrap API, merging consumer, payment and address services (report 01)
  • Difficulty: the candidate rated it average and did not pass
  • Practise first: Customer Bootstrap API

Coverage: One candidate with a Master's degree who came in through a recruiter. The report covers one technical phone screen. It gives October to December 2026 as the interview period and went up on November 18, 2026.

What came up

Writing the happy path was easy. The questions that mattered were about failures: what counts as an error, which failures sink the whole response, and what to do about retries, timeouts and concurrency.

Topic Reports Last seen
Code craft: combine three upstream responses 1 of 1 Nov 2026 (report date)
Follow-ups: retries, timeouts, partial responses 1 of 1 Nov 2026 (report date)

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Build one bootstrap response from consumer, payment and address services (practice) 1 Nov 2026 (report date)

1 detailed candidate timeline, loops, and screens

01: SWE, code craft phone screen

Interview period: 2026 Q4 · Report date: November 18, 2026 · Role: Software engineer · Degree listed: Master's · Channel: Recruiter · Candidate's rating: Neutral experience, average difficulty · Result: Did not pass

  1. The task. In Java on a shared coding platform. Three upstream services, consumer, payment and address, already have their APIs; combine their results into one response. FastPrep's practice version is Customer Bootstrap API.
  2. The tricky part. Catching exceptions isn't enough; you also have to check whether each HTTP status is in the 2xx range. If the consumer call fails, the whole request can return 500. If payment or address fails, keep the other fields.
  3. Follow-ups. Retry a failed call or drop it? How to handle timeouts and partial responses? Does the address include first and last names?
  4. Where it went wrong. The candidate hadn't written Java concurrency in a long time and got stuck there, and only ran the happy-path test.

Result

The candidate did not pass, and felt beforehand that it had probably gone badly.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.