Hard

Design a Multi-Agent Research System System Design Interview

Design an orchestrator-worker agent system for open-ended research with parallel search, synthesis, citations, and bounded cost.

1. Problem Statement

Design a research agent that answers broad questions by spawning parallel subagents, using web and enterprise tools, and returning a cited synthesis.

2. Architecture Discussion Map

Use this as one discussion aid, not a single correct answer. Your design should follow from the requirements, scale, and trade-offs you establish.

Rendering architecture diagram...
Mermaid Source (For AI Bots)
graph LR
    A["Design a Multi-Agent Research System"]
    A --> F1["Workflow versus agent decision"]
    A --> F2["Planner/orchestrator and subagent contracts"]
    A --> F3["Context isolation, tool access, and result provenance"]
    A --> F4["Budgeting, cancellation, retries, and partial failure"]
    A --> F5["Trace-based evaluation and quality measurement"]

3. Key Focus Areas

  • 1
    Workflow versus agent decision
  • 2
    Planner/orchestrator and subagent contracts
  • 3
    Context isolation, tool access, and result provenance
  • 4
    Budgeting, cancellation, retries, and partial failure
  • 5
    Trace-based evaluation and quality measurement

4. What Strong Candidates Should Demonstrate

  • Choose multi-agent architecture only when parallelism justifies its cost.
  • Design context isolation, delegation, synthesis, and citation provenance.
  • Evaluate non-deterministic workflows using traces and task-level graders.

Evaluation Guide

This is an evaluation framework, not a single model answer. Strong designs may make different choices when their assumptions and trade-offs are explicit.

Architecture judgment

20%

Senior signals

  • Explains why a multi-agent system is justified and where a deterministic workflow is better.
  • Identifies tasks that are parallelizable versus tightly dependent.

Coordination and context

30%

Senior signals

  • Defines task contracts, context boundaries, tool scopes, duplicate-work prevention, result schemas, and synthesis.
  • Preserves source provenance through subagent compression.

Reliability and cost

25%

Senior signals

  • Budgets tokens/tool calls/time, supports cancellation, retries, partial results, and loop limits.
  • Prevents combinatorial delegation and low-value exploration.

Evaluation and observability

25%

Senior signals

  • Captures traces, tool choices, handoffs, citation validity, and task outcomes.
  • Uses datasets and graders to compare orchestration changes despite non-determinism.

Trade-offs to articulate

  • Parallel breadth versus token cost.
  • Agent autonomy versus debuggability.
  • Context isolation versus duplicated discovery.

Practice follow-up questions

  1. 1.Subagents return contradictory sources. How does synthesis respond?
  2. 2.Token spend grows 15x while quality improves only 5%. What do you change?

Want interactive feedback?

Practice drawing this system component-by-component on a live whiteboard while the interviewer probes at your target level.

Start Interview

Core Concepts

Agent OrchestrationTask DecompositionTool UseEvaluationCost Control