英語面試最常見的問題：用 STAR 在 45 到 180 秒內答好行為型問題
行為型問題不是事實題：面試官在等你說出情境、任務、行動與結果。本文用 45、90、120、180 秒四種長度拆解 STAR，並教你用英語面試最常見的問題練習，避開模糊代名詞與假設語氣。
目錄
面試進行到一半時，問題會改變形狀：Tell me about a time when you had to deal with a difficult stakeholder. 在它之前的事實型問題，會在你停止說話時結束。這一題不會自己結束，因為面試官不是在等資訊——他們在等四個具體的東西，而且只要第一個拖得太久，他們就會打斷。
為什麼行為型問題的回答方式不同於事實型問題
事實型問題有面試官可以核對的答案；How many years have you used Python? 花八秒就能答完，多餘細節只會扣分。行為型問題則是一個問題裡藏著四個答案，面試官會在你說話時同時填四個格子。
英國 National Careers Service 把這些格子定義為 situation、task、action 和 result。西北地區政府發布給面試官的講義把檢查點說得很清楚：清楚陳述情境或任務、採取的行動，以及結果或成果，而且全都來自一個具體事件，而不是描述你平常怎麼工作。
這就是為什麼兩者表現如此不同。美國人事管理辦公室把結構化面試描述成：對每位候選人問同樣事先寫好的主問題與追問，並依照你抵達前就設定好的基準評分；面試官不是從白紙上蒐集資訊，而是把你的話拿來對照一把尺。
時間順序不是那把尺。照順序敘述專案，會用整整一分鐘填滿一個格子，卻讓另外三個空著，而追問 And what did you personally do? 就表示你的答案被歸類成背景。
STAR 回答的四個部分，以及各佔多少時間
這四個部分不是均等的四等份。華盛頓大學職涯中心發布的指南建議大約 20% situation、10% task、60% action 和 10% result。不均等正是重點：面試官想買的是你的決策，而決策就住在 action 裡。
| 部分 | 面試官在聽什麼 | 佔答案比例 |
|---|---|---|
| Task | 該由你解決什麼，而不是團隊的職責範圍 | 約 10% |
| Action | 你做了哪些決策，包括你否決了什麼 | 約 60% |
| Result | 什麼改變了，以及你怎麼知道它改變了 | 約 10% |
這些比例一旦固定總時長，就會換算成秒數。以下所有數字單位都是秒。
| 總回答時間 | Situation | Task | Action | Result |
|---|---|---|---|---|
| 90 | 18 | 9 | 54 | 9 |
| 120 | 24 | 12 | 72 | 12 |
| 180 | 36 | 18 | 108 | 18 |
聽者最常迷失的兩個地方。第一個是開頭，在事件之前堆疊背景：I had been working on a project that had already been delayed, and we had had two meetings about it 用了三個動詞，卻還沒說出發生什麼事。先用簡單過去式點出事件，再只補上必要的背景。
第二個是轉入 action 的樞紐，也就是 we 接管的時候：We rebuilt the pipeline and we shipped it in three weeks. 寫給面試官的講義把使用 we 列為他們被提醒要留意的訊號，並準備好追問：What was your own role in that? 如果一句話讓團隊其他每個成員來說也成立，那它是背景，不是 action。
面試前就選好故事
故事要依照能力項目來選，不是依照時間順序，而且要在面試前選，不是面試中才選。英國 National Careers Service 指出，例子可以來自工作、家庭或志工經驗，如果你的工作經歷很短，這點尤其重要。
四個故事就能涵蓋大多數行為型面試流程：一次意見分歧、一個你補救的錯誤、一個不是你設定的截止期限，以及一次你必須改變別人想法的經驗。每個故事寫一張卡，五行就好：
- 何時、何地，附上期間或日期
- 對你以外的人來說，風險或利害是什麼
- 只有你能做的那個決定
- 你第一個採取的行動，用動詞寫
- 什麼改變了，附上一個數字或一個你能指出的產出物
接著每張卡都必須回答三個問題：這是一個單一事件，而不是一種習慣嗎？有沒有一個決定是沒有別人會做的？我能不能不靠猜測就說出結果如何？
Action 段落：說你做了什麼，不是團隊做了什麼
面試官受過訓練會聽代名詞，所以保留一個 we 交代背景，然後切換。三個動作可以撐起 action 段落：你看到什麼、你選擇什麼，以及你接著做了什麼。
先從診斷開始，因為這展現的是判斷力，而不是努力：I could see that three settings differed between the two environments, so I started there. 接著說選擇和沒走的路：I considered rebuilding the fixture data and rejected it, because the migration was already frozen. 然後用動詞說實際操作，並講明是誰做的：I fixed the setting I owned that afternoon and wrote the other two up for the platform team.
六個開頭句可以在口說英文中乾淨地開啟 action 段落，而且六個都維持第一人稱：
The first thing I did was...I could see that ... , so I decided to...I checked with ... before I...I chose ... over ... , because...I took it on myself to...What I changed was...
用你能站得住腳的結果收尾
兩句話就夠，只要其中一句可以被核對。站得住腳的數字，是你能在面試官面前重建出來的數字：你持續記錄的計數、你達成的日期、你測量過的時長。你無法重建的數字是負債，因為下一個問題就是 How do you know?
沒有數字時，就用對比和一個產出物：Before the change, every release needed a manual check that took an afternoon. After it, the same check ran inside the pipeline.
另外六個開頭句可以開啟 result 段落：
In the end...The result was ... after ... weeksBy the time I left...It is still ... todayMy manager used the same approach for...The number I can point to is...
然後停下來。不要補上你的優點總結，也不要加上沒人要求的教訓。停下來是答案的一部分：它讓面試官有空間問他們已經握在手上的追問。
四個示範答案：45、90、120 和 180 秒
以下四個答案描述同一場虛構的資料遷移，從一個決策長成一個完整故事。每一則都錄下自己回答，並對照上面的時間表。
45 秒：一個決策
Two weeks before a data migration, the test environment started failing every night.（情境）My job was to find out why before the freeze.（任務）I compared the two environments, found three settings that differed, fixed the one I owned and wrote the other two up for the platform team the same afternoon.（行動）The migration shipped on the closing date and the nightly failures stopped.（結果）
90 秒：利害關係、一個被否決的選項、一個數字
Two weeks before a data migration the test environment failed every night, and the migration could not move because the quarter closed on the same date.（情境）I owned the test environment; the platform team owned the pipeline that fed it.（任務）I compared the environments setting by setting and found three differences. I considered rebuilding the fixture data and rejected it, because the dataset was already frozen for the release. The setting that was mine I fixed that afternoon; the other two I sent to the platform team with the evidence attached.（行動）The migration shipped on the closing date, and nightly failures went from five a week to zero.（結果）
120 秒：意見分歧，以及後續追蹤
Two weeks before a data migration the test environment failed every night, the quarter closed on the same date, and the platform team believed the fault was in my environment while I believed it was in theirs.（情境）I owned the test environment and the release checklist, and I had to hand over a working result rather than an argument.（任務）Instead of reopening the argument, I built a comparison: the same job run in both environments, with the three differences printed side by side. I took the page to the platform lead and said I would fix the setting that was mine that afternoon if we agreed on the other two before the freeze. He accepted, and I wrote both shared fixes into the release checklist with owners.（行動）The migration shipped on the closing date, failures went from five a week to zero, and the comparison page became part of the handover document.（結果）
180 秒：學到什麼，以及之後改變了什麼
Two weeks before a data migration the test environment failed every night, the quarter closed on the same date, and the platform team and I were pointing at each other's systems.（情境）I owned the test environment and the release checklist, and the migration could not move until someone proved where the fault was.（任務）I stopped arguing and made the fault reproducible: the same job in both environments, with the three differences printed side by side. I showed the page to the platform lead, offered to fix my setting that afternoon if we agreed on the other two before the freeze, and he accepted. I wrote both shared fixes into the release checklist as checkboxes with owners, and asked the platform team to keep the comparison job running afterwards as a monitoring step.（行動）The migration shipped on the closing date, nightly failures went from five a week to zero, and the two settings became permanent checks in the release process.（結果）What I would do differently is start the comparison on day one: I spent three days reading logs before building the thing that answered the question in an hour.（學習）
用英語面試最常見的問題來練習
練習問題，而不是練習講稿。行為型問題會圍繞幾項能力打轉，所以把你預期會聽到的題目寫下來、打亂順序，然後抽到哪一題就答哪一題。從一份打亂排序的英語面試最常見的問題清單來練，可以避免排練變成背誦演講。英國 National Careers Service 補充了一個很適合排練的警告：用對話方式把你的重點說清楚，並隨時準備好回答關於你所舉例子的追問。
六個題目就能涵蓋很多範圍：
Tell me about a time you disagreed with a colleague.Describe a situation where you had to meet a deadline you did not set.Give me an example of a mistake you made and what you did next.Tell me about a time you had to change someone's mind.Tell me about a time you had to learn something quickly.Describe a situation where a customer was unhappy with what you did.
只需要一支手機的排練循環：
- 不帶筆記錄下一個回答。
- 對照上面的時間表，為四個部分計時；如果 situation 超過它的時段，表示故事開始得太早。
- 數一數 action 段落裡的第一人稱動詞。如果
we比I多，就重錄。 - 聽結果。如果沒有數字也沒有產出物，補上一個，並把那個句子單獨錄兩次。
- 把錄音播給另一個人聽，只問一個問題：我做了什麼？
如果沒有人陪你排練，AI 對話夥伴可以補上部分落差：HiBay 提供面試情境對話練習，並依照 IELTS 和 TOEIC 標準的分級回報口說表現，即使它無法判斷你的故事是否選對，也能抓出贅字和語速。
當你對這個問題沒有例子時
三個誠實的做法，依偏好排序。
移動情境，保留行為：The closest example I have is from a voluntary project rather than a job - is that useful? 英國 National Careers Service 指出，例子可以來自工作、家庭或志工經驗，所以場景不會讓這個故事失去資格；只有不相關的行為才會。
給出規模較小的版本，並說明它比較小：I have not run a team through a redundancy. What I have done is close a project inside a week when the client moved the launch date. 你不是在假裝規模相符；你是在交出一件真實、可以被評分的事。
說出你沒做過什麼，再搭橋：I have not handled a formal complaint. I have handled a customer who was given the wrong delivery date, and I did it in writing before I called.
三個做法都適用同一條規則：絕對不要用假設語氣回答。I would probably speak to my manager first 不是過去行為的證據，而寫給面試官的講義把條件式回答列為無法評分的回應。感受也有同樣的問題：I am very organised 是一種偏好，而 I kept the release checklist for eleven releases 是面試官可以寫下來的東西。
常見問題
英語面試中的 STAR 回答應該多長？
預設以 90 到 120 秒為目標。杜克大學職涯中心發布的指南把有力的 STAR 回答訂在一到兩分鐘，而 45 秒足以回答一項狹窄的能力。用上面的時間表維持結構，把約 60% 的時間放在 action。更長的回答只有在面試小組要求深入說明時才成立。
如果行為型面試問題我沒有例子，該怎麼辦？
使用工作以外的真實例子，並用一個子句說明；給出規模較小的情境版本，並說明它比較小；或說出你沒做過什麼，再搭橋到你擁有最接近的經驗。然後停下來，讓面試官重新調整問題。用假設語氣回答，例如 I would...，屬於不同的問題類型，而且面試官被要求把它當成無法評分的答案。