Interview Bank

Build an AI Short-Drama Production Pipeline With Agents in 14 Days

D7 One Episode Wrapped: Stringing Six Stages Into an End-to-End Pipeline and Tallying the First Bill

• How do you measure the cost of a generation pipeline, and what besides money should you measure?怎么度量一条生成流水线的成本？除了钱还要量什么？

  Common in ChinaCommon overseasBasic#observability#cost-accounting#pipeline-design

  How to reason about it · think before answering

  1. This looks like a giveaway, but the real question is 'besides money'. Anyone who reports a single total cannot make an optimization decision, because a total does not say where to act.
  2. First decide the granularity: break it down per stage. One number carries no information; a per-stage table immediately shows where the money and the time went. Measured on one episode here: five images cost 0.125 yuan, voice under two cents, three video shots 10.5 yuan — video is 98 percent. You only see that broken down.
  3. Second, measure three things besides money: elapsed time decides how many episodes per day, call count decides whether you hit provider rate limits, and artifact count is the crudest completeness check — four shots should yield four clips, and a missing one means something failed silently.
  4. Third, separate estimates from real spend. Offline or in load tests you have no real amounts, so derive them from published unit prices — but label them as estimates, and never mix the two on one code path or the books will never reconcile.
  5. Also worth flagging: offline timing rankings are usually fake. With the APIs stubbed, local encoding becomes the biggest slice, and optimizing against that chart targets the wrong thing.
  6. Expect the follow-up 'what do you optimize first'. Answer: whatever has a number attached. Here it is waste from failed reruns, because it equals money on the bill. Concurrency comes second — before output is stable, concurrency only burns money faster.

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

  1. 这题看着是送分题，题眼其实在「除了钱」。只报一个总金额的人，做不出任何优化决策，因为总金额不告诉你该动哪里。
  2. 第一步是确定度量的粒度：**按环节摊开**。一个总数没有信息量，一张按环节分列的表能立刻告诉你钱花在哪、时间花在哪。本课量过一集：五张图一毛二五、配音不到两分、三个镜头的视频十块五，视频占了九成八——这个结论只有摊开才看得见。
  3. 第二步是把「钱」之外的三样一起量：耗时决定一天能出几集；调用次数决定会不会撞上厂商的速率限制；产物数是最朴素的完整性校验，四个镜头就该有四个视频，少一个说明某处静默失败了。
  4. 第三步是把估算和真实分开。离线或压测时拿不到真实金额，可以按公开单价折算，但**必须标明它是折算值**，而且折算逻辑和真实金额不能混在一条路径上算，否则账永远对不上。
  5. 还要提醒一句常被忽略的：离线模式下的耗时排名往往是假的。接口被打了桩，本地的编码步骤反而成了大头，照着这张图做优化会优化错地方。
  6. 可预期的追问是「量完之后先优化哪一项」。答：先优化能被数字证明收益的那一项。这个场景里是失败重跑造成的浪费，因为它直接等于账单上的金额；并发排第二，因为在产出还不稳定时并发只会让你更快地烧钱。

  Key points

  • Break the cost down per stage; a single total cannot tell you where to act.
  • Besides money, measure elapsed time, call count and artifact count — throughput, rate limits and completeness.
  • Keep estimated and real spend on separate paths, and always label estimates as estimates.
  • Offline timing rankings are unreliable; do not optimize against a stubbed profile.
  • Prioritize by which improvement has a number attached, not by intuition.

  答题要点

  • 按环节摊开，不要只给一个总数，否则无法定位该优化哪里。
  • 除了金额还要量耗时、调用次数、产物数，各自对应吞吐、限流、完整性。
  • 估算与真实金额分开计算，估算必须标明是折算值。
  • 注意离线模式下耗时排名不可信，别照着假图做优化。
  • 优化顺序按「收益能不能被数字证明」排，不按直觉排。
