技术面试英语词汇：拿下 FAANG offer 的 80 个词

---

速读：你需要知道的 3 件事

• 英语技术面试是双重挑战：你既要展示 CS 知识，又要用第二语言精准表达。多数非母语者失分在沟通，不在概念。
• 80 个词分 4 类，覆盖你真正会用到的词汇：算法、系统设计、行为面、职业英语连接词。
• STAR 方法（Situation、Task、Action、Result）是每一道行为题的结构骨架。每段对应的词汇必须会。

---

技术面试词汇是隐藏的胜负手

LeetCode 题你能解，最优时间复杂度你知道，真公司里你 ship 过生产代码。但当面试官说「walk me through your approach」，你脑子一片空白。不是不知道答案，是不知道怎么用英语说。

这不是个例。这是 FAANG 和顶级初创面试里非母语者的常态。

在竞争激烈的工程招聘中，技术门槛是过滤器，不是分水岭。当每个候选人都能解 LeetCode 中等题，沟通质量才是把 offer 和拒信分开的东西。Google、Meta、Amazon、Microsoft 的面试官明确评估你「能多清晰地表达思考过程」：你能不能解释一个 trade-off、描述一个系统约束、用精准框架抛出一段行为面例子。

对中国、日本、韩国工程师——全球技术池里最强的一批——这个沟通差距代价不成比例地高。关于非母语者在高风险口头评估中的研究稳定显示：让人显得「不胜任」的主要原因是词汇缺口，不是语法错误。你知道你想说什么，只是当下找不到那个英语词。

这个挑战有四个维度。

第一，技术词汇是抽象的。 Algorithm、complexity、bottleneck、trade-off——很多东亚语言里没有直接对应。翻译不了，你必须把它们当作「映射到英语词」的概念来学。

第二，行为词汇是文化性的。 Ownership、ship it、rubber duck debugging、retrospective 是文化特有的词，带着硅谷工程文化的内涵——它们的字面翻译里没有。

第三，精准比流利更重要。 面试官不需要你听起来像母语者，需要你精准。「This solution is O(n log n) which is better than the naive O(n²) approach, but the trade-off is increased space complexity」传递的是智识。模糊的英语正相反。

第四，压力下沟通会退化。 焦虑会缩窄词汇通道。你只是「半会」的词，紧张时第一个消失。解药不是放松，是把词汇自动化到「即便压力下也调得出来」。

这份指南给你 80 个按面试场景组织的词，附定义和个性化例句。也给你结构性框架（STAR、系统设计语言、职业连接词），让面试官觉得你思路清晰。

---

第一节：80 个技术面试词汇，4 大类

每条三件套：词或短语、面试专属定义、按中级水平写的个性化例句——你真在面试里会说的那种，不是课本式。

A 类：数据结构与算法词汇

每场编码面试都会用到的 20 个词。它们描述你的解法做什么、表现如何、为什么这么选。

词 / 短语	面试定义	例句
algorithm	解决问题的分步过程	"My algorithm processes each node once, so it runs in linear time."
complexity	资源使用随输入规模增长的衡量	"The complexity of this approach improves from quadratic to linearithmic with a better data structure."
time complexity	算法运行时间随输入规模如何变化	"The time complexity of binary search is O(log n), which makes it efficient for large datasets."
space complexity	算法随输入增长用多少额外内存	"By reusing the input array instead of allocating a new one, I reduced the space complexity to O(1)."
optimization	提升解法效率或正确性的过程	"The first step in my optimization was to eliminate redundant computations inside the inner loop."
iterate	用循环反复执行	"I iterate through the array once, keeping track of the maximum value seen so far."
recursion	函数调用自身解决更小同型问题	"Recursion is natural here because the tree structure is self-similar at every level."
trade-off	改善一处会让另一处变差的取舍	"The trade-off between time and space complexity is the central design decision in this problem."
edge case	输入或条件在期望范围的极端边界	"I should handle the edge case where the input array is empty before entering the main logic."
bottleneck	制约整体性能的部分	"Profiling revealed that the database query was the bottleneck, not the sorting algorithm."
latency	指令到数据传输开始之间的延迟	"Adding a cache reduces latency for repeated requests because the data no longer needs to be recomputed."
throughput	单位时间内完成的工作量	"To increase throughput, we can process requests in parallel instead of sequentially."
scalability	系统在不降级的情况下处理增量负载的能力	"The design lacks scalability because every new user doubles the number of database writes."
refactor	重构现有代码而不改变外部行为	"I would refactor this into a helper function to make the logic reusable and easier to test."
modular	设计成独立、可替换的组件	"Keeping the code modular means we can swap out the sorting function later without touching the rest."
abstraction	把实现细节藏在简单接口背后	"Using a stack as an abstraction here means the calling code doesn't need to know how the data is stored internally."
encapsulation	把数据和操作它的函数捆绑、隐藏内部状态	"Encapsulation keeps the class's internal state safe from external modification."
debugging	识别并修复代码错误的过程	"During debugging, I added logging statements at each step to trace where the value was going wrong."
iteration	一次完整的循环遍历或一个重复周期	"Each iteration of the outer loop processes one row of the matrix."
constraint	输入、时间或内存上的限制，决定有效解法空间	"Given the constraint that the array is sorted, we can rule out any O(n²) approach."

