Explain it in English
Speak the answer against the clock, then reveal the gold answer and tick the phrases you actually said. These are the lines the pair + design rounds grade.
0/14 done
- AI is allowed — how you use itai-enabledThis round allows AI. How will you use it, and how do you keep ownership of the solution?75s
- Design the offer APIapi-designDesign the REST API for offers on homes.90s
- Default architecture stance (system design opener)system-designWhat's your default architecture for a stateful domain service at Opendoor?75s
- Distributed lock — no double execution (SK AX)resumeHow did you stop a scheduled job from running twice across instances?75s
- Status codes: 404 / 409 / 400 (never 500 for a rule)errorsWhat HTTP status codes does your offer API return, and when?60s
- Async LLM pipeline + state machine (Mimi)resumeTell me about the async LLM pipeline and why it has explicit states.90s
- PK-only payload + fresh-state retrieval (SK AX)resumeWhy send PK-only payloads with fresh-state retrieval instead of the full object?75s
- LLM provider abstraction (Mimi)resumeWhy did you put the LLM provider behind an interface?60s
- Row-level lock — duplicate IDs (SK AX)resumeWalk me through the duplicate-ID-generation fix.75s
- How you open a coding problemcommunicationYou're given a coding problem in the pair round. Talk me through your first 30 seconds.45s
- Staging table + batch worker (SK AX)resumeTell me about decoupling the online transaction from downstream financial processing.90s
- TCP message framing (Dure Info)resumeYou hit XML deserialization failures over TCP. What was actually wrong?60s
- Template Method + dynamic factory (8 sites)resumeHow did regional teams customize a shared workflow without forking it?60s
- The transition endpoint (the crux)api-designWhy expose a separate POST /offers/{id}/transitions endpoint instead of just PATCHing the offer? Walk me through one transition.90s