Interview Bank

From Frontend Engineer to Agent Engineer in 30 Days

D30 Full Retrospective and Application Kickoff: a Complete Pass Over the Interview Bank, a Knowledge Map, Month-Two Application Cadence, Public Launch of the Site

• Walk me through what you have been working on recently and why you moved toward agent engineering, in three to five minutes.用 3 到 5 分钟讲一下你最近这段时间的成长路径，以及为什么转向 Agent 工程。

  Common in ChinaCommon overseasDeep dive#self-introduction#storytelling

  How to reason about it · think before answering

  1. This opens almost every interview and it is the one question you can fully pre-write. It tests selection, not history: three minutes cannot hold a month, so which three things you pick reveals what you think matters. A week-by-week recital is the common failure — it hands the judgment back to the interviewer.
  2. Structure it as origin, turn, evidence, direction. Origin: one sentence on where you were and what capped you. Turn: the concrete problem that pushed you toward agents, not 'I believe in the space'. Evidence: whichever of your projects maps best onto this role, framed as an engineering problem you solved. Direction: the kind of team and problem you want next.
  3. The evidence part has a hard requirement: give something checkable. A repository link, numbers you measured yourself, and the conditions you measured them under. 'I built an agent platform' and 'I split gateway from worker behind a message bus, and with three local replicas, killing the lease holder lets another worker take over once the lease expires' differ by an order of magnitude in credibility.
  4. Hold the integrity line yourself: these are learning projects, say so, and attach measurement conditions to every number (single machine, mock mode). Never present them as company work or quote scale you never ran — two follow-up questions expose it, and that kind of exposure is unrecoverable.
  5. Common mistake: spending the three minutes on technical depth. The opener's job is not to explain anything fully, it is to shape which threads the interviewer pulls over the next forty minutes — so end each part on a deliberate hook, such as 'lease renewal had to be atomic, which took a script', and stop there.
  6. Expect the follow-up: why not stay on your previous track? Answer with a concrete blocker you kept hitting, not with industry trends. Everyone can recite a trend; naming a specific problem shows you reasoned your way here.

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

  1. 这是几乎每场面试的第一题，也是唯一一道你能完全预写的题。它考的不是经历，是**取舍**：3 分钟装不下一个月，你选了讲哪三件事，直接暴露你认为什么重要。流水账式的「第一周我学了……第二周我学了……」是最常见的失败，它把判断权交回给了面试官。
  2. 怎么拆：套一条「起点 - 转折 - 证据 - 去向」的四段结构。起点一句话说清你原来的位置和它的天花板；转折说清是什么具体问题把你推向 Agent，不要用「看好这个方向」这种空话；证据是三个产出物中最能对上这个岗位的那一个，讲清楚它解决了什么工程问题；去向说清你想在什么样的团队继续解决什么问题。
  3. 证据那一段有个硬要求：**给出可被验证的东西**。仓库链接、你实测出来的数字、以及数字的测量条件。同一句话讲成「做了一个 Agent 平台」和讲成「gateway 和 worker 拆开、用消息总线解耦，本地三副本下杀掉持有租约的 worker，另一个能在租约到期后接手」，可信度差一个量级。
  4. 红线要自己守住：这三个是学习项目，说的时候就要说明是个人项目，数字要带测量条件（本地单机、模拟模式压测）。**不要把它讲成公司经历，也不要报没跑过的规模数**——面试官追问两句就穿帮，而且是不可挽回的那种。
  5. 常见误区：把这 3 分钟用来讲技术细节。开场白的目标不是讲透任何东西，是让面试官在后面 40 分钟里想问哪几个点——所以每段末尾都要故意留一个可追问的钩子，比如「租约续约那里我们用了一个脚本保证原子性」，停在这儿别展开。
  6. 可预期的追问：为什么不是继续做原来的方向？答案要落到具体问题上（原来的场景里你反复遇到什么做不了的事），而不是行业趋势——讲趋势的人到处都是，讲具体问题的人显得是自己想清楚的。

  Key points

  • Build the three minutes from origin, turn, evidence and direction — never a week-by-week recital
  • Ground the turn in one concrete thing you could not do before, not in a belief about the market
  • Make the evidence checkable: repository links, numbers you measured, and the conditions behind them
  • State plainly that these are personal learning projects; never dress them as company work or quote unmeasured scale
  • End each part on a deliberate hook so the next forty minutes land where you are strongest

  答题要点

  • 用「起点 - 转折 - 证据 - 去向」四段撑起 3 分钟，不要按周流水账
  • 转折要落到一个具体的做不了的问题上，而不是「看好这个方向」
  • 证据段给可验证的东西：仓库链接、自己实测的数字、以及测量条件
  • 明确说明这是个人学习项目，绝不包装成公司经历、绝不报没跑过的规模
  • 每段末尾留一个可追问的钩子，把后面 40 分钟引到你准备最充分的地方