---

B 类：系统设计词汇

系统设计面试在测你能不能在「规模」上思考。这 20 个词是分布式系统的语言——「设计一个 URL shortener」或「你怎么搭 Twitter」时面试官期待听到的。

词 / 短语	面试定义	例句
architecture	系统的高层结构与组件如何互动	"Before diving into components, I want to describe the overall architecture and then zoom into each layer."
microservices	把应用建成一组小、独立部署的服务	"Migrating from a monolith to microservices allowed each team to deploy their service independently."
monolith	单一统一的应用，所有组件紧耦合	"Starting as a monolith makes sense here — we can extract services later once the domain is better understood."
distributed system	组件运行在多台机器上、通过网络通信	"In a distributed system, we have to assume that any node can fail at any time."
load balancing	把请求分到多台服务器上以避免单台过载	"Load balancing across three server instances ensures no single server becomes a bottleneck."
caching	把高频访问数据存到快速内存里以减小读取时间	"Caching the top 1% of URLs would handle the vast majority of read traffic without hitting the database."
database sharding	把数据库切成更小、更快、跨多机管理的块	"With 10 billion rows, database sharding by user ID would keep each shard's size manageable."
redundancy	组件冗余以提升可靠性与可用性	"Adding a secondary replica provides redundancy — if the primary fails, traffic fails over automatically."
fault tolerance	部分组件失效时系统仍正确运行的能力	"Fault tolerance at this layer means replicating the message queue across three availability zones."
consistency	分布式系统中所有节点同时看到相同数据的保证	"There's a fundamental tension between consistency and availability in a distributed database."
availability	系统可用且可访问的时间比例	"The design targets 99.9% availability, which allows for less than 9 hours of downtime per year."
partitioning	把数据或功能跨多个节点或系统切分	"Horizontal partitioning by region reduces cross-region latency for most users."
API gateway	充当所有客户端请求单一入口、把请求路由到合适服务的服务器	"The API gateway handles authentication and rate limiting before requests reach any internal service."
rate limiting	在给定时间窗口里控制客户端能发的请求数	"Rate limiting at 1,000 requests per minute per user prevents a single client from overwhelming the system."
message queue	在生产者和消费者之间存消息、解耦两者的缓冲	"Using a message queue means the notification service can fall behind without affecting the core transaction flow."
pub/sub	发布者向主题发消息、订阅者接收的消息模式	"The pub/sub model here means adding a new consumer — say, an analytics service — requires zero changes to the publisher."
CDN	Content Delivery Network — 地理分布的服务器网络，把静态内容投递到离用户更近的地方	"Serving static assets through a CDN reduces page load time from 800ms to 90ms for users in Asia."
horizontal scaling	加机器以处理增量负载	"Horizontal scaling is preferable here because the workload is stateless and easy to distribute."
vertical scaling	提升单机容量（更多 CPU、RAM、存储）	"Vertical scaling has a ceiling — at some point you can't buy a bigger server, and the cost grows non-linearly."
technical debt	现在选了更快更易方案、未来需要更多功夫修复的成本	"The current implementation has significant technical debt — we took shortcuts to hit the launch deadline that we'll need to pay back."

