Path: Career (resume · letter · interview)
Goal: Pin the hard rule in career chats: rephrase OK, invent employers/dates/metrics never; gaps stay [NEED EVIDENCE].
Best for: Job seekers who want bilingual-friendly structure without fake metrics.
Honesty first: AI tightens wording; you own every employer, title, and number.
Why beginners skip this
Saving the career-path link feels finished—without a real piece and feedback this week, nothing sticks.
Why this order
Read pack C “do not invent” first, then edit the resume against a real JD; cover letter and mock interview come last because they amplify resume claims.
Outcome
A resume and letter that mirror the job description’s language, plus one practiced STAR story—all grounded in facts you can prove in two spoken sentences.
Suggested order
- Pin Pack C hard rule (never invent) from the prompt packs guide.
- Build an evidence bank offline, then rewrite bullets: career-resume-without-inventing.
- Draft letter + mock interview with evidence checks: career-cover-letter-and-mock-interview.
- Optional polish: writing-reject-ai-slop · claude-email for tone · writing-bilingual-hk-workflow if EN/ZH both ship.
Scene: one real application week
Alex is applying to a junior analyst role. AI suggests “increased retention 18%” because that phrase is common online. Alex’s sheet only shows café inventory dashboards. Alex deletes the 18%, keeps Looker + Friday notes, and practices saying the proof aloud before hitting Apply.
Example
Filled prompt
Hard rule (pin every career chat):
You may rephrase my experience. You must not add employers, titles, dates, tools, awards, or metrics I did not provide. Use [METRIC] or [NEED EVIDENCE] instead.
If you are tempted to invent, say: I cannot invent that—ask for evidence or mark [NEED EVIDENCE].
What good output looks like
- Calendar slot for one live application artifact
- Live artifact opened — not only the bookmark
- Practice timed; refuse-line written
- Pass/fail: artifact dated Asia/Shanghai
Example
Filled prompt
JD line: "Owned roadmap for B2B billing."
My proof bullets (only what I did):
- Led quarterly planning for invoicing v2 with 2 PMs
- Cut dispute handle time from ~3d to ~1d (ticket export, Q2)
Rules: map JD → my bullets; mark [NEED EVIDENCE] if gap; never invent employers/metrics.
What good output looks like
- Each JD phrase maps to a proof bullet or [NEED EVIDENCE]
- No new company names or titles
- Metrics only from what you pasted
- A one-line interview story prompt per mapped bullet
- Gaps listed separately—not papered over
Example
Filled prompt
Ask me 5 follow-ups on this bullet only:
"Cut dispute handle time from ~3d to ~1d."
If I invent numbers, interrupt and mark [UNVERIFIED].
Score answers 1–5 on specificity.
What good output looks like
- Questions dig into method, tradeoffs, and who else was involved
- Interrupts fabricated precision
- Scores with one reason each
- Ends with one weaker answer to rehearse again
- No scripted “perfect” monologue to memorize verbatim
Pick one real role this week—not three. Day 1: paste only facts you own into a working doc and pin the hard rule (no invented employers/metrics). Day 2–3: map three JD lines to proof bullets or [NEED EVIDENCE]. Day 4: one cover-letter paragraph with evidence beside it. Day 5: five mock follow-ups on your weakest bullet; interrupt yourself when you invent precision. End the week with a dated pass/fail note (Asia/Shanghai) listing what still needs evidence.
Save this card
Card: one calendar slot for a live application artifact—not a bookmark binge. Open the artifact before any model rewrite.
Wear-test: show your Save card to a teammate for thirty seconds—if they cannot restate the refuse line, tighten the card tonight and date it (Asia/Shanghai).
Before you start
Create a 25-minute calendar block titled path-career. Open the live artifact for "[NEED EVIDENCE]—do not invent."to invent ”—bookmark alone does not count Keep the live artifact visible the whole time. If you only have a blank box, stop and fetch the real job first
Have: the JD text, your resume export, and a blank evidence sheet. Do not open a second model tab “just to see.” If a metric is fuzzy, write the measurement method or delete the number before any rewrite.
How to use this week
This week ship one real piece + one feedback ask along the path; no checkmark without the piece.
Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).
Red flags + refusal script
Unverifiable resume lines; model-added facts—gaps stay [NEED EVIDENCE].
Pitfalls
| Pitfall | Fix |
|---|---|
| Inventing metrics on the resume | Only numbers you can defend |
| Memorizing a full AI script | Questions + story prompts from your bullets |
| Skipping honesty gate | Refuse fabricated experience |
- Letting the model “improve” a bullet by adding a tool you never used.
- Treating LinkedIn fluff as interview-ready proof.
- Running mock interviews on bullets you have not mapped to JD language first.
- Shipping a letter the same day you invented a metric to fill a gap.
Field note: run one live pass this week that proves—Models may rephrase; they may not add resume facts—gaps stay [NEED EVIDENCE]. Date the pass/fail (Asia/Shanghai); bookmarks do not count.
Practice now
Quant source: each number cites a doc/path (Asia/Shanghai).
Impact verb audit: replace weak verbs with measured ones (Asia/Shanghai).
STAR check: situation/task/action/result present or rewrite (Asia/Shanghai).
Scope split: one achievement per bullet (Asia/Shanghai).
Proof folder: link or path to proof beside each metric (Asia/Shanghai).
Scope line: one bullet = one scope; split stacked achievements (Asia/Shanghai).
Bullet-proof drill: one metric with source note beside it or strike the metric (Asia/Shanghai).
Career-path drill: rewrite one resume bullet with metric + proof link/path; refuse adjectives without numbers (Asia/Shanghai).
Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.
Tonight ship one real resume block or mock-interview note; no checkmark without an artifact.
Close the loop
Write one line: next time I only save the path with no piece, I refuse the checkmark.
One sentence takeaway
Real piece + feedback ask; no checkmark without the piece.
Word-floor practice
Run the Today card once on a real artifact. Write pass/fail + never-do with date Asia/Shanghai. If you only skimmed, do not mark this guide done.
Next
路径:求职(简历 · 求职信 · 面试)
目标: 求职对话置顶硬规则:可以改表述,不可以添履历;缺口用 [NEED EVIDENCE]。
适合: 正在改简历或求职信、模型爱「写漂亮点」顺手加业绩的人。
面试稿要和简历对得上号。模型一开始编,就贴拒绝话术重做。
为什么新手跳过
收藏职业路径标题像进步;本周没有真作品与反馈,什么都没留下。
为什么是这个顺序
先读包 C「不编造」规则,再对着真实 JD 改简历;求职信与模拟面试放最后,因为它们会放大简历内容。
达成效果
一份贴合职位描述用语的简历与求职信,外加一个练过的 STAR 故事:每条都能用两句口语证明。
建议顺序
- 从提示词包钉住包 C 硬规则(绝不编造)。
- 先离线建证据库,再改要点:不编造的简历。
- 写求职信 + 带证据检查的模拟面试:求职信与模拟面试。
- 可选打磨:拒绝 AI 注水 · Claude 邮件语气 · 如果中英都要发则看港双语工作流。
场景:一个真实投递周
Alex 在投初级分析岗。AI 建议写「留存提升 18%」,因为网上常见这种说法。Alex 的表格里只有咖啡馆库存看板。Alex 删掉 18%,保留 Looker + 周五笔记,并在点「投递」前大声练习怎么证明。
实例
填好的提示词
硬规则(每次求职对话都置顶):
你可以改写我的表述。不得添加我没提供过的雇主、职位、日期、工具、奖项或数据。没有就写 [METRIC] 或 [NEED EVIDENCE]。
如果你想编,请改口说:「我没有这方面的证据:请问我。」
像样的输出大概长这样
- 模型会追问缺的数据,而不是直接写「+37%」这类数字
- 缺口用 [METRIC] 或 [NEED EVIDENCE] 标出,不偷偷补洞
- 面试回答能和简历对得上号
- 硬规则每次置顶,像合同条款一样清楚
- 读起来像求职者自己在把关,不是简历代工厂
保存这张卡
记下:路径上今晚停过的 1–2 处 + 练过的真实任务。标上日期。
开始前
先选好今晚真实任务,再打开路径上的指南。
本周怎么用
本周按路径交一件真作品 + 一次反馈请求;没有作品不打勾。
红旗清单 + 拒绝话术
收藏职业路径却没有真作品与反馈,什么都没留下;先交作品。
| AI 输出里的红旗 | 你怎么做 |
|---|---|
| 出现你没输入过的雇主、职位或日期 | 删除;粘贴下方拒绝话术 |
| 精确百分比但你文件里没有来源 | 改成 [METRIC] 或删掉 |
| 明天演示不了的工具名 | 降级为你能展示的工具 |
| 空洞口号(「协同」「推动变革」) | 改成你工作时会说的白话动词 |
| 求职信「热情」却配假调研 | 换成你真正点开过的 2 个事实 |
实例
填好的提示词
模型一开始编造时的拒绝话术:
停下。那个数据/雇主/工具不在我的材料里。
只许用我提供过的内容重写。
缺口请标 [NEED EVIDENCE]。不要自己把洞填上。
像样的输出大概长这样
- 下一稿不再出现新雇主、新工具或新数据
- [NEED EVIDENCE] 缺口仍然可见,方便你回去补材料
- 你拿着稿子进面试时站得住脚
- 拒绝话术短、硬、可复制进任何求职对话
- 不把「润色」偷换成「编造履历」
- 未知标出;不编造负责人、日期或指标
常见坑
| 坑 | 改法 |
|---|---|
| 让模型「写漂亮点」顺便加业绩 | 置顶不新增雇主/数据 |
| 缺口被自动填上 | 强制 [NEED EVIDENCE] |
| 面试稿与简历对不上 | 每轮改完做事实对照 |
现在就练一次
今晚就练:交一件真作品 + 一次反馈请求;没有作品不打勾。
闭环
写下一行:下次只收藏路径不交作品,我拒绝打勾。
一句话带走
真作品 + 反馈请求;没有作品不打勾。
下一步
← Back to home · Learn · Tools · Compare · Start