• After chaining several individually working steps into one pipeline, which problems appear that single-step debugging never shows?把多个已经各自跑通的环节串成一条流水线之后，哪些问题是单独调试时看不见的？

  Common in ChinaCommon overseasDeep dive#integration#pipeline-design#observability

  How to reason about it · think before answering

  1. This tests integration instinct. If the answer is only 'interfaces do not line up', you have only integrated synchronous pure functions. In generative pipelines the integration problems live in state and artifacts, not in signatures.
  2. The framing question is: during single-step debugging, who does the gluing? Your head does. You know where the last script wrote its files and which blob to feed forward. Chaining forces that implicit knowledge into code, and whatever you fail to move becomes an integration bug.
  3. That yields three concrete classes. First, artifact paths and naming: a fixed output path is fine in isolation, but the second run overwrites the first, and on failure you cannot tell which files belong to which attempt. The fix is a run id that every artifact hangs under.
  4. Second, partial intermediate state: a step produces incomplete output without erroring, the next step accepts it, and the error propagates until it explodes far from its origin. The fix is a completeness assertion after every step, such as an expected artifact count.
  5. Third, observability: six stages each log their own way, hundreds of lines scroll past, and you cannot tell which stage failed. The fix is one log contract — a scannable progress table on the terminal, details pushed to files.
  6. Expect the follow-up 'how do you catch these earlier'. Answer: agree on three things before chaining — the artifact directory layout, each step's input/output contract, and the log format. Fix those and most integration bugs never get written.

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

  1. 这题考的是系统集成的直觉。回答里如果只有「接口对不上」，说明你只集成过同步的纯函数；生成式流水线的集成问题主要出在状态和产物上，不在接口签名上。
  2. 拆解的角度是：单独调试时，是谁在做衔接？答案是你的脑子。你知道上一个脚本把文件写到哪、知道该拿哪份数据喂下一步。串起来之后这些隐式知识必须搬进代码，而搬漏的地方就是集成问题的来源。
  3. 由此可以推出三类具体问题。第一类是产物路径与命名：单独跑时随手写一个固定输出路径没问题，串起来跑第二遍就把第一遍覆盖了，失败时也分不清哪些文件属于哪一次。解法是每次运行分配一个运行标识，所有产物挂在它下面。
  4. 第二类是中间态：某一步的产物不完整但没报错，下一步照单全收，错误一路往下传，最后在离源头很远的地方炸掉。解法是每一步产出后做完整性校验，比如按数量断言。
  5. 第三类是可观测性：六个环节各打各的日志，几百行滚过去，出了事看不出是哪一环。解法是统一日志规格，终端上只留一张能一眼扫完的进度表，细节压到文件里。
  6. 可预期的追问是「怎么提前发现这些问题」。答：串联之前先约定三件事——产物目录布局、每一步的输入输出契约、日志规格。这三件事定下来，绝大多数集成问题在写代码时就被挡住了。

  Key points

  • In isolation a human does the gluing; chaining means moving that implicit knowledge into code.
  • Artifact paths and naming: assign a run id and hang every artifact under it to avoid overwrites and confusion.
  • Incomplete intermediate state that does not error propagates far before exploding; assert completeness after every step.
  • Log flooding: adopt one log contract, keep a progress table on the terminal and push details to files.
  • Prevent it by agreeing on directory layout, per-step I/O contracts and log format before chaining anything.

  答题要点

  • 单独调试时是人脑在做衔接，串联的本质是把隐式知识搬进代码。
  • 产物路径与命名：每次运行一个运行标识，所有产物挂在它下面，避免覆盖与混淆。
  • 中间态不完整却不报错，错误会传到很远的地方才炸；每一步产出后做完整性校验。
  • 日志淹没：统一日志规格，终端只留进度表，细节压到文件。
  • 预防手段是串联之前先定好目录布局、输入输出契约与日志规格三件事。