---

C 类：行为面词汇

行为题（「Tell me about a time you...」）不是软问题，是对你判断、协作、影响力的结构化评估。这 20 个词就是评估的语言。

词 / 短语	面试定义	例句
initiative	不被指示就主动行动，预判需要做的事	"I took the initiative to write the post-mortem document before the team lead asked, which helped us identify the root cause faster."
accountability	为行动及其结果负责，包括失败	"When the deployment caused a 30-minute outage, I owned the accountability — I wrote the incident report and presented it to the team."
stakeholder	任何对项目结果有利益相关或受其影响的人	"Aligning with stakeholders early meant we avoided a three-week rework cycle when requirements changed."
cross-functional	涉及不同部门或学科的人/团队	"I led a cross-functional effort between engineering, product, and legal to ship the data privacy feature on time."
ownership	把项目或领域当成自己的责任的心态，超越正式职责	"Ownership in this context meant I stayed through the incident until the root cause was resolved, even though it wasn't technically my service."
retrospective	项目或冲刺后召开的结构化复盘会	"After the launch failure, we ran a retrospective and identified three process gaps we've since addressed."
iterate (agile)	先发可用版本，再基于反馈在循环里改进	"We chose to iterate on a minimal version first rather than spend six months building the complete solution."
ship	把功能或产品发给用户	"The goal of that sprint was to ship a working prototype that internal users could test before the end of Q3."
feedback loop	收集结果信息、用于改进未来行动的机制	"We added user analytics to create a tighter feedback loop — we could see within 48 hours whether the change was working."
scope creep	项目需求逐步超出原边界扩张	"Scope creep was the primary risk — we had to make a deliberate decision to defer three features to the next release."
align	让不同方就共享理解或方向达成一致	"Before writing a single line of code, I aligned with the product manager on what success looked like."
escalate	把当前层级解决不了的问题升级到更高层	"When I couldn't get a decision on the API contract, I escalated to my manager, who resolved it with the other team lead in one meeting."
prioritize	按相对重要或紧急排序任务/目标	"Given the two-week deadline, I had to prioritize the features by user impact and deprioritize anything that wasn't on the critical path."
impact	你的工作对用户、业务或技术结果的可衡量影响	"The impact of the caching layer was a 60% reduction in database load, which directly lowered our infrastructure costs."
influence	改变他人方向、行为或观点，尤其是在没有正式权力时	"I influenced the team's decision to adopt the new framework by writing a comparative analysis and presenting it at the tech review."
mentor	通过建议、反馈、知识分享指导更资浅的成员	"I mentored two junior engineers during my time there, pair-programming with them weekly and reviewing their design documents."
collaborate	与他人共同朝目标工作，主动贡献并协调	"The feature required me to collaborate closely with the mobile team, which meant daily syncs and shared documentation."
deliver	在约定的范围、质量、时间内完成并交付	"Despite the ambiguous requirements, I delivered a working API within the sprint timeline by making early, explicit assumptions and validating them."
pivot	基于新信息或结果做出重大方法转变	"Three weeks in, user testing showed our initial approach was wrong. We had to pivot quickly, which meant cutting two planned features."
drive	通过主动努力和领导推进项目	"I drove the migration project from start to finish — coordinating across four teams and delivering it two weeks ahead of schedule."

---

D 类：通用职业英语连接词

这些不是技术词，是面试沟通的连接组织——展示你思路清晰、合理限定陈述、与面试官问题深度互动的短语。

非母语者常常会技术词汇但缺少这些职业连接词。没有它们，回答听起来支离破碎、过度自信或闪烁其词。有了它们，回答听起来结构化、像 senior。

