Dayward AIWeChat Mini Program
From Frontend Engineer to Agent Engineer in 30 Days
Week 4 · D26🔒 LockedAbout 6 hours

System Design Deep Dive: Agent Platforms / Customer-Support Agents / Multi-Tenancy / Cost Control

Prepare an interview-ready answer template for each of four frequently asked system-design topics: agent platforms, customer-support agents, multi-tenancy, and cost control.

Today's goals 0/3

Sign in to tick these off and save your progress.

Today's Goals

  1. Give a system-design answer template for an agent platform (architecture, scalability, cost)
  2. Give a system-design answer template for a customer-support agent (multi-turn conversation, escalation to a human, knowledge base)
  3. Give a checklist of design points for both the multi-tenancy and cost-control topics

From today this course has no new technology: yesterday connected the backend to a browser and four weeks of technical content ended there — the next five days practice expression, how these same parts become an answer that makes an interviewer nod within 40 minutes. So you will see many familiar terms today, and the point is not what each is but "how many minutes this section gets, where the interviewer will interject, and which sentence loses points on the spot."

Plain-Language Walkthrough

The client gives you one sentence, and you cannot pull out construction drawings

An architecture bid presentation. The client opens with one sentence: "We want an office building."

The firm that lost unrolled a set of construction drawings on the spot, with beam reinforcement and pipe routing all drawn. Beautiful drawings, and by the third minute the client was looking at their phone — they had not yet said whether the budget was twenty million or two hundred.

The firm that won spent five minutes asking first: budget range, stories, fire rating, timeline. Then they produced a site plan of nothing but boxes and arrows, went deep on structural selection and fire egress, and said "standard practice" for everything else. The last five minutes were dedicated to trade-offs: why no second basement level, and at what budget the scheme should be overturned.

Whoever opens with construction drawings loses. A system-design interview is that same presentation: a one-sentence brief, 35 to 40 minutes, and one client scoring silently. The answer's shape is five fixed steps, each with a time box:

StepTimeWhat this step must deliver
1 Clarify requirements5 mindaily actives and concurrent sessions, per-turn latency budget, cost budget, multi-tenant or not, failure tolerance
2 Capacity and cost estimate3 mina number with arithmetic behind it, not a number reported by feel
3 Architecture sketch8 minfour blocks: intake, execution, storage, observability
4 Go deep on 2 to 3 points15 minpicked live from three pre-prepared deep-dive packs
5 Trade-offs5 minwhat you gave up, and at what scale this design gets overturned

Below, step by step, where the interviewer will interject.

Step one, clarifying, 5 minutes. None of the five questions is optional, because each substantially changes the architecture: daily actives decide whether to split, the latency budget decides synchronous versus asynchronous, the cost budget decides model tiering, multi-tenancy decides the table structure, and failure tolerance decides the shape of retries and degradation. The interviewer will most likely interject "just assume something" — that is not "stop asking," it is "give a number yourself and state your basis": "then I will work from 10,000 daily actives at 5 turns each, and if it is actually six figures I will say in step five what changes." Whoever starts drawing without asking discovers twenty minutes later that they solved a different problem.

Step two, estimating, 3 minutes. Reporting only the result and not the arithmetic is this step's most common death. The interviewer's interjection will certainly be "where did that number come from."

Step three, the sketch, 8 minutes. Four boxes and arrows suffice. The interviewer will point at an arrow and ask "is this synchronous or asynchronous" — drawing every arrow as a synchronous call is this step's only fatal flaw.

Step four, going deep, 15 minutes. This cannot be improvised, and three deep-dive packs must be prepared so whichever the interviewer picks you have it: state and ordering, cost and rate limiting, failure and retry, corresponding to what you already wrote on D11, D13, and D9 plus D10.

Step five, trade-offs, 5 minutes. Almost nobody does this step, and doing it earns points — it is the shortest dividing line between having designed something and having read a design.

Reciting the structure is not the same as delivering it. Each of the four frequent topics has one through-line, and with the wrong line the five steps are a hollow frame however correctly walked. Each of the four templates below pins a line first and hangs the parts off it.

Sign in and link WeChat to read

Sign in, then link your WeChat mini program account on the account page. Linked accounts share one free article per day. Unlock additional articles with rewarded videos in the mini program.

Mini program QR code

Scan in WeChat to open Dayward AI. Open the same course and chapter, choose the rewarded video, then refresh this page after completion.

Interview questions

  • You get 35 to 40 minutes for a system design round. How do you budget that time, and why is drawing the architecture not step one?系统设计环节只有 35 到 40 分钟,你会怎么分配时间?为什么第一步不是画架构图?
    Common in ChinaCommon overseasBasic#system-design#interview-process

    🔒 Unlock this chapter to see the answer keys.

  • System design: design an e-commerce customer support agent. It looks up orders and shipments, drafts refunds by policy, answers product and policy questions, and escalates to a human when it cannot resolve the issue.系统设计:请设计一个电商客服 Agent。它要能查订单和物流、按规则拟退款方案、回答商品与政策问题,并在搞不定时转人工。
    Common in ChinaCommon overseasDeep dive#system-design#customer-support#escalation

    🔒 Unlock this chapter to see the answer keys.

  • For a multi-tenant agent service, how do you design data isolation and billing isolation, and when do you move from a shared table to a dedicated database per tenant?一个多租户的 Agent 服务,数据隔离和计费隔离要怎么设计?什么时候该从共享表升级到独立库?
    Common in ChinaCommon overseasIntermediate#system-design#multi-tenancy#isolation

    🔒 Unlock this chapter to see the answer keys.

  • An agent system's model spend is out of control. Which levers do you pull, in what order, and roughly how much does each save?一个 Agent 系统的模型成本失控了,你会从哪几个层面着手控制?每一层大概能省多少?
    Common in ChinaCommon overseasIntermediate#system-design#cost#capacity-planning

    🔒 Unlock this chapter to see the answer keys.

Comments