我既在 Target 面试过，也在更早几年通过 vendor 合作关系和他们的技术组织有过比较近的接触。所以我对他们 behavioral 面试到底在测什么、为什么这么测，有一个相对完整的认知。
Target 有一套他们称为「expectations」的价值观，用来要求 leader 和 individual contributor。面试中他们不一定会把框架名字说出来，但问题明显围绕这些主题：drive results、embrace change、take action with urgency、champion diversity and inclusion、以及协作。
我亲耳听过或从我辅导过的人那里收集到的 behavioral 问题： "Tell me about a time you had to change course on a project midstream. What happened and how did you decide to pivot?（讲讲你在一个项目进行到一半时不得不改变方向的一次经历。发生了什么，你是怎么决定转向的？）" "Describe a situation where you had to influence without authority.（描述一次你需要在没有正式权力的情况下施加影响的情境。）" "Tell me about a time you had to balance speed and quality when you couldn't have both.（讲讲一次你在速度和质量不可兼得时如何权衡的经历。）" "How have you built relationships with a team that didn't report to you?（你是如何和不向你汇报的团队建立关系的？）" "Give me an example of a time you advocated for a team member or peer.（举一个你为团队成员或同事发声支持的例子。）"
这些不一定是逐字引用，但很有代表性。共同点是：他们想看你能在快速变化的环境里运转（零售本来就波动大），你能跨职能建立关系（门店运营、商品、供应链、数字化都得协作），以及你会考虑对人的影响，而不只是技术产出。
对于 SWE 和 senior IC 岗，behavioral 通常是 30-45 分钟，会问 3-4 题。STAR 方法在这里很好用。我补充一点：确保你的故事有明确结果，并带上数字或业务结果。「We improved checkout latency by 20% which reduced cart abandonment」比「我们把页面做快了」强很多。他们是数据驱动的公司。
如果你来自纯 startup 背景，跨职能协作这个主题可能需要多想想。准备一些能体现你和非工程角色一起朝共同目标推进的故事。
4 条回复
apm_aisha (Primly starter)
他们对 PM 岗也是用同一套 behavioral 框架吗，还是会稍微不一样？我问是因为那个“influence without authority”问题感觉特别 PM 向。
由 AI 翻译，查看原文
sec_sasha (Primly starter)
对 PM 来说非常类似。“influence without authority”这个问题在 PM 岗上几乎一直会出现。你也会被问更多关于你怎么排优先级、以及你如何处理和 engineering 或 design 的分歧。但底层看重的价值观是一样的。
由 AI 翻译，查看原文
laidoff_lena (Primly starter)
「速度 vs 质量」这个问题其实挺难的，表面上很简单。很多人会答「我找到一个平衡点」。但说实话，我觉得面试官想看的是：你真的遇到过没法两全的情况，并且做过一次真实取舍，而不是一个圆滑的“不置可否”。
由 AI 翻译，查看原文
Primly Team
One stage people underestimate in Target loops is the debrief-ready specificity of your stories. Behavioral prompts can sound broad, but interviewers usually need enough concrete detail to map your example to a leadership expectation without guessing.
A useful structure is STAR plus two add-ons: Constraints: what made this hard (time, ambiguity, dependencies, guest impact). Tradeoff + principle: the explicit decision rule you used (speed vs quality, customer vs internal, short vs long term).
Common failure mode is narrating activity instead of decision making. If your story does not include at least one moment where you chose between options and can explain why, it often reads as “team did a project” rather than “you led through uncertainty.”
For folks who have been through Target interviews, what’s one follow-up question you got that surprised you, and how did you adjust your answer in the moment?