短语	功能	面试中的例子
elaborate	暗示要展开细节	"Could you elaborate on the scale requirements? That would change my design significantly."
clarify	在开始前确认或澄清模糊点	"Before I start, I want to clarify — are we optimizing for read performance or write performance?"
rephrase	复述问题或观点以确认理解	"Let me rephrase that constraint to make sure I have it right: we have a 100ms SLA for 99th percentile response times?"
walk through	一步步带某人走过你的思路	"Let me walk through my reasoning before I write any code."
break down	把复杂问题拆成更小部分	"I'll break down the problem into three components: data modeling, API design, and caching strategy."
in terms of	指明你在讨论哪个维度	"In terms of time complexity, this is optimal. The question is whether the space trade-off is acceptable."
to elaborate	引入更详细的解释	"To elaborate on the latency concern — the bottleneck is the synchronous call to the third-party API, which we can't control."
to circle back	回到之前提出的点	"I want to circle back to the edge case I mentioned — it becomes important once we consider the concurrent write scenario."
approach	你提出的整体方法或策略	"My approach would be to start with a simple solution, establish correctness, and then optimize."
considerations	应当影响决策的因素	"The main considerations here are consistency requirements, expected read/write ratio, and team familiarity with the technology."
trade-offs	不同选项的代价与收益	"There are real trade-offs between these two designs, and the right choice depends on the read/write ratio."
in my experience	用个人经验限定一个陈述	"In my experience, starting with a monolith and extracting services later is less risky than starting distributed."
I'd argue that	引入一个你愿意为之辩护的立场	"I'd argue that the additional complexity of microservices isn't justified at this scale."
one way to think about it	提出一个心智模型或类比	"One way to think about this is that the cache is a buffer between the fast and slow parts of the system."
that said	承认前一观点后引入反点	"That said, there are scenarios where the simpler approach would fail — specifically, high-concurrency writes."
to be specific	暗示要给具体例子	"To be specific, I reduced query time from 1.2 seconds to 40 milliseconds by adding a composite index."
building on that	在已说的点上延伸	"Building on that — if we add a read replica, we can handle the read scaling without changing the write path at all."
to your point	承认并接住面试官说的话	"To your point about consistency — you're right that eventual consistency won't work here given the financial nature of the data."
the crux of the matter	指出最核心的点	"The crux of the matter is whether we prioritize write throughput or read latency — everything else follows from that decision."
it depends on	承认答案与语境相关	"It depends on the access pattern. If reads far outnumber writes, a cache makes sense. If writes dominate, it adds complexity without benefit."

---

第二节：STAR 方法词汇指南

STAR 是行为面试单一最重要的框架。每家大型科技公司（Google、Amazon、Meta、Microsoft、Apple）都明确使用「能力本位行为评估」，STAR 是被期待的回答结构。

STAR 的含义：

• Situation —— 背景与前提。你在哪里、发生了什么？
• Task —— 你的具体职责。你被期待做什么？
• Action —— 你实际做了什么。你采取的具体步骤。
• Result —— 可衡量的结果。因为你的行动发生了什么？

面试官想要的比例大致是 10% / 15% / 50% / 25%。多数候选人在 Situation 投入过多、在 Action 与 Result 上交付不足。这正是词汇最重要的地方。

STAR 开场短语

Situation 开场（快速搭场景）：

1. "This happened during my time at [company], when our team was responsible for..."
2. "The context was a critical migration project with a hard deadline of..."
3. "We were in the middle of a product launch when..."
4. "Shortly after I joined the team, we encountered a situation where..."
5. "During Q3 of last year, our service started experiencing..."

Task 开场（说明你的责任）：

1. "My specific responsibility was to..."
2. "I was accountable for delivering..."
3. "The task fell to me because..."
4. "I owned the end-to-end design and implementation of..."
5. "The team needed someone to drive the..."

Action 开场（展示主动与思考）：

1. "The first thing I did was..."
2. "I started by breaking the problem into three components..."
3. "My approach was to first understand the root cause before proposing any solution..."
4. "I decided to escalate early, because..."
5. "Rather than accepting the existing approach, I proposed an alternative by..."

Result 开场（用数字开头）：

1. "The outcome was a [X]% improvement in..."
2. "As a direct result, we reduced [metric] from X to Y..."
3. "The feature shipped on time and within budget, and subsequently..."
4. "We received direct feedback from the engineering director that..."
5. "The impact was significant: specifically, [quantified outcome]..."

