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

Interview questions

• With only one week left before your interviews, how would you plan your review?如果只剩最后一周准备面试，你会怎么安排复盘节奏？

  Common in ChinaCommon overseasBasic#interview-prep#prioritization

  How to reason about it · think before answering

  1. This sounds casual but it tests prioritization. The interviewer wants judgment, not diligence: the week is fixed, so how do you decide where it goes? 'Eight hours a day, start from the top' shows no judgment at all.
  2. Offer a reusable rule: the marginal value of reviewing a topic depends on how far you currently are from being able to explain it, so step one of any plan is measurement, not study. Planning without measuring is allocating a budget blindfolded.
  3. Concretely: day one is triage only — say every answer out loud and tag it green (can explain unaided), yellow (can explain with a glance at notes), or red (cannot). Skip reds immediately. The output of that pass is a distribution, not knowledge. Days two and three hit yellow and red, day four hits what is still red, and the last days go to mock interviews and delivery.
  4. Name the discipline and its failure mode: fixing the first red question on the spot burns thirty minutes, so by question twenty the day is gone and most of the set was never assessed. That detail is what proves you have actually done this.
  5. Add a falsifiable bar for 'I know it': out loud, ninety seconds, no notes. The fluency you feel while reading silently belongs to the author, not to you.
  6. Expect the follow-up: what if the reds cluster in one area? Fix the upstream concept first rather than the individual questions — clustered reds usually share one missing prerequisite, and repairing it lights up five questions at once.

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

  1. 这题看着像闲聊，其实在考「你会不会做优先级」。面试官想听的不是勤奋，是判断：一周时间是固定的，你怎么决定把它花在哪。答「每天复习八小时，从头过一遍」就是没有判断。
  2. 先给一条可复用的推导：复习的边际收益取决于「这一块你现在离能讲清有多远」，所以任何计划的第一步都必须是**测量**，而不是学习。没测量就排计划，等于闭着眼睛分配预算。
  3. 落到具体做法：第一天只做分诊——把所有题目出声过一遍，按「能讲清 / 看一眼能讲 / 讲不出」标三种颜色，看到不会的立刻跳过。这一遍的产出是一张分布图，不是知识。第二、三天只碰后两类，第四天只碰仍然讲不出的，最后两三天留给模拟和表达。
  4. 要主动说出「只标记不纠结」这条纪律和它的失败模式：碰到第一道不会的题当场去补，一道题吃掉半小时，做到第 20 道今天就没了，剩下的题连颜色都没有。这个细节最能证明你真的这样练过。
  5. 再补一个判据：判断「会」的标准必须可证伪——出声、限时 90 秒、不看提纲。默读产生的流畅感是题库给的，不是你的。
  6. 可预期的追问：如果分诊发现红题集中在同一块怎么办？答案是先补那一块的**上游**概念，而不是逐题补——同一块里的题往往共用一个没吃透的前置，补上游一道题能带亮五道。

  Key points

  • Start by measuring, not studying: one spoken pass over everything, tagging only, no on-the-spot fixes
  • Three shrinking passes: tag everything, then only yellow and red, then only what is still red, leaving the tail for delivery practice
  • Make 'I know it' falsifiable: spoken, under ninety seconds, no notes — silent reading does not count
  • The triage pass produces a distribution that tells you whether the remaining days go to technique or to delivery
  • When reds cluster, repair the shared upstream concept rather than each question

  答题要点

  • 第一步是测量不是学习：先出声过一遍全部题目，只做三色标记，不当场补漏
  • 三遍递减：第一遍全量标记，第二遍只刷黄和红，第三遍只刷仍然红的，最后留时间给表达与模拟
  • 「会」的判据必须可证伪：出声讲、90 秒内讲完、不看提纲，默读不算
  • 分诊的产出是一张分布图，它决定后面几天该补技术还是补表达
  • 红题扎堆时先补共同的上游概念，比逐题补效率高得多
