面试题库

30 天从前端工程师到 Agent 工程师

D20 定时 Job 与主动关怀：时区、quiet hours、每日上限、通知 provider 抽象

• 模型调用、支付、通知渠道你都做过 provider 抽象。通知这一份接口和另外两份有什么不同？You have abstracted model calls, payments and notification channels behind providers. How does the notification interface differ from the other two?

  国内高频海外高频进阶#provider-abstraction#api-design#retry-semantics

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

  1. 这题在考你是「会套模式」还是「懂模式」。把三者说成一回事——都是接口加多个实现、换厂商不改业务——只答到了共性那一层，面试官真正想看的是你有没有识别出差异并把它写进接口。
  2. 先给共性，一句话带过：都是把「会被替换的东西」推到接口后面，业务代码只认接口，选择点集中在一处。这一层是对的，但不构成区分度。
  3. 然后给三条差异，这是拿分点。第一，收下不等于送达：支付网关返回成功钱就划走了，通知渠道返回成功只表示它收下了，真正送达是过一会儿通过回执异步告诉你的。所以返回值只能叫 accepted 不能叫 delivered，而且必须带渠道侧的消息标识，回执回来时靠它对上号。
  4. 第二，限流的层次不同：渠道自带每秒条数上限并会用 429 加重试间隔告诉你稍后再来，这是**渠道维度的技术约束**；而每日发送上限是**用户维度的礼貌约束**。两者混成一个概念就没法分别调整——一个说的是这条线路挤不下了，一个说的是这个人今天已经被打扰够了。
  5. 第三，没有撤销：支付有退款，通知发出去就撤不回来，取消只在交给渠道之前有效。所以接口里不能出现 cancel——在接口上留一个做不到的操作比根本没有这个操作更危险，调用方会真的去用它。
  6. 可以预期的追问：那失败重试怎么设计？答分三类：限流按渠道给的时长退避重试；参数错（正文非法、用户已退订）不可重试，直接放弃并把当天的名额还回去；服务端错误或超时可重试但必须带同一个幂等键——数据库里多一行你能删掉，用户手机上多响一声删不掉。再补一条判断抽象好坏的判据：新接一个渠道时如果它只需要实现「把这条消息发出去」，抽象就对了；如果它还得知道现在是不是安静时段、这是今天第几条，说明业务规则泄进了渠道层。

  How to reason about it · think before answering

  1. This question separates applying a pattern from understanding one. Saying all three are the same — an interface with several implementations so you can swap vendors without touching business code — only covers the shared part; the interviewer wants to see whether you spotted the differences and encoded them in the interface.
  2. Acknowledge the commonality in one line: each pushes a replaceable dependency behind an interface, business code depends only on the interface, and the selection point lives in exactly one place. Correct, but not differentiating.
  3. Then give three differences, which is where the points are. First, accepted is not delivered: when a payment gateway returns success the money has moved, but when a notification channel returns success it has merely taken the message, and actual delivery arrives later as an asynchronous receipt. So the result is accepted, never delivered, and it must carry the provider-side message id so the receipt can be correlated.
  4. Second, throttling lives at a different layer: the channel has its own per-second ceiling and tells you to come back later with a 429 plus a retry interval — a channel-level technical constraint — while the daily cap is a user-level courtesy constraint. Collapsing them into one concept makes them impossible to tune separately: one says this line is congested, the other says this person has been interrupted enough today.
  5. Third, there is no undo: payments have refunds, notifications do not. Once handed to the channel the message is gone, and cancel only means anything before that handoff. So the interface must not expose a cancel method — leaving an operation that cannot work is worse than not having it, because callers will actually use it.
  6. Expect: how do you design retries then? Three classes. Throttling backs off for the interval the channel gave you. Parameter errors (invalid body, unsubscribed user) are not retryable, so give up and return the daily slot. Server errors and timeouts are retryable but must carry the same idempotency key — you can delete a duplicate row, you cannot un-buzz a phone. Add a test for the abstraction itself: if a new channel only has to implement send the message, the boundary is right; if it also needs to know whether it is quiet hours or which message of the day this is, business rules have leaked into the channel layer.

  答题要点

  • 共性是把可替换依赖推到接口后面、选择点集中一处，但这只是及格线
  • 收下不等于送达：返回值叫 accepted 不叫 delivered，必须带渠道侧消息标识以便异步回执对号
  • 限流分两层：渠道的每秒上限是技术约束，每日发送上限是用户维度的礼貌约束，不能合并
  • 通知没有撤销，接口里不能有 cancel；留一个做不到的操作比没有更危险
  • 重试分三类：限流按渠道给的时长退避、参数错不可重试并归还名额、服务端错误可重试但必须带同一个幂等键
  • 判断抽象切没切对：新渠道只需实现发送就对了，还要知道安静时段和当天条数就说明业务泄进了渠道层

  Key points

  • The shared part is pushing a replaceable dependency behind an interface with a single selection point — that is only the baseline
  • Accepted is not delivered: name the result accepted and carry a provider message id so async receipts can be correlated
  • Throttling has two layers: the channel's per-second ceiling is technical, the daily cap is a user-level courtesy rule, and they must stay separate
  • Notifications have no undo, so the interface must not expose cancel — an unimplementable operation is worse than none
  • Three retry classes: back off for the channel's interval on throttling, give up and release the slot on parameter errors, retry server errors with the same idempotency key
  • Test the boundary: a new channel should only implement send; needing to know quiet hours or today's count means business rules leaked into the channel

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