完整 STAR 范例答

问题：「Tell me about a time you dealt with a difficult technical problem.」

Situation： 在公司第二年，我们的主产品 API 开始间歇性返回 500 错误，且只在高负载——具体说是高峰时段——出现。错误是非确定性的，在 staging 难以复现。

Task： 我被指派为负责定位根因并解决该问题的工程师。约束是我们在八天内有一场重大客户演示，那场上不能有不稳定。

Action： 我的做法是有方法的：在动任何代码前，我先分析错误日志以建立模式。我注意到错误与特定数据库查询模式相关，这暗示是瓶颈而不是代码 bug。我加细粒度日志去遍历调用栈、隔离问题。具体说，我发现一个特定 ORM 查询对一张 5000 万行表做全表扫描，因为缺少一个组合索引。我写了一份数据库迁移，先在副本环境测试以确认正确性，然后用功能开关部署，万一出错可立即回滚。我还回过头审查了其他五个最高流量查询，看是否有同类问题——又找到了两个。

Result： 修复在部署 24 小时内把错误率从约 0.8% 降到接近零。对 p99 响应时间的影响是从 1.4 秒降到 210 毫秒。客户演示顺利进行。我随后给团队写了一份指南，介绍如何识别和预防这类查询性能问题——之后我们在三次代码评审里用上了它。

注意起作用的词汇：constraint、approach、bottleneck、iterate、to be specific、circle back、impact。它们不是装饰，是给面试官的信号——你按结构化、职业的工程方式思考。

---

第三节：系统设计面试语言

系统设计面试没有唯一正解。面试官在评估你是否像 senior 工程师一样思考：能不能在模糊里搭出结构，能不能就 trade-off 说理，能不能清晰沟通你的决策。

下面的词汇模式是 senior 工程候选人的样子。学它们不是为了背稿，是为了内化它们代表的思考模式。

怎么组织你的回答

系统设计面试的前两分钟决定后面的轨迹。强候选人用一致的结构：

1. 先澄清需求。 「Before I start designing, I want to clarify a few things. What's the expected scale? Are we optimizing for reads or writes? What's the acceptable latency for the critical path?」

2. 明确陈述你的方法。 「My approach will be: define the data model, design the API, then talk through the main components and their interactions. I'll flag trade-offs as I go.」

3. 推到决定。 「Given the constraints you've described, I'd lean toward a SQL database over NoSQL here, because the relational structure of the data is a better fit. That said, if write volume exceeds X, we'd want to revisit that decision.」

10 个传递「资深思维」的信号短语

下面这些短语传达架构成熟度，出现在拿到强录用建议的候选人答中。

信号短语	它在传达什么
「The first question I'd ask is...」	设计前你先收集需求
「The trade-off between X and Y is...」	你在就竞争性关切说理
「A key consideration here is...」	你区分轻重
「I'd start simple and add complexity only when needed...」	你避免过早优化
「This assumes [assumption] — if that changes, the design would change significantly...」	你把假设说出来
「The bottleneck in this design is likely...」	你预判失败点
「One failure mode we need to handle is...」	你考虑韧性
「If I were to scale this to 10x traffic...」	你向前看而不丢失当前范围
「I would monitor this with...」	你考虑运维与可观测
「The simplest thing that could work is... and here's when we'd outgrow it...」	你理解系统的演化

非母语者常见错误

下面这些模式在非母语者英语面试里频繁出现，并稳定收到面试官的负面反馈。

错误 1：不澄清就直奔方案。

• 现象：候选人在需求确立前就开始描述具体技术。
• 面试官想：「他不问澄清问题。这在真实工程环境里是风险。」
• 修：「Before I propose a design, can I ask a few questions to make sure I understand the constraints?」

错误 2：描述而不决定。

• 现象：「We could use MySQL, or we could use Cassandra. Both have advantages. MySQL is relational. Cassandra is distributed.」
• 面试官想：「他能背事实，但不能下决断。」
• 修：「Given the read-heavy workload and structured data, I'd go with PostgreSQL. Here's why...」

