面试题库

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

D27 简历与项目包装：STAR、README、架构图、demo 视频、英文简历

• 请用 STAR 法则讲一个你做过的技术项目。Walk me through a technical project of yours using the STAR framework.

  国内高频海外高频基础#behavioral#star#resume

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

  1. 这题在考「你会不会控制信息密度」，不是考你记不记得 STAR 四个字母。面试官已经听过几十遍 STAR，他真正在数的是：你花了多少时间讲背景、多少时间讲你自己做了什么、最后有没有一个能被追问的数字。
  2. 先定时间分配再开口，这是可以现场执行的一条纪律：情境 20 秒、任务 15 秒、行动 90 秒、结果 25 秒。绝大多数人的失败模式是情境讲了 90 秒——那部分听起来最安全，因为不涉及你的能力，所以人会不自觉地躲在那里。
  3. 行动那 90 秒里只讲你亲手做的部分，主语必须是「我」。团队做了什么用一句话带过，然后立刻切回「我负责的是其中的 X，我的做法是 Y」。说不清「我和别人的边界在哪」，这条经历在评分表上会被打成不可验证。
  4. 结果必须落到一个带前后对照的数字，并且主动补一句测量条件。比如「分片利用率从 256 个里只占 1 个变成全占满，最大桶从 2000 条降到 19 条，这是本地单机、2000 个模拟用户、256 个分片的自检结果」。补测量条件不是示弱——它把「我知道自己测的是什么」这件事直接摆出来了。
  5. 如果这段经历是学习项目或课程项目，在情境那 20 秒里就说清楚，不要等到被追问。主动交代来源的人，后面报的数字反而更容易被相信；藏着掖着被问出来，之前讲的全部要被重新掂量一遍。
  6. 可以预期的追问：「这个数字是怎么测的？」以及「如果规模再大十倍，这个做法还成立吗？」第一个考真实性，第二个考边界感——答第二个时要主动说出「在什么规模下我会推翻现在这个设计」，这一句几乎没人说，说了就是加分。

  How to reason about it · think before answering

  1. This question tests whether you can control information density, not whether you remember four letters. The interviewer has heard STAR dozens of times; what he is actually timing is how long you spend on background versus on what you personally did, and whether you land on a number he can probe.
  2. Decide the time split before you open your mouth: 20 seconds of situation, 15 of task, 90 of action, 25 of result. The classic failure is spending 90 seconds on situation — it feels safe because it says nothing about your ability, so people hide there.
  3. In those 90 seconds of action, say 'I', not 'we'. Summarize the team's work in one sentence, then cut straight back to 'my piece was X, and the way I did it was Y'. If your boundary with the rest of the team is unclear, the story is scored as unverifiable.
  4. The result has to be a before-and-after number, and you volunteer the measurement conditions with it: 'shard utilization went from 1 of 256 to all 256, and the largest bucket dropped from 2000 to 19 — measured locally with 2000 simulated users across 256 shards.' Naming the conditions is not hedging; it shows you know what you measured.
  5. If it is a personal or course project, say so inside the first 20 seconds rather than waiting to be asked. Volunteering the origin makes your numbers more credible, not less; being caught hiding it forces the interviewer to re-weigh everything you said before.
  6. Expect two follow-ups: 'how did you measure that?' and 'does this still hold at ten times the scale?' The first tests honesty, the second tests judgment — answer the second by naming the scale at which you would throw this design away.

  答题要点

  • 开口前先分配时间：情境 20 秒、任务 15 秒、行动 90 秒、结果 25 秒，别让背景吃掉一半时长
  • 行动部分主语是「我」，明确说出自己和团队的边界
  • 结果给一个带前后对照的数字，并主动补上测量条件
  • 学习项目在情境阶段就主动交代，不等追问
  • 结尾主动加一句「在什么规模下这个设计会失效」，把边界感摆出来

  Key points

  • Budget the time before speaking: 20s situation, 15s task, 90s action, 25s result — never let background eat half the answer
  • Say 'I' in the action section and draw a clear line between your work and the team's
  • End on a before-and-after number and volunteer how it was measured
  • Disclose that it is a personal or course project up front, not under questioning
  • Close by naming the scale at which the design would break — it signals judgment