京东物流 · 第二轮:GM + HRBPJD Logistics · Round 2: GM + HRBP

⏳ 等 Crystal 排期⏳ Awaiting scheduling 预计 8/3–8/7 · 周中 ≥7PM ETEst. Aug 3–7 · midweek ≥7PM ET 视频 · 2 位面试官Video · 2 interviewers
对方 · 加拿大国家经理(GM,姓名待向 Crystal 索取,LinkedIn 不可见,推断中国派驻;2022 年那轮有过前任 → 他是第二任,背着「别重蹈 2022」的任务)+ HRBP(大概率 = Tina Wang,JDL 美国主体 Senior HRBP,Fontana,五年陪美国从 0 建到十几仓;招聘+培训背景、data-driven)。你的第一轮谈话记录就在他们手上。
本轮性质 · 第一轮是行政筛选(零技术、零案例)——真正的考核在这轮:GM 考业务判断力 + 技术深度,HRBP 复查动机 + 稳定性 + 薪资。主体/EOR 问题(§8)她能给权威答案。
Who · Canada Country Manager (GM — name still to get from Crystal; invisible on LinkedIn, likely China-seconded; the 2022 run had a predecessor → he's the second GM, carrying a "don't repeat 2022" mandate) + the HRBP (most likely Tina Wang, Senior HRBP of the JDL US entity, Fontana — five years staffing the US 0→dozen-warehouse buildout; recruiting + training background, data-driven). They are holding the notes from your first call.
What this round is · Round 1 was an admin screen — zero technical, zero case questions. The real evaluation happens here: the GM tests business judgment and technical depth; the HRBP re-checks motivation, stability, and comp. She can answer the entity/EOR question (§8) authoritatively.
一句话立场(开场与收尾都能用)

"我不是来建第一个仓的。我是来把已经跑起来的协同仓做满、把该转自营的部分算清楚、并把加拿大的方案打法固化下来的。"

📝 语言说明:切换 EN 只改指导文字要说的台词保持原语言——那是你实际要讲出口的话,翻译了就没用了。 📝 On language: the EN toggle switches the guidance only. Spoken scripts stay in their original language — those are the actual lines you'll deliver, so translating them would defeat the point.

§1排期确认前的行动清单Before the Slot Is Confirmed

Crystal 承诺「下周之内答复」;你 7/31 晚的 WhatsApp 跟进已送达。 Crystal promised an answer "within next week"; your Thursday-night WhatsApp follow-up was delivered.

🔴 拿 GM 姓名🔴 Get the GM's name
她来消息安排面试时,在回复里顺带问:"方便告知一下国家经理的姓名吗?我想提前做点功课。" 拿到 → 立即 LinkedIn 深挖 + 建人物档案 When she messages to schedule, ask in the same reply: "Could you share the Country Manager's name? I'd like to prepare properly." Once you have it → immediate LinkedIn dig + profile file
🔴 开场练熟🔴 Drill the opener
§3 的 90 秒中英开场练到脱口而出。第一轮英文开场散是最大扣分项;视频轮第一印象权重更高 Drill §3's 90-second opener in both languages until it's automatic. The scattered English opening was Round 1's biggest deduction; first impressions weigh more on video
🟡 离职原因🟡 Why-leave line
§4 的一句话干净版背熟——第一轮被追问两次,HRBP 大概率重演 Memorise §4's one-liner — it was probed twice in Round 1 and the HRBP will likely re-run it
🟡 8/7 前无消息🟡 Silent by Fri 8/7
发轻量跟进(WhatsApp,中文):"想问下上周的审核有进展吗?另外如果安排跟国家经理的面试,方便告知他的姓名吗?我想提前做点功课。谢谢!" Send the light nudge (WhatsApp, Chinese): ask whether last week's review has progressed, and for the GM's name in the same breath
🟢 视频工具🟢 Video platform
确认平台(Teams / 腾讯会议 / Zoom)→ 提前装好、登录、测摄像头与耳机 Confirm the platform (Teams / Tencent Meeting / Zoom) → install, log in, and test camera + headset in advance

§2口径锁定表 —— 与第一轮必须一致Story Lock — Must Match Round 1

Crystal 的谈话记录就在他们手上,任何数字前后不一致都是红旗。 They're reading Crystal's notes. Any number that shifts between rounds is a red flag.

顺丰团队S.F. team size
3 人 → 50 人 ⚠️ 逐字稿说 50、AI 纪要写 20 —— 统一说 50 3 → 50 people ⚠️ transcript says 50, the AI summary wrote 20 — always say 50
顺丰柜网S.F. locker network
0 → 2,000+ 服务点 · 年 1,000 万+ 件 · 5 年 0 → 2,000+ points · 10M+ parcels/yr · 5 years
加拿大现状Canada framing
「协同仓模式,多伦多 + 温哥华,下一步转自营」;英文用官方词 "co-managed warehouses"(出自 8/1 运营专员公开 JD) ⛔ 不再说「零仓库」「纯绿地」 "Co-managed warehouses in Toronto + Vancouver, moving to self-operated next""co-managed" is JDL's own term (from the Aug 1 Ops Specialist posting) ⛔ never "zero warehouses" or "pure greenfield" again
美国网络US network
「十几个仓库」(Crystal 原话)—— 不说 9 个 "A dozen-plus warehouses" (Crystal's words) — not 9
FoodsUp
多站点效率 +35% · 拣货 UPH +30% · 人力成本 −20% Multi-site efficiency +35% · picking UPH +30% · labour cost −20%
蒙特利尔仓Montréal warehouse
约 2 个月从零上线~2 months, zero to live
KPI 系统KPI system
「看板人工复核时间减少约 40%」 ⛔ 不说「从数小时到数分钟」(不实) "Cut manual dashboard review by ~40%" ⛔ never "from hours to minutes" (untrue)
Hive
域是 7 个:outbound / inbound / inventory / crossdock / returns / exceptions / platform 7 domains: outbound / inbound / inventory / crossdock / returns / exceptions / platform
薪资Salary
CAD $100–110K,第一轮已明确拒绝 $75K(见 §7 复查话术) CAD $100–110K; $75K was explicitly declined in Round 1 (re-check script in §7)
到岗 / 工签Start / status
3–4 周(Crystal 已确认没问题)· 合法身份无需协助 —— 已过关,别再展开 3–4 weeks (Crystal confirmed it's fine) · authorised, no sponsorship — settled, don't reopen
⛔ 禁区:2022 年那轮加拿大启动为什么停了 —— 绝不主动提(等于说「我知道你们失败过」)。人事变动 / 外卖亏损 / 价格战一律不碰。 ⛔ Forbidden: why the 2022 Canada launch stalled — never raise it (it says "I know you failed once"). Executive churn / food-delivery losses / price wars — all off the table.

§390 秒开场(视频版)The 90-Second Opener (Video Edition)

GM 大概率中文主导,但英文版先备好——若对方英文开场,前 90 秒就是英文。中途主动切换一次展示双语(第一轮这招奏效)。 The GM will likely run in Chinese, but have the English cold — if they open in English, the first 90 seconds are English. Switch languages once, deliberately, to demonstrate the bilingual requirement (it worked in Round 1).

中文版 · ≈90 秒

"我做物流和供应链十五年,一条主线:把仓储和末端履约,用系统和数据重做一遍

起点在顺丰,五年,把智能柜末端网络从零建到 2,000 多个点位,一年跑 1,000 万件以上;团队从 3 个人带到 50 个人。那段经历和你们现在的加拿大很像——我们也是先租仓起步,爆仓了我自己下去搬货,量起来了才申请预算上分拣设备。所以听 Crystal 说加拿大现在是协同仓、下一步转自营,我很清楚这个阶段该怎么走。

中间在 IRS Logistics 端到端上过一套 TMS,人工砍了 40%;现在在 FoodsUp 做 WMS 产品经理,仓库流程重构加移动化,多站点效率提升 35%——白天在仓里和运营对流程,晚上用中文对接大陆研发团队写 PRD,这个双语双时区的工作方式我已经跑了两年多。加拿大这边我也从零上线过一个仓,大概两个月跑通。

所以这个岗位吸引我的,就是它正好站在我最熟的位置上:客户方案、系统集成、和把打法写成 playbook。"

English version · ≈75 sec

"I've spent fifteen years in logistics and supply chain, with one thread through all of it: redesigning warehousing and last-mile fulfillment around systems and data.

I started at S.F. Express — five years building a smart-locker network from zero to over two thousand points, ten million-plus parcels a year, growing the team from three people to fifty. That chapter looks a lot like your Canada operation today: we also started with rented warehouses — when they overflowed I was moving parcels myself — and only invested in sorting automation once the volume justified it. So when Crystal described the partner-warehouse model moving toward self-operated, that's a stage I've personally run.

Since then I led an end-to-end TMS implementation at IRS Logistics that cut manual work by forty percent, and today I'm the WMS Product Manager at FoodsUp — warehouse redesign plus mobile migration, thirty-five percent efficiency gain across sites. Days in the warehouse with operations, evenings writing PRDs in Chinese with our China engineering team. I also launched a warehouse here in Canada from zero, in about two months.

This role sits exactly where I've done my best work: customer solutions, systems integration, and turning what works into a playbook."

三个不要 · 不要学历开头 · 不要倒序流水账 · 不要超过 2 分钟 Three don'ts · don't open with your degree · don't walk backwards through every job · don't exceed 2 minutes

§4「为什么离开现公司」—— 一句话干净版"Why Are You Leaving" — The Clean One-Liner

第一轮绕了三轮、被追问两次(「no particular reason?」)。这轮 HRBP 几乎必然复查。 Round 1 took three loops and two probes ("no particular reason?"). The HRBP will almost certainly re-run it.

中文版

"不是逃离。FoodsUp 的 WMS 是我从头带起来的,做得很完整;但那是支撑自家业务的内部履约,天花板看得到。我做得最好的阶段是从 0 到 1——这种机会在成熟公司十年碰不到一次,而你们加拿大正在这个点上。"

English version

"I'm not running from anything. I built FoodsUp's WMS from the ground up and it's in good shape — but it's internal fulfillment supporting our own business, and the ceiling is visible. My best work has always been zero-to-one, and that kind of opening comes up maybe once a decade. Canada is at exactly that point."

⛔ 说完就停。不要再补「我很稳定」「recruiter 来找我」—— 等下一题。 ⛔ Deliver it and stop. No "I'm very stable," no "the recruiter found me" — wait for the next question.

§5GM 预测题 —— 第一轮没考的,就是这轮要考的Predicted GM Questions — What Round 1 Skipped Is What Round 2 Tests

第一轮零技术、零案例。GM 一定会挖系统深度,视频轮大概率给场景题。 Round 1 had zero technical and zero case questions. The GM will dig into systems, and a scenario question is very likely on video.

T1「讲讲你的 WMS 重构具体做了什么」"Walk me through your WMS rebuild"
  • FoodsUp:流程重构 + 移动化迁移;7 大域(outbound / inbound / inventory / crossdock / returns / exceptions / platform) FoodsUp: process rebuild + mobile migration; 7 domains (outbound / inbound / inventory / crossdock / returns / exceptions / platform)
  • 结果:效率 +35% · 拣货 UPH +30% · 人力成本 −20% Results: efficiency +35% · picking UPH +30% · labour cost −20%
  • 关键词:先立 KPI 埋点——异常头几周就浮现,不拖到季末 Key line: instrument the KPIs first — anomalies surface in the first weeks, not at quarter-end
T2「客户系统怎么对接?」(API / EDI)"How do you integrate customer systems?" (API / EDI)
  • 顺丰:承运商 / 硬件 API 集成全栈管过 S.F.: ran carrier and hardware API integrations end to end
  • 顺丰中小商户 OMS:日发数百单的卖家零 EDI、无 IT 投入就能接入 —— 跨境卖家生态正需要这个 S.F.'s SMB-facing OMS: sellers shipping hundreds of orders a day onboarded with zero EDI and no IT investment — exactly what the cross-border seller ecosystem needs
  • FoodsUp:与大陆研发团队写 PRD → 上线部署到仓库(已经在跨时区对接中国团队) FoodsUp: PRDs with the China R&D team → deployed to the warehouse floor (already working cross-timezone with a China team)
T3「你懂 TMS 吗?」「数据这块自己动手吗?」"Do you know TMS?" / "Are you hands-on with data?"
  • TMS:IRS Logistics 端到端实施——需求→设计→UAT→切换;人工 −40%、效率 +25% TMS: end-to-end implementation at IRS Logistics — requirements → design → UAT → cutover; manual work −40%, efficiency +25%
  • 数据:Tableau 预测(顺丰混合车队成本模型)+ FoodsUp 看板 Data: Tableau forecasting (S.F. hybrid-fleet cost model) + FoodsUp dashboards
  • 挂钩:方案岗的定价与 IRR 模型正是同一套肌肉(美国同岗在职者自述日常 = P&L 模型 / 定价策略) The hook: a solutions manager's pricing and IRR models are the same muscle (the US incumbent describes the job as P&L modelling / pricing strategy)
🎯场景题:「跨境卖家要进加拿大,你怎么设计方案?」The case: "A cross-border seller wants into Canada — design the solution"
最可能的案例题(客户画像:TikTok / Temu / Amazon 生态)。练熟五步结构,内容自然流出。 The most likely case (customer profile: TikTok / Temu / Amazon ecosystem). Drill the five-step structure; the content will follow.
  1. 需求画像 —— SKU 数与体积、月单量与波动(旺季倍数)、销售渠道(TikTok Shop / Amazon FBM / 独立站)、货源地与清关路径、当前痛点(时效?成本?退货?) Profile the demand — SKU count and cube, monthly volume and its swings (peak multiples), channels (TikTok Shop / Amazon FBM / DTC), origin and customs path, current pain (speed? cost? returns?)
  2. 网络设计 —— 东西岸分仓判断:多伦多协同仓服务安省+东部人口带,温哥华接西岸+离港近;先单仓还是双仓看单量分布;协同仓现有产能优先,不承诺还没有的自营能力 Design the network — east/west split: Toronto partner warehouse covers Ontario and the eastern population belt, Vancouver takes the west coast and sits near the port; one site or two depends on volume distribution; use existing partner capacity first — never promise self-operated capability that doesn't exist yet
  3. 系统集成 —— 渠道订单 → OMS → WMS 链路;API 优先、小卖家给零代码接入(顺丰 OMS 经验);库存同步与超卖防护;退货流必须在方案里(加拿大退货成本高) Integrate the systems — channel order → OMS → WMS; API-first, zero-code onboarding for small sellers (the S.F. OMS play); inventory sync and oversell protection; returns flow must be in the design (returns are expensive in Canada)
  4. 成本与报价 —— 入库 / 仓储 / 拣包 / 耗材 / 尾程分项报价;尾程承运商组合(Canada Post / Purolator / 区域承运商)按重量段与邮编带选路;给客户看单票落地成本 vs 美国仓发加拿大的关税+时效对比 Cost and quote — line-item pricing across inbound / storage / pick-pack / materials / final mile; carrier mix (Canada Post / Purolator / regionals) routed by weight band and postal zone; show the customer landed cost per order vs. shipping from a US warehouse with duty + transit time
  5. SLA 与上线 —— 截单时间、当日/次日出库承诺、旺季保障;上线时间表(集成→UAT→试单→放量);上线后 QBR 机制 SLA and go-live — cutoff times, same/next-day ship commitments, peak coverage; launch timeline (integration → UAT → pilot orders → ramp); QBR cadence after go-live
收尾一句(呼应 JD 第六块)

"这套流程我会写成加拿大的标准件——报价表、入驻 SOP、集成规范模板——第二个客户直接按模板走。"

T4「协同仓爆仓 / SLA 掉了怎么办?」"Partner warehouse overflows / SLA slips — what do you do?"
  • 先讲故事:顺丰爆仓我自己下去搬货派货,之后才建输送带分拣 Lead with the story: when S.F. overflowed, I was on the floor moving and dispatching parcels myself — the conveyor sorting came after
  • 再讲机制:异常 SOP + 数据对账——我设计,运营专员执行,异常数据回流给我做方案迭代 Then the mechanism: exception SOPs + data reconciliation — I design them, the ops specialist runs them, and exception data flows back into solution iteration
T5「什么时候该转自营?」—— 他们自己最头疼的题"When should we go self-operated?" — their own hardest question
答好直接加分——这就是这个岗位存在的理由。 Nail this and you win the round — it's the reason the seat exists.
  • 三个触发条件:(稳定基线单量)· 成本结构(自营单票成本何时低于协同仓费率)· 客户承诺(SLA 或合规要求协同仓给不了) Three triggers: volume (a stable baseline) · cost structure (when per-order cost of own ops beats the partner rate) · customer commitments (SLAs or compliance a partner can't deliver)
  • 同构经验:顺丰混合车队自营 vs 3PL 成本模型——同一类决策,我建过模型 The parallel: S.F.'s hybrid fleet own-vs-3PL cost model — the same class of decision, and I built that model
  • 落点:「我 90 天内会交一份带 IRR / 回收期 / 触发条件的商业论证」 Land it: "Within 90 days I'd put a business case on the table with IRR, payback period, and trigger conditions"
T6「前 90 天你会做什么?」"What would your first 90 days look like?"
三十字版(完整版见 30-60-90 计划 v2)

"第一个月继承与诊断——摸清两地协同仓现状、算出使用率缺口、吃透 Fontana 方案库;第二个月产品化与首单——报价表、入驻 SOP、集成规范三件套本地化,端到端拿一个客户方案;第三个月交付与路线图——首客上线,交一份协同仓转自营的 IRR 商业论证。"

说完主动补:「我把这个写成了完整的 30-60-90 计划,面试后可以发给您。」(HTML 版已备好) Then offer: "I've written this up as a full 30-60-90 plan — happy to send it after the call." (The HTML version is ready.)
T7「15 年经验,为什么来做这个岗?」(GM 版)"Fifteen years — why this seat?" (GM edition)

"从 0 到 1 我做过三次——顺丰柜网、蒙特利尔仓、FoodsUp WMS。这种项目经验不是溢价,是保险:第一年会踩的坑我基本都踩过。而且我很清楚这不是总监岗——我看重的是方案经理是唯一横跨『客户』和『仓』两端的角色。"

English version

"I've done zero-to-one three times — the S.F. locker network, the Montréal warehouse, the FoodsUp WMS. On that kind of work, experience isn't a premium — it's insurance: the mistakes you'd make in year one, I've already made. And I'm clear this isn't a director seat — what I value is that the solutions manager is the only role spanning both the customer side and the warehouse side."

§6STAR 故事库 —— 8 个故事STAR Story Bank — 8 Stories

开口先讲数字(京东是数字文化:160 万单/天、99.99%)。每个故事用一句话落回加拿大收尾。切 EN 看英文版——两个语言版本都要练;GM 轮优先练 #1、#3、#4。 Lead with the number (JD's culture is number-saturated: 1.6M orders/day, 99.99%). Land every story back on Canada in one closing line. Toggle 中文 for the Chinese versions — rehearse both; for the GM round drill #1, #3, #4 first.

地图故事 → 考点对照Story → requirement map
  • #1 蒙特利尔绿地建仓海外仓规划 · 建站 SOP · 培训warehouse planning · site SOPs · training
  • #2 WMS 重构 → 移动端WMS 实施/上线 · 流程优化WMS implementation · process optimisation
  • #3 顺丰智能柜全栈生态🏆 端到端方案 + WMS/TMS/OMS + API 一次覆盖🏆 end-to-end solution + full WMS/TMS/OMS + API stack in one
  • #4 KPI 监控 + WarehouseIQ数据/KPI 驱动 · AI 新鲜度data/KPI-driven ops · freshest AI story
  • #5 拣货路径重设60 秒精益故事(快问快答用)the 60-second lean story (for quick probes)
  • #6 中小商户 OMS#3 的 OMS 层深挖 · 客户方案设计#3's OMS layer · customer-facing design
  • #7 开放 API 承运商集成#3 的集成层深挖 · UAT→上线#3's integration layer · UAT→go-live
  • #8 KMB 排班数字化团队/培训短板的补位故事covers the team-management gap
#1蒙特利尔绿地建仓(FoodsUp)Montréal greenfield launch (FoodsUp)
  • S:FoodsUp 只有多伦多一个仓;业务要在蒙特利尔建第二个履约站点——没本地团队、没流程、没本地化系统FoodsUp ran a single Toronto warehouse; the business needed a second fulfillment site in Montréal — no local team, no processes, no localized systems
  • T:从零建起——WMS 配置、作业流程、SOP、员工培训——紧迫时间表内跑稳stand the site up from zero — WMS configuration, workflows, SOPs, staff onboarding — and reach stable operations on a tight timeline
  • A:先复制再本地化(克隆 TRT 任务流,按 MTL 布局调整)· 带照片验收标准的任务级 SOP,新员工不靠口口相传 · 先埋点再扩张:KPI 看板上线即投用replicate, then localize (cloned Toronto's task flows, adapted to MTL's layout and labour model) · task-level SOPs with photo-evidence acceptance criteria so new hires didn't rely on word-of-mouth · instrument before you scale: KPI dashboards live from day one
  • R:约 2 个月上线;两站同一套 KPI/任务骨架,可跨站对比;成为多站点模板live in ~2 months; both sites on one KPI/task backbone, cross-site comparable; became the multi-site template
落点:「这就是加拿大从协同仓走向自营时要做的事——我在这块大陆上、双语市场里做过一遍。」 Landing: "This is exactly what Canada's partner-to-self-operated move needs — and I've done it on this continent, in a bilingual market."
#2WMS 重构,Web → 移动端(FoodsUp)WMS rebuild, web → mobile (FoodsUp)
  • S:Web 版 WMS——终端慢、无扫码、人工录入出错;效率触顶web-based WMS — slow terminals, no barcode scanning, error-prone manual entry; efficiency plateaued
  • T:重构核心流程 + 迁移到带条码扫描的原生移动端,不停摆rebuild core workflows + migrate to native mobile with scanning, without disrupting operations
  • A:写需求前先和运营经理走一遍每条流程(流程优先,不是技术优先)· 按拣货效率影响排序、分站点分阶段推广 · 一线员工 UAT · 不把有问题的流程原样数字化walked every flow with ops managers before writing requirements (process-first, not tech-first) · prioritized by picking impact, phased by site · UAT with floor staff · refused to digitize a broken process as-is
  • R:多站点效率 +35%;扫码降错;移动平台成为后续 AI/自动化基座multi-site efficiency +35%; scanning cut entry errors; the mobile platform became the base for later AI/automation work
落点:证明既能主导软件,也能主导它服务的现场流程——JDL 的 WMS/WES/WCS 栈正需要这种两栖。 Landing: proof of running both the software and the floor process it serves — what JDL's WMS/WES/WCS stack demands.
#3🏆 顺丰智能柜——全栈生态设计🏆 S.F. smart lockers — the full-stack ecosystem
本岗位最强的单个故事——一次覆盖 WMS/TMS/OMS + 硬件 + API。被问「讲一个你设计过的复杂端到端系统」时用这个;想深挖某一层就切 #6(OMS)或 #7(API)。 The strongest single story for this seat — covers WMS/TMS/OMS + hardware + APIs in one. Use it for "walk me through a complex end-to-end system you designed"; zoom into #6 (OMS) or #7 (API) on follow-ups.
  • S:香港末端在崩塌——高层密集市场,上门配送失败是第一成本;没有基础设施把承运商、商户、消费者连起来Hong Kong's last mile was breaking — in a high-rise market, failed door-to-door delivery was the top cost driver; no unified infrastructure connected carriers, merchants, consumers
  • T:从零设计并落地完整的最后一公里生态——软件 + 硬件 + 供应商集成的运营体系,不是一个柜机产品design and launch a complete last-mile ecosystem from zero — software + hardware + partner integrations, not a locker product
  • A(按层讲):OMS(商户自助建单/取件码/追踪/对账)· TMS(自营+3PL 混合车队调度,成本模型平衡单均成本与服务水平)· 柜机系统(柜格分配、Tableau 容量预测布点)· 微型仓 WMS(枢纽分拣→区域微仓→柜机,替代 hub-to-door)· 硬件(IoT 控制器、电子锁、云端 CCTV、YSL AI 人脸识别柜)· 开放 API(顺丰/UPS 承运商 + 800+ 便利店折入同一骨架) (tell it by layer): OMS (merchant self-serve orders / pickup codes / tracking / reconciliation) · TMS (hybrid own+3PL fleet dispatch; cost model balancing per-parcel cost vs service) · Locker system (cell allocation, Tableau capacity forecasting by density) · micro-warehouse WMS (hub sort → regional micro-warehouse → locker, replacing hub-to-door) · hardware (IoT controllers, e-locks, cloud CCTV, YSL AI face-recognition locker) · open APIs (S.F./UPS carriers + 800+ convenience stores on one backbone)
  • R:0 → 1,000+ 柜机,含便利店 2,000+ 点位;年 1,000 万+ 件;香港最大末端网络;团队 3 → 50 人0 → 1,000+ lockers, 2,000+ points incl. stores; 10M+ parcels/yr; HK's largest last-mile network; team 3 → 50
落点:「我设计过一个把 OMS、TMS、柜机、微型仓 WMS、硬件 IoT 与承运商 API 拧成一体的末端生态——这正是京慧『设计→规划→执行』想做的事,只是我在实体网络上做了一遍。」 Landing: "I've built an ecosystem tying OMS, TMS, lockers, micro-warehouse WMS, IoT hardware and carrier APIs into one — exactly what JingHui's design→plan→execute aims at, except I did it on a physical network."

备用纯 TMS 例子(不同公司):IRS Logistics 端到端 TMS——需求→设计→UAT→平行运行→切换;人工 −40%、效率 +25%、物流支出 −10%,并促成空运业务线(营收 +10%)。 Backup pure-TMS example: the IRS Logistics end-to-end TMS — requirements → design → UAT → parallel run → cutover; manual −40%, efficiency +25%, logistics spend −10%, plus a new air-freight line (+10% revenue).

#4KPI 监控 + WarehouseIQ(FoodsUp)KPI monitoring + WarehouseIQ (FoodsUp)
  • S:KPI 在 Tableau/Metabase 里,但发现异常靠人工——经理每班头一小时都在看看板;异常层层放大才有人处理KPIs lived in Tableau/Metabase but anomaly detection was manual — managers spent the first hour of every shift reading dashboards; issues amplified before anyone acted
  • T:弥合「出问题了」与「该怎么办」之间的空档close the gap between "something's wrong" and "here's what to do"
  • A:KPI 监控系统带实时异常标记 + 预设纠正行动(不只是告警)· WarehouseIQ:5 个 AI 智能体按 KPI 领域诊断根因、推荐行动,可对话提问 · 抬升为 Hive:每个 PRD、每个领域的 KPI 在方案设计时就定义口径,上线后自动被监控 · 人在回路,只推荐不执行KPI monitoring with real-time exception flags + pre-defined corrective actions (not just alerts) · WarehouseIQ: 5 AI agents by KPI domain diagnosing root causes and recommending actions, conversational · elevated into Hive: every PRD's and every domain's KPIs defined at design time, auto-monitored after go-live · human-in-the-loop, recommend-only
  • R:异常实时标记 + 行动建议;人工看看板时间 −40%;试点主管约 70% 采纳建议exceptions flagged in real time with recommended actions; manual dashboard review −40%; pilot supervisors adopted ~70% of recommendations
⛔ 不要说「从数小时到数分钟」——已确认不实。只用「人工复核时间减少约 40%」。 ⛔ Never "from hours to minutes" — confirmed untrue. Only "cut manual review by ~40%."
落点(方案岗翻译):「每个客户方案在设计时就带着 KPI 口径,上线后自动被监控——这就是京慧控制塔和 QBR 的底层能力。」也是你最新鲜的 AI 故事——JDL 正在营销 AI 仓储。 Landing (translated for the solutions seat): "Every customer solution ships with its KPI definitions built in at design time and monitored automatically after go-live — the substrate of JingHui's control tower and QBRs." Also your freshest AI story — JDL actively markets AI warehousing.
#5拣货路径重设(FoodsUp)—— 60 秒版Pick-path redesign (FoodsUp) — the 60-second story
  • S:拣货是人力瓶颈——老旧库位规则、低效路径;UPH 停滞、人力成本上升picking was the labour bottleneck — outdated slotting rules, inefficient routes; UPH flat, labour costs rising
  • T:不加人手提升拣货效率raise picking efficiency without adding headcount
  • A:跟随拣货员观察 + 数据分析 → 认定行走时间是最大浪费 → 重设路径、调库位、标准化为 SOP、培训主管落地shadowed pickers + analyzed pick data → identified walking time as the biggest waste → redesigned routes, re-slotted, standardized as SOPs, trained supervisors to sustain it
  • R:UPH +30% · 人力成本 −20%——能持续,因为改动由运营方拥有,不是强加的UPH +30% · labour cost −20% — and it stuck, because operations owned the change
用法:被问「举一个你改进流程的例子」时的快答;把 #2/#4 留给深挖。 Use: the quick answer to "give me one process improvement"; save #2/#4 for the deep dive.
#6中小商户 OMS + 便利店集成(顺丰)—— #3 的 OMS 层SMB OMS + convenience-store network (S.F.) — #3's OMS layer
  • S:柜网在扩张,但中小商户没有系统推送/追踪/对账订单;小卖家负担不起 EDI 或 IT 项目the locker network was scaling but SMB merchants had no system to push/track/reconcile orders; small sellers couldn't afford EDI or an IT project
  • T:搭订单管理层,让单人小店也能自助入驻跑履约;不再砸柜机资本也能扩物理覆盖build the order-management layer so even a one-person shop could self-onboard; extend coverage without more locker capex
  • A:自助建单、取件码自动发放、实时追踪、配送对账——日发数百单的商户零 EDI、无 IT 投入接入 · 端到端设计商户入驻 SOP · 800+ 便利店折入同一套 OMS/预约骨架,覆盖扩到 2,000+ 点位 · 为 2 个新市场本地化(营收 +40%)self-serve orders, automatic pickup codes, real-time tracking, reconciliation — merchants shipping hundreds of orders a day onboarded with zero EDI, no IT investment · designed the merchant onboarding SOP end to end · folded 800+ convenience stores into the same OMS/booking backbone, extending coverage to 2,000+ points · localized for 2 new markets (+40% revenue)
  • R:商户自助入驻;2,000+ 取件点;年 1,000 万+ 件SMB self-onboarding; 2,000+ pickup points; 10M+ parcels/yr
落点:「我搭过 OMS,不只是用过」——而加拿大要快速入驻的,正是这批跨境卖家长尾。 Landing: "I've built an OMS, not just used one" — and the long tail it onboarded is exactly the cross-border seller base Canada needs to onboard fast.
#7开放 API 承运商集成(顺丰/UPS)—— #3 的集成层Open API carrier integrations (S.F./UPS) — #3's integration layer
  • S:每家承运商各跑各的系统;没有实时数据交换,每次接入都是人工、脆弱的连接every carrier ran its own systems; no real-time data exchange — every new carrier was a manual, fragile hookup
  • T:开放 API 平台——承运商集成一次即得实时追踪、柜机预约、状态同步;每次接入按正规集成项目来跑build an open API platform — integrate once for real-time tracking, locker booking, status sync; run each onboarding as a formal integration project
  • A:设计 API 契约(订单追踪 / 柜机预约 / 状态 webhook / 错误处理)· 每家承运商走完整流程:集成规范与字段映射 → 沙箱 → UAT → 平行运行 → 切换上线 → SLA 监控 · 版本控制 + 合作方支持designed the API contract (tracking / locker booking / status webhooks / error handling) · ran each carrier through the full motion: integration spec & field mapping → sandbox → UAT → parallel run → cutover → SLA monitoring · versioning + partner support
  • R:被顺丰、UPS 等采用;多承运商同平台实时追踪与预约——1,000 万件/年网络背后的集成骨架adopted by S.F. Express, UPS and others — the integration backbone behind a 10M-parcels-a-year network
落点:这正是 JD 里那套动作——集成规范 → API/EDI → 测试 → UAT → 上线 → SLA。「我站在平台侧,把承运商集成从 UAT 一路推到切换上线。」 Landing: this is the JD's exact motion — integration spec → API/EDI → testing → UAT → go-live → SLA. "I sat on the platform side and drove carrier integrations from UAT through cutover."
#8排班数字化 5,000+ 人(KMB)—— 团队短板补位Scheduling digitisation, 5,000+ staff (KMB) — covers the team gap
  • S:5,000+ 名车长人工排班——人力浪费、合规风险(12 小时上限、强制休息)、疲劳投诉5,000+ bus captains on manual rosters — wasted labour, compliance risk (12-hour caps, mandatory rest), fatigue complaints
  • T:全车队排班数字化、标准化digitize and standardize rostering fleet-wide
  • A:法规约束建模进系统、ML 辅助生成班表 · 与各车厂主管一起推广:培训、反馈闭环、分阶段采纳 · 并行:2,000 辆车零部件生命周期系统(部件故障 −18%)modelled regulatory constraints into the system, ML-assisted roster generation · rolled out with depot supervisors: training, feedback loops, phased adoption · in parallel: parts-lifecycle system across 2,000 buses (part failures −18%)
  • R:排班相关运营开支 −30%;5,000+ 人规模上均衡合规scheduling-related opex −30%; balanced, compliant shifts at 5,000+ scale
坦诚表述(被问带团队经验时,务必用)

"我的带人经验是通过系统和主管来实现的——我在 5,000 人规模上搭建了一线团队赖以运转的标准、培训体系和绩效追踪。我尚未直接带过有直属汇报线的团队——而这恰恰是本岗位的那一步进阶,也正是我想要它的原因。"

The honest line (English — use verbatim when asked about team management)

"My people-leadership has been through systems and supervisors — I built the standards, the training programs, and the performance tracking that front-line teams ran on, at a five-thousand-person scale. What I haven't yet done is manage a team with direct reports — and that's precisely the step up this role offers, which is part of why I want it."

面试官会奖励这种有自知之明的回答;反正短板他们也看得出。 Interviewers reward the self-aware version; they'd spot the gap anyway.

📎 作品集:portfolio.ryanchan.info —— 引导面试官看 WarehouseIQWMS Task Management 这两个。 📎 Portfolio: portfolio.ryanchan.info — steer them to WarehouseIQ and WMS Task Management.

§7HRBP 预测题Predicted HRBP Questions

HRBP 大概率重放 Crystal 的剧本(动机 / 现职 / 离职 / 薪资 / 到岗)——答案与第一轮逐字一致(§2)。新增两个点: The HRBP will likely re-run Crystal's script (motivation / current role / why leave / comp / start date) — answer word-for-word consistent with Round 1 (§2). Two additions:

💰薪资复查 —— 第一轮问了两次 = 他们最在意Salary re-check — asked twice in Round 1 = what they care about most
照这个讲

"这个我和 Crystal 已经对齐过:我的区间是 $100K 到 $110K。比起把每一块钱谈到极致,我更在意总包结构和这个岗位的成长路径——如果基本薪资在区间下沿,奖金和中长期空间怎么设计,我很开放。"

English version

"Crystal and I have already aligned on this: my range is $100K to $110K. And rather than fighting for every dollar of base, I care more about the total package and the growth path of this seat — if base lands at the bottom of the range, I'm open on how bonus and longer-term upside are structured."

  • 不重提「$75K 不用说了」——话已带到,重复显得对抗 Don't repeat "let's not discuss $75K" — the point landed; restating it reads adversarial
  • 🎴 Fontana $85–110K USD 这轮仍不打;留到 offer 谈判,用法是「内部同岗公平」 🎴 The Fontana $85–110K USD card stays down this round; hold it for offer negotiation, framed as internal equity
  • 若 HRBP 给出低于 $100K 的硬顶 → 不拒绝、不接受:「我对机会本身很有兴趣,建议先把互相的评估走完,薪资放到 offer 阶段一起看总包。」 If the HRBP states a hard cap below $100K → neither refuse nor accept: "I'm genuinely interested in the opportunity itself — let's finish evaluating each other and look at total comp together at offer stage."
Q稳定性拷问:「你会不会干一年就走?」The stability probe: "Will you leave after a year?"
照这个讲

"看我的履历——顺丰 5 年、FoodsUp 3 年多,我一份工作都做几年。而且这个岗位的价值恰恰在时间里:playbook 是我写的、首批客户是我上的、自营论证是我算的——这些资产在第三年比第一年值钱得多,我没有理由种了树不摘果子。"

English version

"Look at my record — five years at S.F., three-plus at FoodsUp; I stay for years everywhere I go. And this seat compounds: I'd be writing the playbook, launching the first customers, building the self-operation case — those assets are worth far more in year three than in year one. I have no reason to plant the tree and skip the harvest."

§8我要问的(视频轮版)What You Ask (Round 2 Edition)

第一轮反问只有 2 个且都是行政题——这轮要用业务型问题展示战略视角。业务问 GM,组织问 HRBP。时间不够砍后面。 Round 1 managed only two questions, both administrative. This round, business questions show the strategic lens. Business → GM; organisational → HRBP. Cut from the bottom.

GM业务型 · 按优先级Business questions · in priority order
  1. 「协同仓转自营的触发条件是什么——量、成本模型,还是客户要求?目前有时间表吗?」 ← 最高信号:直击他自己的核心命题 "What triggers the move from partner to self-operated — volume, the cost model, or customer requirements? Is there a timeline?" ← highest signal: it's his own core problem
  2. 「首批目标客户是跨境卖家生态,还是也要拿本地品牌?管道里最像『第一个标杆客户』的是什么画像?」 "Are the first target customers the cross-border seller ecosystem, or local brands too? What does the most likely 'anchor customer' in the pipeline look like?"
  3. 「多伦多和温哥华怎么分工——各服务本地,还是东西岸配?」 "How do Toronto and Vancouver divide the work — each serving its own region, or an east/west split?"
  4. 「保税仓(CBSA CBW)在规划里吗?这决定加拿大是本地履约站还是北美转运节点。」 "Is a bonded warehouse (CBSA CBW) in the plan? That decides whether Canada is a local fulfillment station or a North American transshipment node."
  5. 岗位边界(确认式,8/1 运营专员 JD 已证实分工):「我读了你们运营专员的 JD——他是协同仓日常的单一联系人,管对账和异常闭环;我理解我做方案、定价、集成和 SOP 设计,他执行、异常数据回流给我迭代——这个分工我理解得对吗?」 ← 做完功课的确认式问题,用人经理最爱 Role boundaries (confirmation-style — the Aug 1 Ops Specialist JD proves the split): "I read your Operations Specialist posting — they're the single point of contact for the co-managed warehouses, owning reconciliation and exception closure. My read: I design the solutions, pricing, integrations and SOPs; they execute, and their exception data flows back to me for iteration — is that the right split?" ← the homework-done question hiring managers love
  6. 收尾:「前 90 天您希望这个岗位交出什么,您才会认为这次招聘是对的?」 Closer: "What would this role need to deliver in the first 90 days for you to call the hire a success?"
HR组织型 · Crystal 明确 defer 给他们的,必问Organisational · explicitly deferred by Crystal — must ask
  1. 「雇佣主体是美国实体还是加拿大实体?CAD 发薪吗?医保 / RRSP 这些福利怎么走——本地方案还是 EOR?」 ⛔ 这题里不提薪资数字 "Is the employing entity US or Canadian? Paid in CAD? How do benefits run — medical, RRSP — a local plan or an EOR?" ⛔ no salary figures inside this question
  2. 「汇报线:直线向加拿大 GM,还是同时向美国方案线有虚线?」 "Reporting: solid line to the Canada GM, or a dotted line to the US solutions organisation as well?"
  3. 「奖金机制:目标百分比、第一年是否按比例折算?」(若薪资题已谈到总包可跳过) "Bonus mechanics: target percentage, and is year one pro-rated?" (skip if total comp already came up)
⛔ 不要问:2022 年那轮为什么停(=「我知道你们失败过」)· 人事变动 / 外卖亏损 / 价格战 · 996(想探文化就问「国际团队和中国本部的运营节奏有什么不同」) ⛔ Don't ask: why the 2022 launch stalled (= "I know you failed") · executive churn / delivery losses / price wars · 996 (probe culture via "how does the international team's operating rhythm differ from the China business?")

§9🆕 8/1 新情报 —— 可用,但不点名🆕 Aug 1 Intel — Usable, But No Names

7/19 的「多伦多搜不到 JDL 员工」已过时:8/1 复查发现 3 名 GTA 在职者 The Jul 19 finding of "no JDL employees in Toronto" is stale: an Aug 1 re-check surfaced three current GTA staff.

  • HRBP 已锁定(高置信推断) —— 北美可见的 JDL HRBP 只有一人:Tina Wang,雇佣主体(JDL US)的 Senior HRBP,Fontana。她出场本身就佐证「加拿大挂美国组织」;绿地建站 staffing 是她五年的日常——蒙特利尔 SOP/培训故事对她无需翻译 HRBP identified (high-confidence inference) — only one JDL HRBP is visible in North America: Tina Wang, Senior HRBP of the employing entity (JDL US), Fontana. Her presence itself corroborates "Canada hangs under the US org"; greenfield staffing has been her day job for five years — your Montréal SOP/training story needs no translation for her
  • Logistics Specialist · 多伦多 —— 约 11 个月前还在 Such A Good Supply Chain Inc.(货代)→ 现已入职 JDL。[推断,弱] 该公司无 LinkedIn 无网页,协同仓关联无法核实 Logistics Specialist · Toronto — was at Such A Good Supply Chain Inc. (freight forwarding) ~11 months ago → now at JDL. [weak inference] the company has no LinkedIn or web footprint; the partner-warehouse link is unverifiable
  • Warehouse Specialist · Mississauga —— [推断] 多伦多侧协同仓大概率在 Mississauga Warehouse Specialist · Mississauga[inferred] the Toronto-side partner warehouse is most likely in Mississauga
  • PMO · 加拿大 —— PMO 职能已在岗;组织不只 GM + HRBP PMO · Canada — a PMO function already in seat; the org is more than GM + HRBP
  • 运营专员公开 JD(Crystal ~07-25 发布,$50K + Annual Bonus) —— 官方逐字确认协同仓:"primary liaison with third-party / co-managed warehouses";岗位边界与你的 30-60-90 附一推断逐条吻合;薪酬梯子:Ops $50K → Solutions/Sales $75K → Warehouse Mgr $80–110K;她名下 4 个 req 同时在招 Ops Specialist public JD (posted by Crystal ~Jul 25, $50K + annual bonus) — officially confirms the model verbatim: "primary liaison with third-party / co-managed warehouses"; role boundaries match your 30-60-90 appendix point by point; the salary ladder: Ops $50K → Solutions/Sales $75K → Warehouse Mgr $80–110K; she's running 4 reqs at once
  • 🚨 双管线警示 —— 2022 年那轮的加拿大国家经理 Vito Zhong,现在是 SHEIN 加拿大 GM = 你 SHEIN 流程的决策人。⛔ 绝不为 JDL 情报接触他;⛔「2022 为什么停」禁区再升一级;⛔ SHEIN 面试里提「另一家在流程中」绝不具体到 JDL 🚨 Cross-pipeline alert — the 2022 run's Canada Country Manager, Vito Zhong, is now SHEIN's Canada GM = the decision-maker in your SHEIN process. ⛔ Never contact him for JDL intel; ⛔ the "why did 2022 stall" no-go is now doubly radioactive; ⛔ in SHEIN interviews, never let "another company in process" become identifiably JDL
✅ 可以说:「我注意到你们在大多区已经有本地团队在运营,这和 Crystal 讲的协同仓模式对得上。」——展示功课,不点名。 ✅ Safe to say: "I noticed you already have a local team operating in the GTA — which matches the partner-warehouse model Crystal described." Homework shown, no names.
⛔ 不点人名 · 不说「我查了你们员工的 LinkedIn」 · 不提 Such A Good(猜错很尴尬,而且显得在打探)。GM 本人仍不可见 → 姓名只能向 Crystal 要(§1)。 ⛔ No names · never "I looked up your employees on LinkedIn" · don't mention Such A Good (wrong guess is awkward, and it reads as snooping). The GM remains invisible → the name only comes from Crystal (§1).

§10视频面试当天检查表Day-of Checklist

设备Setup
笔记本 + 耳机;摄像头平视高度;背景整洁;灯在脸前不在脸后(晚 7 点天可能还亮,注意逆光) Laptop + headphones; camera at eye level; tidy background; light in front of your face, not behind (it may still be bright at 7 PM — watch the backlight)
网络Network
有线或路由器旁;手机热点备用;掉线预案:立即 WhatsApp 消息给 Crystal Wired or next to the router; phone hotspot as backup; if you drop: WhatsApp Crystal immediately
工具Platform
提前 1 天确认平台(Teams / 腾讯会议 / Zoom),装好、登录、测试 Confirm the platform a day ahead (Teams / Tencent Meeting / Zoom); install, log in, test
桌面Desk
第二屏或 iPad 摊开 §2 口径表 + §8 反问清单;不要照着念——视频里眼神移动看得见 Second screen or iPad open to §2 story lock + §8 questions; don't read from them — eye movement shows on video
着装Dress
有领上衣;GM 是中方背景,偏正式一档不吃亏 Collared shirt; the GM has a China-org background — erring one notch formal costs nothing
开场Opening
「您好,我是 Ryan,谢谢两位安排时间。」等对方引导,不抢着自我介绍 "Hello, I'm Ryan — thank you both for the time." Let them steer; don't launch into your intro
语言Language
跟随对方开场语言;中途找机会自然切换一次(§3 策略) Follow their opening language; switch once, naturally, mid-call (§3 strategy)
收尾Closing
反问 → 「前 90 天期望」→ 主动提 30-60-90 计划可发送 → 问下一步流程与时间线 Your questions → the "first 90 days" closer → offer to send the 30-60-90 plan → ask about next steps and timeline
面试后 30 分钟Within 30 min after
WhatsApp 中文致谢 Crystal + 复述下一步;若 GM / HRBP 留了联系方式则分别致谢;回填 recruiter-notes.md;更新 tracker Thank Crystal on WhatsApp in Chinese + restate next steps; thank the GM / HRBP separately if they shared contact details; backfill recruiter-notes.md; update the tracker
+35%FoodsUp 多站点效率
(WMS 重构 + 移动化)
FoodsUp multi-site efficiency
(WMS rebuild + mobile)
1,000 万10M+顺丰柜网年处理量
2,000+ 点位 · 团队 3→50
S.F. locker parcels/yr
2,000+ points · team 3→50
2 个月2 months蒙特利尔仓
从零上线
Montréal warehouse
zero to live
从零建过 · 系统落过 · 中英双语Built from zero · Shipped the systems · Bilingual