错误 3：用模糊的正面修饰。

• 现象：候选人说「this is very efficient」「this approach is much better」。
• 面试官想：「按什么衡量更好？好多少？」
• 修：要具体。「This reduces time complexity from O(n²) to O(n log n), which matters at 10 million records.」尽量量化。

错误 4：从母语句法直译。

• 中文例：「这个问题，我想可以通过……解决。」 → 「I think this problem can be solved by using...」
• 日文例：在技术语境里过度使用 「I feel that...」 → 「My assessment is that...」或「The data suggests...」
• 韩文例：在英语里省略主语（英语必需）

错误 5：思考时沉默而不是出声。

• 现象：候选人思考时安静，让面试官以为他卡住。
• 修：把思考说出来。「Let me think about this for a moment... I'm considering whether the consistency requirement here rules out an eventually consistent store...」「卡住」和「在深思」之间，区别就在这里。

---

第四节：30 天面试前词汇冲刺

面试前四周，跑这套聚焦词汇冲刺。顺序很重要：算法→系统设计→行为→整合。

第 1 周 —— A 类：算法词汇

目标： 把 20 个算法词自动化到「讲代码时自然出现」。

每日练习（20 分钟）：

• 第 1—2 天：学前 10 个词。加进 Rhythm Word，做第一次 SRS。
• 第 3—4 天：学剩下 10 个，对全部 20 个做 SRS。
• 第 5 天：完整出声做一道 LeetCode Easy 或 Medium。强制使用 A 类至少 5 个词。
• 第 6 天：用想象的面试官，把两道你做过的 LeetCode 题讲一遍。录音。
• 第 7 天：复习 Rhythm Word 标记为弱的 A 类词，集中攻这部分。

第 1 周检查点： 你能不能不犹豫地用清晰英语解释 merge sort、binary search、hash table lookup 的时间空间复杂度？

第 2 周 —— B 类：系统设计词汇

目标： 能用精准词汇提出、对比、辩护系统设计选择。

每日练习（25 分钟）：

• 第 8—9 天：学前 10 个系统设计词。加进 Rhythm Word。
• 第 10—11 天：学剩下 10 个，对全部 20 个做 SRS。
• 第 12 天：选一道经典系统设计题（URL shortener、Twitter timeline、rate limiter），讲 15 分钟设计，强制使用 B 类至少 8 个词。
• 第 13 天：读一篇系统设计博客或架构文章。把每个语境中遇到的 B 类词记下来。
• 第 14 天：复习 Rhythm Word 标记的弱词，重做出声设计练习。

第 2 周检查点： 你能不能在 60 秒内解释「水平扩展 vs 垂直扩展」的 trade-off 以及何时选哪个？

第 3 周 —— C 类：行为词汇

目标： 准备好自然使用行为词汇的 STAR 答案。

每日练习（25 分钟）：

• 第 15—16 天：学 20 个行为词。加进 Rhythm Word。
• 第 17 天：从你自己的经验里写出三个 STAR 故事。每个故事至少用 3 个行为词。
• 第 18 天：出声练这三个故事，计时。每个回答 2—3 分钟。
• 第 19 天：聚焦 Result 部分。把每个故事的结果段重写，加入具体数字或可衡量结果。
• 第 20 天：练最常见的五道行为题：
  • "Tell me about a time you had a conflict with a teammate."
  • "Describe a situation where you had to deliver under a tight deadline."
  • "Tell me about a time you made a significant technical decision."
  • "Give an example of a time you influenced a team without formal authority."
  • "Tell me about a time you failed."
• 第 21 天：复习 Rhythm Word 标记的弱行为词。

第 3 周检查点： 你能不能在 3 分钟内讲三个不同的 STAR 故事，每个至少含一个可衡量结果？

第 4 周 —— 模拟面试整合

目标： 在真实面试压力下整合所有词汇。