D1 一条 AI 短剧生产线长什么样：工序拆解、任务图架构与四类生成模型选型

• 为什么要在厂商 SDK 之上再套一层自己的 provider 接口？什么时候这层反而是负担？Why wrap a vendor SDK in your own provider interface, and when does that layer become a liability?

  国内高频海外高频基础#provider-abstraction#architecture

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

  1. 这题在筛「有没有真的换过一次厂商」。只答「解耦、方便替换」的人，说的是一句所有人都会说的话，区分度在于你能不能给出「这层带来了什么、又赔上了什么」的具体清单。
  2. 怎么拆：先问自己「如果不套这层，哪些能力会散掉」。答案有三样，而且都能落到具体文件上——离线可跑（网络出口收敛到一处才可能打桩）、多厂商并存（业务代码写的是动作而不是某家的四步流程）、计量收口（每次调用的花费必须有唯一一处记账）。
  3. 接着说抽象的位置：接口要按业务动作定义，不按厂商的 HTTP 请求定义。异步视频任务的提交、轮询、取件、下载四步，对业务代码来说是一个 generate；把这四步漏到业务层，抽象就白做了。
  4. 结论与代价：这层会磨掉各家的独有能力（某家支持首尾帧、某家支持结构化运镜参数）。正确处理不是把接口撑大，而是留一个可选透传字段，让需要它的那一处显式承认自己绑定了某一家。
  5. 什么时候是负担：你只会用一家、也永远不会离线跑的时候；以及出现两个信号时——为加一个厂商改了接口签名让另外三个实现跟着改，或者接口里出现了只有一家有的参数名。这两个信号说明抽象抽在了厂商能力的最小公倍数上，位置错了。
  6. 可预期的追问：那要不要直接用某个统一网关或聚合 SDK？可以，但你仍然需要自己的接口，因为聚合层解决的是协议差异，解决不了你自己的落盘契约与记账口径。

  How to reason about it · think before answering

  1. The screen is whether you have ever actually swapped a vendor. Answering only decoupling and easy replacement is what everyone says; the signal is naming what the layer buys and what it costs.
  2. How to break it down: ask what you lose without the layer. Three concrete things — offline runnability (you can only stub when network egress is funneled into one place), multi-vendor coexistence (business code expresses an action, not one vendor's four-step flow), and metering (every call's cost must be recorded in exactly one place).
  3. Then place the abstraction: define it by business action, not by the vendor's HTTP request. Submit, poll, retrieve, download for an async video job is one generate to the caller; leaking those four steps upward defeats the purpose.
  4. Conclusion and cost: the layer sands off vendor-specific capabilities, such as first-and-last-frame conditioning or structured camera parameters. The fix is not a wider interface but one optional passthrough field, so the single call site explicitly admits it is vendor-bound.
  5. When it is a liability: single vendor forever and no offline path. Two warning signs — adding a vendor forced a signature change across the other implementations, or a vendor-only parameter name appeared in the interface. Both mean you abstracted the least common multiple of vendor features.
  6. Likely follow-up: why not just use an aggregation gateway or SDK? You still need your own interface, because aggregators normalize protocols but not your on-disk artifact contract or your cost ledger.

  答题要点

  • 三个理由要说具体：离线可跑、多厂商并存、计量收口，每一个都对应一处真实代码
  • 接口按业务动作定义，异步任务的提交轮询取件下载四步必须关在实现里
  • 把落盘路径写进接口契约，因为厂商返回的图片与视频链接都是会失效的临时链接
  • 代价是磨掉独有能力，用可选透传字段处理，而不是撑大公共接口
  • 两个「抽错了」的信号：加厂商要改签名、接口里出现厂商专有参数名

  Key points

  • Name three concrete reasons: offline runnability, multi-vendor coexistence, and a single metering point
  • Define the interface by business action; submit-poll-retrieve-download stays inside the implementation
  • Put the output file path in the contract, because vendor image and video URLs are short-lived temporary links
  • The cost is losing vendor-specific features; handle it with one optional passthrough field, not a fatter interface
  • Two signs you abstracted wrong: adding a vendor changes the signature, or a vendor-only parameter leaks into the interface