D12 Cost and Model Routing: Choosing a Model per Stage, Caching, Degradation, and a Budget Circuit Breaker

• How do you break down the cost of a content-generation pipeline, and which stage would you optimize first?一条内容生成流水线的成本要怎么拆？拆完你会先优化哪一环，为什么？

  Common in ChinaCommon overseasBasic#cost-analysis#observability

  How to reason about it · think before answering

  1. This question checks whether you have actually read a bill. Answering with generic advice like use more caching signals you never ran this in production; naming the breakdown dimensions and rough ratios signals you did.
  2. Establish the dimensions first: by stage (script, image, video, speech), by billing unit (per second, per item, per character, per token), and by billable status (succeeded, cache hit, failed and not charged). Drop any one of them and a whole class of spend becomes invisible.
  3. Then give orders of magnitude. Video is billed per second, so a dozen seconds already costs a few yuan, while images are cents per item, speech is fractions of a cent per character, and text is lower still. Video typically dominates at over ninety percent.
  4. So the priority is driven by what is expensive, not by what is easy to change. Attack video first, cheapest lever to most expensive: caching and idempotency, tiered routing with a cheap draft tier, degradation across resolution, duration and shot count, and only then vendor negotiation.
  5. Add a credibility note: never put an unverified unit price in the table. Mark derived prices as estimates and leave unpublished ones blank while still counting usage. Reporting an estimate as an official price is how these projects lose trust.
  6. Expect the follow-up: how do you prove the optimization worked? Run the same input twice and compare the per-stage panel, not the monthly invoice, which mixes in traffic you did not cause.

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

  1. 这题在考你有没有真的看过账单。凭感觉答「多用缓存、少调模型」的人一听就没做过；能说出「按什么维度拆、拆出来大概什么比例」的才是。
  2. 拆的维度要先立住：按环节（脚本、图像、视频、语音）、按计价单位（按秒、按张、按字符、按 token）、按是否计费（成功、命中缓存、失败未扣费）。三个维度缺一个，报表就会有一类花费永远看不见。
  3. 然后给数量级。多媒体生成这类流水线里视频按秒计价，一集十几秒就是几块钱；图像按张几分钱、语音按字符几厘钱、文本更低。结论是视频通常占九成以上，其余全是零头。
  4. 所以优化顺序不是「哪一环最容易优化」，而是「哪一环最贵」。先优化视频，手段按代价从低到高排：缓存与幂等（不重复调）、分档路由（草稿档用便宜规格）、降级（清晰度、时长、镜头数）、最后才是换厂商谈价。
  5. 补一句可信度：不确定的单价不要写进表。官方只给资源包价的档位要标明是折算值，官方没公开的档位就留空只统计用量——把估算值当官方价报上去，是这类项目最常见的翻车点。
  6. 可预期的追问是「那怎么证明优化生效了」。答案是同一份输入跑两遍，对照面板上按环节的金额与调用次数，而不是看月账单——月账单里混着别人的流量，归因不到你这次改动。

  Key points

  • Break it down three ways: by stage, by billing unit, and by whether the call was actually charged
  • Lead with the ratio: video is billed per second and usually exceeds ninety percent of per-episode cost
  • Optimize expensive first: caching and idempotency, tiered routing, degradation, vendor negotiation last
  • Leave unknown unit prices blank while still counting usage, and label derived prices as estimates
  • Validate by running the same input twice and diffing the per-stage panel, not the monthly invoice

  答题要点

  • 按三个维度拆：环节、计价单位、是否真的计费（成功 / 缓存命中 / 失败未扣费）
  • 先给比例再给结论：视频按秒计价，通常占单集成本九成以上，其余是零头
  • 优化顺序由贵到便宜：缓存与幂等、分档路由、降级、最后才谈价换厂商
  • 拿不到的单价宁可留空只统计用量，折算出来的要标明是折算值
  • 验证靠同一份输入跑两遍对照面板，不看混杂的月账单