• 第 22—23 天：做两次模拟编码面。每次结束后，复盘哪些词没用上或被回避，加进 Rhythm Word 复习队列。
• 第 24 天：做一次模拟系统设计面（用 Pramp、interviewing.io 或朋友）。能录就录。
• 第 25 天：回看录音（或听练习伙伴反馈）。哪些词汇空缺浮出来？
• 第 26 天：在 Rhythm Word 集中复习第 22—25 天标出来的每一个空缺词。
• 第 27—28 天：再做两次模拟。这次主动用 D 类连接词（elaborate、walk through、circle back、to your point、it depends on），让它们感觉自然。
• 第 29 天：休息。不学新词。
• 第 30 天：在 Rhythm Word 里轻量复习最弱的 10 个词。只做信心会话。

月末检查点： 你能不能用本指南词汇做一次 45 分钟的完整模拟技术面（编码 + 系统设计 + 行为），不犹豫、不退回模糊语言？

---

常见问题

技术面试英语我需要哪些词汇？

四方面：（1）算法与数据结构 —— complexity、trade-off、edge case、recursion、bottleneck；（2）系统设计 —— architecture、scalability、fault tolerance、caching、consistency；（3）行为 —— ownership、accountability、impact、initiative、stakeholder；（4）职业连接词 —— "walk me through"、"to elaborate"、"the trade-off between X and Y"、"it depends on"。多数非母语者跨类覆盖不全。本指南给你全部 80 个。

怎么用英语描述算法？

按这个结构：说出算法、描述时间和空间复杂度、解释为什么适合这道题，然后说 trade-off。例：「My approach uses a two-pointer technique. The time complexity is O(n) since we traverse the array once, and the space complexity is O(1) since we're not using any additional data structures. The trade-off is that this only works if the input is sorted — which, given the constraints, it is.」

面试里「walk me through your approach」是什么意思？

意思是：在写代码前一步步解释你的思路。面试官想听你叙述推理——你怎么拆问题、考虑哪些 trade-off、为什么选这个数据结构而不是那个。这不是让你立刻动手写代码，是邀请你出声思考。强候选人会回应：「Sure. Let me start by clarifying the constraints, then I'll outline my approach before writing any code.」

英语技术面里怎么显得更自信？

三个具体技巧。第一，用结构性短语传递「有组织」的信号——「I'll break this into three parts」「the key considerations are X, Y, and Z」，让你听起来有意为之。第二，量化一切——「I reduced latency from 800ms to 90ms」远比「I improved the performance significantly」自信。第三，把假设说出来——「I'm going to assume the input array is sorted; I'll note where that assumption matters」。明示假设传达的是意识，不是软弱。

STAR 方法是什么？用什么词汇？

STAR 是 Situation、Task、Action、Result——回答行为题的框架。Situation 词汇：「The context was」「During my time at」「We were in the middle of」。Task 词汇：「I was responsible for」「I owned」「My accountability was」。Action 词汇：「My approach was to」「I escalated to」「I drove the」「I collaborated with」。Result 词汇：「The outcome was a [X]% improvement」「As a direct result」「The impact was」。关键比例：50% 在 Action，25% 在 Result。多数候选人花在 Situation 上——而那对面试官信息量最少。

---

结论

拿到 FAANG offer 的工程师并不总是能解最难 LeetCode 题的。他们是能把中等题解得清晰、能精准沟通思路、能让面试官相信「他来一起干活会舒服」的人。

对非母语者，这是一项可学的技能。不是天赋，不是运气。本指南里每一个短语都被真实工程师在真实面试里用过。词汇是有限的，框架（STAR、系统设计组织、出声推理）是可学的。

你的 30 天冲刺从一个决定开始：你现在哪个词汇空缺代价最大？

对在备考技术面的工程师，Rhythm Word 让你把本指南 80 个词中的任何一个加进来，配按你需要的语域（职业、技术、语境丰富）写的个性化句子学习。间隔重复引擎确保你复习的是你最弱的词，不是已经会的。

每自动化一个词，就是面试间里少一次犹豫。

在 App Store 下载 Rhythm Word：免费下载

---

想要更多职业英语词汇资源？也参见：

• 职场英语词汇：100 个让你听起来很专业的核心词
• 求职面试英语：60 个能帮你拿到 offer 的词与短语
• 主动回忆：让词汇真正留下来最快的方式
• 语境例句为什么是学词汇最高效的方式