Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Design a Multi-Agent Research Assistant

MediumGenerative AI & LLMs00:00
Practice interviewer
In session
5 left
00:00

Your question is Design a Multi-Agent Research Assistant. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Scenario

You are building an internal research assistant that answers complex analyst questions by coordinating multiple agents: one plans the task, one retrieves internal documents, one queries approved external sources, and one synthesizes a final answer. Users ask multi-step questions that often require comparing policies, summarizing recent changes, and citing evidence. The system is expected to support roughly 8,000 queries per day, with noticeable spikes during incident reviews and quarterly planning.

Constraints

  • p95 latency: 4,000ms for standard queries
  • Cost ceiling: $12K/month at projected volume
  • Unsupported or weakly grounded claims must stay below 4% on a 300-question golden set
  • Must resist prompt injection from retrieved content and external web pages
  • Final answers must include source-backed citations and refuse when evidence is insufficient

Available Resources

  • Internal document corpus of ~200K markdown, PDF, and wiki pages
  • Approved LLM APIs, embedding models, and tool-calling support
  • Hybrid search over internal content and a small allowlisted external search API
  • 20 hours of SME labeling time per month for evals and error analysis

Question

How would you design the agentic workflow and multi-agent orchestration for this system so it remains grounded, safe, and cost-effective under these constraints? Explain how you would decide when to use multiple agents versus a simpler flow, and how you would evaluate whether the orchestration is actually helping.