Design a latency budget for a multi-step agent workflow.

Instruction: Describe how you would budget latency across planning, retrieval, tool use, and generation. Measured single-request trace: intake 0.1 s, retrieval 0.4 s, planning 0.6 s, two required tools in parallel taking 0.8 s and 1.2 s, then generation 0.5 s. Overall deadline is 3.0 s with 0.2 s delivery reserve. Compute critical-path duration and slack; distinguish this from adding stage p95 values.

Context: Assesses whether the candidate can design a practical architecture and explain the main tradeoffs. Describe how you would budget latency across planning, retrieval, tool use, and generation.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would work backward from the user promise and give the request an overall deadline. Intake, retrieval, model turns, tools, and final delivery need budgets within that deadline, including room for a useful fallback...

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions