技術面試英文詞彙：80 個拿下 FAANG offer 的字
掌握 80 個技術面試必備詞彙，分四大類（演算法、系統設計、行為面試、職場英文），附定義、個人化例句，加上 30 天學習計畫。
重點摘要：你需要知道的 3 件事
- 英文技術面試是雙重挑戰：你要展現 CS 知識，又要用第二語言精準表達。多數非母語者掉分在溝通，不在概念。
- 80 個字、4 大類 涵蓋你真正會用到的詞彙：演算法、系統設計、行為面試、職場英文連接詞。
- STAR 法（Situation、Task、Action、Result）是每個行為題的結構骨架。每個段落的詞彙會用就是必備。
為什麼技術面試詞彙是隱藏的勝負點
你會解 LeetCode、會算最佳時間複雜度、在真實公司送過 production code。但面試官說「walk me through your approach」時，你會空白——不是不會答，是不知道用英文怎麼說。
這不是少見情況。對 FAANG 和頂級新創面試的非母語英語人士來說，這是常態。
在競爭激烈的工程招募裡，技術門檻是篩子，不是分水嶺。當每個候選人都能解 LeetCode Medium，溝通品質才是 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 個字你在每場 coding 面試都會用。它們描述你的解法做了什麼、效能如何、為什麼這樣選。
| 字／片語 | 面試定義 | 例句 |
|---|---|---|
| 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（敏捷） | 先快速釋出可運作版本，再依回饋反覆改善 | "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 類：面試的職場英文連接詞
這些不是技術詞，是面試溝通的結締組織——顯示你思路清晰、合宜地修飾陳述、與面試官的問題對話的片語。
非母語者常常會技術詞彙、缺這些職場連接詞。沒有它們，回答聽起來零碎、過度自信、或閃躲。有了它們，回答聽起來結構分明、像資深工程師。
| 片語 | 功能 | 面試中的範例 |
|---|---|---|
| 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 開場（迅速設定場景）：
- "This happened during my time at [company], when our team was responsible for..."
- "The context was a critical migration project with a hard deadline of..."
- "We were in the middle of a product launch when..."
- "Shortly after I joined the team, we encountered a situation where..."
- "During Q3 of last year, our service started experiencing..."
Task 開場（聲明你的負責範圍）：
- "My specific responsibility was to..."
- "I was accountable for delivering..."
- "The task fell to me because..."
- "I owned the end-to-end design and implementation of..."
- "The team needed someone to drive the..."
Action 開場（展示你的主動性與思考）：
- "The first thing I did was..."
- "I started by breaking the problem into three components..."
- "My approach was to first understand the root cause before proposing any solution..."
- "I decided to escalate early, because..."
- "Rather than accepting the existing approach, I proposed an alternative by..."
Result 開場（用數字開頭）：
- "The outcome was a [X]% improvement in..."
- "As a direct result, we reduced [metric] from X to Y..."
- "The feature shipped on time and within budget, and subsequently..."
- "We received direct feedback from the engineering director that..."
- "The impact was significant: specifically, [quantified outcome]..."
完整 STAR 範例答案
題目：「Tell me about a time you dealt with a difficult technical problem.」
Situation： During my second year at the company, our main product API started experiencing intermittent 500 errors that only appeared under high load — specifically during peak traffic hours. The errors were non-deterministic and difficult to reproduce in staging.
Task： I was assigned as the engineer responsible for identifying the root cause and resolving the issue. The constraint was that we had a major customer demo in eight days, and the instability was unacceptable for that event.
Action： My approach was methodical: I started by analyzing the error logs to establish a pattern before touching any code. I noticed the errors correlated with specific database query patterns, which suggested a bottleneck rather than a code bug. I added granular logging to iterate through the call stack and isolate the problem. To be specific, I found that a particular ORM query was performing a full table scan on a 50-million-row table because a composite index was missing. I wrote a database migration, tested it in a replica environment to verify correctness, and deployed it with a feature flag so we could roll back instantly if anything went wrong. I also circled back to review the other five highest-traffic queries to check for the same issue — I found two more.
Result： The fix reduced the error rate from approximately 0.8% to near zero within 24 hours of deployment. The impact on p99 response time was a reduction from 1.4 seconds to 210 milliseconds. The customer demo proceeded without any issues. I subsequently wrote a documentation guide for the team on identifying and preventing this class of query performance issue, which we've used in three code reviews since.
注意詞彙是怎麼運作的：constraint、approach、bottleneck、iterate、to be specific、circle back、impact。這些不是裝飾，是給面試官的訊號：你用結構化、專業的工程語言思考。
第三節：系統設計面試的語言
系統設計面試沒有單一正解。面試官評量的是你像不像資深工程師思考：能不能在模糊中建立結構、推理 trade-off、清楚溝通決策？
下面的詞彙模式就是資深候選人聽起來的樣子。研讀它們不是為了背腳本，是為了內化它們代表的思考模式。
怎麼結構化你的回答
系統設計面試前兩分鐘決定後面所有走向。強候選人會用一致結構：
-
先釐清需求。 "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?"
-
明確說出你的方法。 "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."
-
推進到決定。 "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：直接從母語句構翻譯。
- 中文範例："This problem, I think can be solved by using..." → "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 個演算法字自動化，讓你談 code 時自然出現。
每日練習（20 分鐘）：
- 第 1–2 天：學前 10 個字，加進 Rhythm Word，完成第一段 SRS。
- 第 3–4 天：學剩下 10 個字，全部 20 個都跑完 SRS。
- 第 5 天：完整出聲解一題 LeetCode Easy 或 Medium，逼自己用至少 5 個 A 類詞彙。
- 第 6 天：跟想像的面試官解釋兩題你之前解過的 LeetCode，錄下自己。
- 第 7 天：複習 Rhythm Word SRS 標記為弱的 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 分鐘，逼自己用至少 8 個 B 類字。
- 第 13 天：讀一篇系統設計部落格或架構文章，記下你在語境中遇到的每個 B 類字。
- 第 14 天：複習 Rhythm Word 標記字，重複出聲設計練習。
第 2 週檢查點： 你能不能在 60 秒內解釋水平與垂直擴充的 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 天：做兩場 mock coding 面試。每場後檢討錯過或迴避了哪些詞彙，加進 Rhythm Word 複習隊列。
- 第 24 天：做一場 mock 系統設計面試（用 Pramp、interviewing.io 或朋友）。可能的話錄下來。
- 第 25 天：聽錄音回放（或請練習夥伴給回饋）。哪些詞彙落差出現了？
- 第 26 天：聚焦 Rhythm Word session，複習你在第 22–25 天標為落差的每個字。
- 第 27–28 天：再做兩場模擬面試。這次主動使用 D 類連接片語（elaborate、walk through、circle back、to your point、it depends on），讓它們感覺自然。
- 第 29 天：休息。不加新詞。
- 第 30 天：在 Rhythm Word 輕度複習你最弱的 10 個字。只做信心 session。
月度檢查點： 你應該能進行一場 45 分鐘的模擬技術面試（coding、系統設計、行為），用本指南的詞彙不結巴、不退回模糊語言。
常見問題
英文技術面試需要什麼詞彙？
你需要四個領域的詞彙：（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" 是什麼意思？
意思是：寫 code 之前一步步解釋你的思路。面試官想聽你敘述你的推理——你怎麼拆解問題、考量哪些 trade-off、為什麼選某個資料結構而非另一個。它不是在叫你立刻開始寫 code，是在邀請你出聲思考。強候選人會這樣回："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 讓你把本指南任何一個字加進去，用你會需要的精準語體（職場、技術、情境豐富）的個人化例句學習。App 的間隔重複引擎確保你複習的是最弱的字，不是已經會的字。
你自動化的每個字，就是面試裡少一次猶豫。
在 App Store 下載 Rhythm Word：免費下載
要找更多職場英文詞彙資源？也參考：
Rhythm Word 已在 iOS 上架。如果我們對單字學習的思考方式讓你產生共鳴，歡迎下載試試看。
Download on the App Store