面试题库

14 天用 Agent 搭一条 AI 短剧生产线

D14 一季五集：批量产出、作品集包装与短剧生产线面试专题

• 如果让你重做一遍这条生产线，架构上你会怎么改？If you rebuilt this pipeline from scratch, what would you change architecturally?

  国内高频海外高频深入#architecture-review#trade-offs

  分析过程 · 先想清楚再作答

  1. 这题在考自我批判的质量。答「没什么要改的」直接出局；答一堆花哨的新技术也不行，因为那说明你没从这次的实践里学到东西。好答案是具体的、有代价分析的、并且能追溯到某一次踩坑。
  2. 先立一个筛选标准：只讲那些我这次真的被绊过、而且知道正确做法的地方。不确定的部分坦白说不确定——说得出方案的边界，比说得出方案本身更能证明你做过。
  3. 第一处可以讲重算范围。审核台上改一句台词，现在是按节点依赖整体重算下游，粒度偏粗；更好的做法是让每个节点声明自己依赖输入的哪几个字段，改台词只触发配音与字幕，不碰视频。代价是节点定义变复杂，收益是重做成本从一整镜降到一次语音合成。
  4. 第二处是成本模型。现在的单价表里有折算值和留空项，估算够用但不能对账；接了真实账单之后应该改成从账单反推实测单价，并保留一个偏差告警——估算和实际差超过阈值就报警，这比事后对账有用得多。
  5. 第三处是并发模型。现在闸门是按 provider 分类做的，更贴近现实的做法是按「配额桶」建模，因为同一家厂商的不同接口配额独立，而不同厂商之间又完全独立。改了之后限流的定位会准很多。
  6. 可预期的追问是「为什么当初不那样做」。诚实回答：当时先做能跑通的最小版本，把复杂度留给已经被数据证明值得的地方。这句话本身就是架构判断——面试官想听的正是你会不会区分「必要的复杂度」和「过早的复杂度」。

  How to reason about it · think before answering

  1. This tests the quality of your self-critique. Saying nothing needs changing ends the conversation; listing trendy technologies is just as bad, because it shows you learned nothing from the build. A good answer is specific, has a cost analysis, and traces back to a concrete stumble.
  2. Set a filter first: only discuss places where you actually got tripped up and now know the right approach. Say plainly where you are still unsure, because naming the limits of your solution proves more than the solution itself.
  3. First, recomputation scope. Editing one line of dialogue currently recomputes the whole downstream subgraph. Better would be for each node to declare which input fields it depends on, so a dialogue edit triggers only speech and subtitles, never video. The cost is more complex node definitions; the benefit is redoing one synthesis instead of a whole shot.
  4. Second, the cost model. The rate card today mixes derived prices with deliberate blanks, which is fine for projection but useless for reconciliation. Once real invoices exist, back out measured unit prices from them and keep a drift alert that fires when projection and reality diverge past a threshold, which beats after-the-fact reconciliation.
  5. Third, the concurrency model. Gates are currently keyed by provider, but modelling them as quota buckets matches reality better, since different endpoints from one vendor have independent quotas while different vendors are fully independent. Rate-limit diagnosis gets far more precise.
  6. Expect the follow-up: why not build it that way originally? Answer honestly that you shipped the smallest working version and spent complexity only where data justified it. That sentence is itself an architectural judgement, and distinguishing necessary complexity from premature complexity is exactly what the interviewer is listening for.

  答题要点

  • 只讲真的踩过且知道正确做法的地方，不确定的坦白说不确定
  • 重算范围改成按字段级依赖，改台词只触发配音与字幕而不重生成视频
  • 成本模型接真实账单后反推实测单价，并加一个估算与实际的偏差告警
  • 并发闸门从按 provider 改成按配额桶建模，贴合各接口配额独立的现实
  • 解释当初为何没这么做：先做最小可跑版本，把复杂度留给数据证明值得的地方

  Key points

  • Only discuss stumbles you actually hit and now know how to fix; admit what you are unsure about
  • Move recomputation to field-level dependencies so a dialogue edit skips video regeneration
  • Back out measured unit prices from real invoices and add a projection-versus-actual drift alert
  • Model concurrency gates as quota buckets rather than per provider, matching per-endpoint quotas
  • Explain the original choice: ship the smallest working version and spend complexity only where data justifies it