商業英文：面試英文

英文面試考的不是英文能力，是「用英文展示思考」的能力。 這份是 B2B SaaS PM 面試常見題型 + 句型 + 必背 reverse Q。

面試英文 vs 日常英文：差別在哪

核心心法：面試是 demo 你「用英文做 PM 工作」的能力，不是「英文很好」。

Self Intro：三個版本背起來

30 秒版（電梯遇到 hiring manager）

I'm Maki, a B2B SaaS PM with 5 years of experience. Most recently I led pricing & growth at [Company], where I shipped a usage-based model that lifted NRR from 105% to 118%. I'm here because [specific reason — e.g., I want to work on infra products / I love your team's writing on X].

結構：Who + What + Quantified result + Why here.

60 秒版（onsite intro）

Quick background — I'm Maki, currently PM on the storage product line at [Company].

Three things to know about my background:

• Domain: 5 years in B2B SaaS, focused on infra and developer tools
• Strengths: I'm a metrics-driven PM — I went from BI analyst to PM, so I lean heavily on data
• Most recent win: shipped a usage-based pricing model that lifted NRR from 105% to 118%, which became the template for two other product lines

What pulled me to [Company] is [specific reason — e.g., your CEO's blog on X / your tech blog on Y / I'm a heavy user of Z].

Happy to dive into any of these.

2 分鐘版（Tell me about yourself）

加上：

• 一個「why PM」的 origin story（30 秒）
• 一個 specific career inflection point（30 秒）
• 為什麼想換工作（如果有）（30 秒）

結構：Origin → Path → Inflection → Why now → Why here

禁區：

• ❌ Walking through resume in chronological order（很無聊）
• ❌ I was born in Taiwan, then I went to college...（不需要 personal history）
• ❌ My English is not so good, please bear with me.（永遠禁止）

STAR：Behavioral Question 答題框架

Situation → Task → Action → Result

每段控制：

• Situation：30 秒（背景）
• Task：15 秒（你的角色 + 目標）
• Action：60 秒（最重要，講你做什麼）
• Result：30 秒（量化 + lessons）

關鍵句型

Pro tip：結尾主動加 lesson——比起「結果很好」，「結果好 + 我學到 X」更顯成熟。

經典 Behavioral Question + 答題模板

1. Tell me about a time you disagreed with your manager.

模板：

Last year my manager wanted to ship feature X for a big enterprise deal. I disagreed because [specific data point — e.g., only 8% of customers wanted it, eng cost was 3 months].

What I did:

1. Got curious first — set up a 1:1, asked her to walk me through her logic
2. Brought data — pulled the customer interview transcripts and shared a 1-pager with three options
3. Proposed a middle path — ship a smaller version in 4 weeks instead

Outcome: she went with the middle path. The smaller version landed the enterprise deal AND we kept Q3 timeline. Lesson: disagreeing isn't about winning, it's about expanding the option set.

2. Tell me about a project that failed.

規則：選真的失敗的（不要包裝成「失敗其實是成功」）。

模板：

[Project] was supposed to [goal]. We launched, and within 30 days [failure metric — e.g., adoption was 12% vs. 40% target].

Root cause analysis: I had over-indexed on [wrong assumption]. Looking back, I should have [specific corrective action].

What I did to recover:

1. Killed the feature publicly with a postmortem
2. Refunded customers who'd paid for it
3. Wrote up lessons internally — adopted by 2 other teams

Lesson: I now run a 5-customer interview minimum before any feature ships. Hasn't failed me since.

3. Tell me about a time you led without authority.

模板：

[Project] needed buy-in from 3 teams I didn't manage — eng, design, and sales.

Approach:

1. Did 1:1s first — understood each team's incentives before any meeting
2. Built a shared doc — listed each team's concern + how the project addressed it
3. Made the eng lead the visible owner — gave her the spotlight in the launch

Outcome: we shipped on time, eng lead got promoted, sales team adopted the playbook for 2 more projects.

4. Tell me about a time you killed a feature.

模板（最容易加分的題）：

Q1 we shipped feature X. Adoption was [low number] after 60 days.

Decision process:

1. Defined kill criteria upfront — if adoption < 15% by D60, sunset
2. Wrote sunset PRD — communicated to customers 30 days early
3. Replaced with [Y] — the use case became a workflow inside our existing tool

Result: NPS went UP after sunset (less feature bloat). Lesson: shipping isn't success — adoption is.

Product Sense Question 答題

「How would you improve [Product]?」

結構：

Three clarifying questions first:

1. Are we focused on a specific user segment or all users?
2. What's the success metric — engagement, revenue, retention?
3. Any constraints — eng resources, timeline?

[Wait for answer]

Got it. Let me think for 30 seconds.

[Pause]

OK — based on [their answer], I'd focus on [user segment]. Their JTBD is [specific job]. Today they struggle with [3 pain points]. The biggest opportunity is [one of them] because [why].

Three solutions, ranked by RICE:

1. [Solution A] — high impact, medium effort
2. [Solution B] — medium impact, low effort
3. [Solution C] — high impact, high effort

I'd start with [B] because we can validate the hypothesis cheaply.

Want me to dive deeper into one?

「Estimate the market size for X.」

結構：

Let me think out loud. Top-down or bottom-up?

[Choose one]

Bottom-up:

• Total potential users: [number, with assumption]
• % addressable: [X%]
• Average revenue per user: [$X]
• Total: [$X]

Sanity check against top-down: [different angle]

Lower bound / upper bound: [$X — $Y].

Want me to stress-test any assumption?

Reverse Question：你必問的 5 題

面試到結尾：「Do you have questions for us?」

答 No = 你不感興趣 = 你 out。

必問清單

Q1：Role 細節

What does success look like in this role at 30 days, 90 days, and 1 year?

為什麼：show 你想清楚「怎麼做好這份工作」。

Q2：Team / Manager

If I'm hired, what's the first project I'd work on? Who would I work with?

為什麼：判斷你會不會被 dump 到沒人想做的爛 project。

Q3：Org dynamics

How do PM, design, and eng make decisions when they disagree?

為什麼：判斷組織健康度。回答含糊 = 內鬥嚴重。

Q4：Manager style

What's your management style? How often do you give feedback?

為什麼：判斷你跟 manager 合不合。Manager 答不出來 = 不熟管理。

Q5：Why this person joined

What made you join this company? What's kept you here?

為什麼：聽弦外之音。回答只有「pay」「benefits」 = 文化不健康。

加分版（不一定問，但問了顯得你 senior）

What's the biggest challenge the team is facing right now that I'd help solve? What would prevent someone from succeeding in this role? What's something the company is bad at that you're trying to fix? If I joined and looked back in 6 months, what would surprise me — good or bad?

禁問清單

• ❌ How much will I get paid?（Salary 不是 reverse Q 階段問）
• ❌ How many vacation days?（顯得你只關心福利）
• ❌ Can I work remote?（如果 JD 沒講要先研究，不是現場問）
• ❌ When can I expect to get promoted?（顯得 entitled）
• ❌ What does your company do?（準備不足的最大紅旗）

Salary Discussion：別先報數字

被問期望薪水時

❌ 直接報數字（你會吃虧）：

I'd like $180k base.

✅ 反問 + 推回：

Happy to talk numbers. To make sure we're aligned, what's the range for this role?

如果對方堅持要你先報：

Based on my research and what I'm currently making, I'm looking for something in the range of [X — Y] base, plus equity. But I'm flexible — what matters most is [factor — growth / scope / team].

收到 offer 後 negotiate

Thanks for the offer — really excited about the team. Couple of questions:

1. Is the base flexible? Based on [data point — competing offer / market rate], I was hoping for closer to [X].
2. What's the equity refresh cadence?
3. Sign-on bonus negotiable?

When do you need a decision?

Buy Time（思考時間）

被問難題不要立刻答。沉默 + 思考 = 顯得 thoughtful，不是顯得弱。

中式英文陷阱（面試專用）

Cheat Sheet（一頁回顧）

1:1 模擬：經典開場 + 收尾

開場（被問 Tell me about yourself）

Sure. Quick background — I'm Maki, currently PM on [team] at [company]. Three things to know: [3 bullets] What pulled me to [Company] is [reason]. Happy to dive into any of these.

收尾（你問完 reverse Q 後）

Thanks — really enjoyed the conversation. The thing that stood out to me is [specific moment in interview, show you were listening]. What are next steps?

收到 reject

Thanks for letting me know, and for the feedback. Specifically on [point], that's a fair call — I'll work on it. Would love to stay in touch in case future roles come up.

📚 延伸閱讀：

• 商業英文 Email 寫作
• 商業英文：會議 / 視訊發言
• 商業英文：簡報 / Demo
• 商業英文：Slack / PR / 非同步
• 商業英文：談判 / Push-back
• Nora 主講義：CloudWave PM 面試講義 v3