• How do you turn scattered knowledge into a map that is actually useful for review?怎么把零散的知识点组织成一张便于复习的知识地图？

  Common in ChinaCommon overseasIntermediate#knowledge-organization#interview-prep

  How to reason about it · think before answering

  1. The load-bearing phrase is 'useful for review'. Most answers become 'group things by module and draw a mind map', which produces a table of contents, not a map — a contents page cannot tell you what to fix first. That is where candidates separate.
  2. Break it down: a graph has nodes and edges. Grouping nodes is cheap and almost everyone does it correctly; the information lives in the edges. So ask yourself how many edges your diagram has and what each one means. No answer means you drew a contents page.
  3. Give an operational rule for edges: draw A to B only when not understanding A blocks understanding B. 'Both are about message queues' does not qualify — that is sibling grouping. 'You cannot understand context compression without the context window' does. Course order does not qualify either; that is a calendar, not a dependency.
  4. Conclusion: use the map by painting your weak spots onto it. If a node is shaky, check whether its upstream is shaky too — repair upstream and several downstream nodes light up at once. That is the map's one advantage over a checklist: a checklist says what is broken, a map says where to start.
  5. Production angle: the same habit pays off at work. When debugging an incident, the dependency graph in your head decides whose logs you open first; without it you probe services one by one. Saying this shows the map is a working tool, not an exam prop.
  6. Expect the follow-up: how big should it be? Small enough to redraw on a whiteboard in five minutes. Past that you start maintaining the map instead of using it — merge nodes into themes and leave the detail in your question bank.

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

  1. 题眼在「便于复习」四个字。绝大多数人答成「按模块分类、画个思维导图」，那产出的是目录不是地图——目录任何一本书的前几页都有，它不能告诉你先补哪里。区分度就在这儿。
  2. 怎么拆：一张图有两种元素，节点和边。分层（节点怎么分组）是廉价的、几乎人人做得对；真正的信息量在边上。所以先问自己一个问题——我这张图上有几条边，每条边的含义是什么？答不上来就说明画的是目录。
  3. 给一条可操作的连边判据：只有当「不懂 A 就学不懂 B」时才连 A 指向 B。「A 和 B 都属于消息队列」不算，那是同层并列；「不理解上下文窗口就理解不了为什么要压缩」算。课程的先后顺序也不算——那是日历，不是依赖。
  4. 结论：地图的用法是把你的弱点涂上去。某个节点讲不清，先看它的上游是不是也红——是的话补上游，一次带亮一串。这就是地图相对清单的唯一优势：清单说哪里错了，地图说该从哪儿开始。
  5. 生产视角：这套东西在工作里同样有用。排查一个线上问题时，你脑子里那张「谁依赖谁」的图决定了你先看哪个服务的日志；没有这张图的人只能一个个试。面试时把这个类比说出来，会显得你不是为了背题才画图。
  6. 可预期的追问：那张图应该多大？答案是能在白板上 5 分钟画完——超过这个规模你会开始维护它而不是使用它，节点合并成主题，细节留在题库里。

  Key points

  • Grouping into layers is what any table of contents does; a map's information is in its edges
  • One rule for edges: draw one only when A is a genuine prerequisite for B — sibling topics and course order do not count
  • Paint your weak spots on the nodes and fix upstream first when reds cluster; one fix lights up several downstream nodes
  • Long cross-layer edges are the valuable ones — following them in an interview shows a system, isolated nodes only produce fragments
  • Keep it redrawable on a whiteboard in five minutes; finer detail belongs in the question bank, not the map

  答题要点

  • 分层只是分组，任何目录都做得到；地图的信息量全部在边上
  • 连边的判据只有一条：不懂 A 就学不懂 B 才连边，同类并列和课程顺序都不算
  • 把弱项涂到节点上，红点扎堆时优先补上游节点，一次带亮一串下游
  • 跨层的长边最值钱，面试时顺着长边讲能体现体系，孤立节点只能给出零碎答案
  • 规模控制在白板 5 分钟能画完，再细的内容留在题库里而不是图上
• 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 分钟引到你准备最充分的地方

Comments

Sign in to join the discussion

No comments yet — be the first.