注册一亩三分地论坛,查看更多干货!
您需要 登录 才可以下载或查看附件。没有帐号?注册账号 
x
第一轮 debugging:是关于 dasher random pick 地里也有类似的 这个做的不好 花时间太长了 然后follow up 就是一些上production 有哪些要注意的 改动的 之类的 没有问consistent hashing
第二轮 system design:food review 那道题
第三轮 ai coding:地里原题 没有starter code 有DAG 的
At DoorDash, when something goes wrong with an order — delayed, lost, undelivered — support agents need to respond consistently. We want a system that can evaluate an order's current state and automatically decide what action to take: issue a refund, close the request, escalate, etc.
Our system would function by querying a real API that you build to represent order status, checking the order status, and following a rule set defined as a directed acyclic graph to make a decision.
An example DAG could look like this:
Start Node
│
▼
Check if the order is late?
├── Yes ──▶ Issue Refund ──▶ End
└── No ──────────────────▶ End
第四轮 BQ:跟这里问的差不多 https://www.1point3acres.com/interview/problems/company/doordash/hm-behavioral-round |