D5 配音、字幕与音轨：多角色语音、时间轴对齐与字幕文件

• 多角色配音里，怎么保证同一个角色跨集用的是同一个声音？In a multi-character pipeline, how do you guarantee the same character keeps the same voice across episodes?

  国内高频海外高频基础#tts#consistency#provider-abstraction

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

  1. 这题看着像配音问题，其实考的是状态该存在哪里。答「配置里写死」不算错，但只答到这一层看不出工程判断。
  2. 先说清楚风险来自哪：声音是角色身份的一部分，观众对它的敏感度不低于脸。跨集不一致的典型成因有三个——每集独立跑一次流程、音色靠临时映射或随机挑选、以及某次为了改一句台词的语气顺手改了这个角色的全局参数。
  3. 解法是把音色归档而不是归代码：角色档案里带一个音色字段，配音环节只读不写。这样一致性由档案保证，跟哪一集、哪一次运行、谁跑的都无关。这跟角色形象靠基准图归档是同一套思路。
  4. 但只存音色标识还不够，跨集听感一致还依赖另外两项：基调情绪与语速。同一个音色用两种语速念，听起来像两个人的状态。所以档案里要一起存这三项，单条台词只允许覆盖情绪，不允许覆盖语速。
  5. 再补一层防御：把音色标识连同模型名一起记进产物元数据。厂商下线或重命名一个音色是会发生的，你要能查出「第二季为什么听起来不一样」，而不是只能凭记忆猜。
  6. 可以预期的追问：如果厂商真的下线了那个音色怎么办？答案是把音色选择也做成 provider 抽象的一部分：档案里存的是角色的音色角色定位，映射到具体厂商音色的表放在适配层，换厂商或补映射时不动档案。

  How to reason about it · think before answering

  1. This looks like a voice question but is really about where state lives. 'Hardcode it in config' is not wrong, but stopping there shows no engineering judgment.
  2. Name the risk first: voice is part of a character's identity, and audiences are about as sensitive to it as to a face. Inconsistency across episodes has three usual causes — running each episode as an independent pipeline, picking voices from an ad-hoc or random mapping, and someone tweaking a character's global parameters while fixing the delivery of one line.
  3. The fix is to file the voice in the character record rather than in code: the record carries a voice id, and the dubbing step only reads it. Consistency then holds regardless of episode, run or operator — the same pattern as pinning appearance to a base reference image.
  4. Storing the voice id alone is not enough. Perceived sameness also depends on the baseline emotion and the speaking rate; the same voice at two different rates sounds like a different state of a person. Keep all three in the record, and allow per-line overrides of emotion only, never of rate.
  5. Add a defensive layer: record the voice id together with the model name in the artifact metadata. Vendors do retire and rename voices, and you want to be able to answer 'why does season two sound different' from data rather than memory.
  6. Expect the follow-up: what if the vendor retires that voice? Make voice selection part of the provider abstraction — the record stores the character's voice archetype, and the mapping to a concrete vendor voice lives in the adapter, so swapping vendors never touches the character records.

  答题要点

  • 把音色存进角色档案，配音环节只读不写，一致性与集数、运行次数、操作人无关
  • 档案里要同时存音色标识、基调情绪与语速；单条台词只允许覆盖情绪，不允许覆盖语速
  • 把音色标识与模型名一起写进产物元数据，便于回答「为什么这一季听起来不一样」
  • 跨集不一致的典型成因是每集独立跑、临时映射、以及改一句台词时顺手改了全局参数
  • 音色选择应纳入 provider 抽象：档案存角色的音色定位，具体厂商音色的映射放在适配层

  Key points

  • Store the voice in the character record and have the dubbing step read it only, so consistency is independent of episode, run or operator
  • Keep voice id, baseline emotion and speaking rate together; allow per-line emotion overrides but never rate overrides
  • Write the voice id and model name into artifact metadata so you can explain why a later season sounds different
  • Typical causes of drift are per-episode independent runs, ad-hoc mappings, and global tweaks made while fixing one line
  • Fold voice selection into the provider abstraction: records hold the archetype, the adapter maps it to a concrete vendor voice