Cover letter + mock interview loop (with evidence checks)
Goal: Ship a short evidence-based letter, then rehearse answers the model is not allowed to embellish.
Best for: Applicants who freeze on “Tell me about yourself” or paste AI letters that sound like everyone else.
Letters and mocks from your bullets only—never invented stories.
Why beginners skip this
Pretty letters without proof fail in the room. Map JD lines to evidence you can say aloud and rehearse follow-ups. Mid-week cost shows up as rework, not as a missing bookmark.
Step 1 — Letter from evidence only
A cover letter is not a biography. Three short paragraphs: why them (facts you researched), why you (resume proof), clear ask. Ban passion fluff.
Goal: Draft a 3-paragraph cover letter from evidence only.
Role: [title] at [company]
Why them (my research): [2 facts]
Why me (resume only): [3 proof points]
Format: ≤250 words; subject line if email; no “I am passionate…”
Boundaries: Do not invent awards, metrics, referrals, or shared history.
After drafting: list every claim → Evidence location | OK to send?
Example
Filled prompt
Role: Junior data analyst at a regional grocery chain
Why them: They published a 2026 case study on reducing food waste with weekly store dashboards; their careers page lists SQL + stakeholder updates.
Why me: Built weekly Looker views for campus café inventory; sent Friday notes to ops lead; documented two A/B price tests in sheets.
Boundaries: No invented “cut waste 18%” unless that number is in my files.
What good output looks like
- Why-them facts are checkable
- Why-me maps to resume bullets
- Claim list ends with OK/needs metric—not silent inventions
- Pass/fail dated (Asia/Shanghai) sits next to the artifact
Step 2 — STAR story without hero mode
STAR = Situation, Task, Action, Result. The model helps structure; you supply numbers. If Result is missing, keep [METRIC] and dig in your files later.
Turn these notes into STAR. Label each part.
Notes: ---
[paste]
---
Result may only use numbers I wrote or [METRIC].
Then ask me one follow-up that an interviewer might ask to pressure-test the Result.
Step 3 — Mock interview loop
Do this step with a real artifact open—not from memory.
You are a careful interviewer for [role].
Rules: Ask ONE question at a time. Wait for my answer.
After each answer, score Clarity / Evidence / Length (1–5).
Point out any claim that was not in my resume packet.
Suggest one tighter opening sentence—without inventing new achievements.
Start with: “Tell me about a time you influenced a decision without authority.”
Example
Filled prompt
STAR aloud: pushed back on unrealistic launch date.
≤2 min. Ban resume-missing metrics. Record yourself once.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.
What good output looks like
- One question at a time
- Evidence score reacts to unverifiable claims
- Opening-line suggestion stays faithful
Save this card
Card: Map JD lines to proof you own; record the mock before you trust the wording. Keep this beside the tool; read before you start.
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).
1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)
- [ ] Tools/writes paused
- [ ] Refuse-line dated
- [ ] Artifact path saved
- [ ] Next link chosen (or stop)
Before you start
Open the JD and your evidence bullets side by side for “Ship a short evidence-based letter, then.” Cross out any metric you cannot say aloud in 10 seconds. Guide: career-cover-letter-and-mock-interview. If you only have a blank practice box, stop and fetch the real job first.
- Goal in one line: ___
- Allowed tools: ___
- Forbidden: ___
- Human approve needed for: ___
How to use this week
This week for career: map one claim to evidence you can say aloud for “Ship a short evidence-based letter, then rehearse answers th.” Record one answer. Cut one unsourced number Guide: career-cover-letter-and-mock-interview.
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 when it invents
Unverifiable superlatives; mock that only reads the script—map JD to proof you can say aloud.
Pitfalls
| Pitfall | Better |
|---|---|
| Sending the first AI letter unchanged | Run the claim→evidence list; cut slop |
| Practicing only with the model’s “ideal answer” | You speak first; model coaches second |
| Memorizing a script you cannot explain | Keep bullets; speak in your own words |
Example
Filled prompt
Job: Ship a short evidence-based letter, then rehearse
Prior fail: [what missed the check]
Repair: keep the same Done; add one constraint + one concrete example from my notes.
Boundaries: draft only; label Unknowns [?]; no silent send.
Return: fixed output + the one-minute pass/fail I will mark.
What good output looks like
- Names the prior fail without inventing a new job
- Adds one constraint tied to “Ship a short evidence-based letter, then rehearse ”
- Still draft-only / Unknowns labeled
- Pass/fail: you mark green on the same checklist (career-cover-letter-and-mock-interview #4)
Field note: record one mock answer on your phone, play it back, and strike any claim you cannot source in ten seconds. Keep the refuse line visible while you draft.
Practice now
Live card: one career artifact edit with proof, no invention (Asia/Shanghai).
Today: paste one JD + your evidence bullets. Ask for a cover letter mapping three requirements to three bullets you provided—no new metrics. Then answer one STAR question aloud in under two minutes.
Cover + mock card (copy): 1. Role / company: ___ · three JD requirements I will map: A ___ B ___ C ___ 2. Evidence bullets I pasted (no invented metrics): 1) ___ 2) ___ 3) ___ 3. STAR answer timed: Situation ___ · Task ___ · Action ___ · Result ___ · seconds: ___ 4. Refuse-line if the model invents a metric: ___ (date: Asia/Shanghai)
Pass/fail: every claim in the letter traces to a bullet you pasted; STAR under 120 seconds.
- [ ] Artifact path written
- [ ] Refuse example would say "yes"
- [ ] Dated Asia/Shanghai
One sentence takeaway
Map JD lines to proof you own; record the mock before you trust the wording. This week: one letter paragraph + three follow-ups you can answer aloud.
- You can point to a dated refuse-line
- You have one artifact path from tonight
- You can teach the red flag in one sentence
Next
Resume · Path · Verify · Reject AI slop · Stakeholder update
Pair with today: open the first Next link (career-resume-without-inventing) only after you dated a refuse-line for this guide (Asia/Shanghai).
求职信 + 模拟面试循环(带证据检查)
目标: 写出短而有据的求职信,再排练回答——模型不得替你添油加醋。
适合: 一听「做个自我介绍」就卡壳,或曾贴出千人一面 AI 求职信的人。
求职信与模拟只来自你的要点——绝不编故事。
为什么新手跳过
一封带无来源数字的「漂亮」信,会在面试里塌。先对照 JD 列大纲并冻结事实,再要求「更有冲击力」。
步骤 1——只凭证据写求职信
求职信不是自传。三小段:为何选他们(你自己查到的事实)、为何是你(简历证据)、明确请求。禁止「充满热情」空话。
目标:只凭证据写三段求职信。
职位:[title] @ [company]
为何选他们(我的调研):[2 事实]
为何是我(仅简历):[3 证据]
格式:≤250 词;若是邮件含主题;不要「我充满热情」
边界:不编奖项、数据、内推或共同经历。
起草后:列出每条主张 → 证据位置 | 能否发送?
实例
填好的提示词
JD:运营经理;我的证据:带过 3 名实习生、把周会从 30 分钟降到 12 分钟、没有「10 人团队」经历。
写求职信:把三条 JD 要求映射到我提供的三条证据——不要加任何新指标。
先出草稿,别发送。
像样的输出大概长这样
- 「为何他们」可核对
- 「为何我」能映射回简历
- 主张清单以 OK/缺数据结束——没有偷偷编造
步骤 2——STAR 故事,不要英雄模式
STAR = 情境、任务、行动、结果。模型帮结构;数字你来。结果缺失就留 [METRIC],稍后翻文件补。
把笔记收成 STAR,每部分标注。
笔记:---
[粘贴]
结果只能用我写过的数字或 [METRIC]。
然后问我一个面试官可能用来追问结果的问题。
步骤 3——模拟面试循环
用真实材料做这一步——不要凭记忆。
你是 [岗位] 的严谨面试官。
规则:一次只问一题。等我答完。
每答后按 清晰度 / 证据 / 长度 打 1–5 分。
指出任何不在我简历材料里的主张。
给一句更紧的开场——不得编造新成就。
第一题:「讲一次你在没有职权时推动决定的经历。」
实例
填好的提示词
STAR 题:与供应商就 SLA 发生冲突。
按 情境·任务·行动·结果 组织,口述控制在两分钟内。
简历上没有的数字别用。自己录音听一遍。
像样的输出大概长这样
- 一次一题
- 证据分会对无法核实的说法作出反应
- 开场建议仍忠实于原经历
- 贴合填例场景——不是空泛打气
- 相关则拒绝编造事实或静默发送
保存这张卡
卡面:证据句 + 三个追问。投递/面试前看卡;说不出口的夸赞删掉;缺项就停,不硬开。
1. 我交出了:___ 2. 我拒绝了:___ 3. 我永不再做:___(日期:Asia/Shanghai)
- [ ] 工具/写入已暂停
- [ ] 拒做句已标注日期
- [ ] 成品路径已存
- [ ] 已选下一步(或停)
开始前
打开你真正会用的账号/项目。准备好与「求职信 + 模拟面试循环(带证据检查)」相关的真实材料(不要空白练习框)。
默认姿态:在人确认发送/写入之前只出草稿。授予新工具前,先写一条带日期的拒做句(Asia/Shanghai)。
- 一句话目标:___
- 允许的工具:___
- 禁止:___
- 需要人批准:___
本周怎么用
本周一封求职信 + 一轮模拟:每句夸赞对应证据;模拟里追问「举例」。把过/不过写进笔记并注明日期(Asia/Shanghai)。
红旗
信中无证据的最高级形容词;模拟只念稿不回答追问。编造项目——删。卡上写不清就不继续——先补检查项再跑。
红旗 + 模型编造时的拒绝
- 求职信编造共同人脉或奖项
- STAR 结果多出你没输入的数据
- 教练把你的故事改成更漂亮的虚构
实例
填好的提示词
对照 JD 检查这封信:高亮每一个数字。
删掉我无法在十秒内说出出处的数字。列出你删了改了什么。
像样的输出大概长这样
- 虚构被删
- 面试与简历一致
- 练的是补救不是撒谎
- 贴合填例场景——不是空泛打气
- 相关则拒绝编造事实或静默发送
常见坑
| 坑 | 更好 |
|---|---|
| AI 求职信一字不改就发 | 跑主张→证据清单;删注水 |
| 只背模型的「理想答法」 | 你先说;模型后教练 |
| 死记自己讲不清的稿 | 留要点;用自己的话讲 |
实例
填好的提示词
任务:Ship a short evidence-based letter, then rehearse
上次失败:[哪条检查未过]
修复:保持同一 Done;加一条约束 + 一条你笔记里的具体例子。
边界:仅草稿;未知标 [?];禁止悄悄发送。
返回:修好的输出 + 我将打勾的一分钟过/不过。
像样的输出大概长这样
- 点名上次失败,不另起炉灶
- 约束贴着「求职信 + 模拟面试循环(带证据检查)」
- 仍是草稿 / 未知已标注
- 过/不过:同一张检查表能打绿(career-cover-letter-and-mock-interview #4)
现在就练一次
实卡:一处职业材料带证据修改,不编造(Asia/Shanghai)。
今天写一段求职信并自问三个追问。过/不过与永不做注明日期(Asia/Shanghai)。只收藏标题算失败。
今日卡片(可复制)— career-cover-letter-and-mock-interview: 1. 我要产出的成品:___ 2. 通过/失败标准:___ 3. 若想跳过核验/发送的拒做句:___(日期:Asia/Shanghai) 4. 本篇一条永不做:___
- [ ] 成品路径已写
- [ ] 拒做例句会说「可以」
- [ ] 已标注 Asia/Shanghai 日期
一句话带走
把 JD 每一行映射到你真有的证据再写求职信;先录音模拟面试,再相信 AI 改出来的漂亮措辞。没证据的句子一律删掉。本周做一次可检查练习,否则只是收藏。本周留下可核对的过/不过记录并注明日期(Asia/Shanghai)。
- 能指出一条带日期的拒做句
- 今晚有一条成品路径
- 能用一句话说清红旗
下一步
简历 · 求职路径 · 核验 · 拒绝 AI 套话 · 干系人更新
今日搭配:先为本篇写上拒做句日期(Asia/Shanghai),再打开下一步里的第一篇(career-resume-without-inventing)。
← Back to home · Learn · Tools · Compare · Start