Back to Details

cold-email-writer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Cold Email Writer

陌生开发邮件撰写工具

When to Use This Skill

适用场景

Use this skill when the user wants to:
  • Write a cold outreach email to a hiring manager, founder, or recruiter
  • Reach out about a job opening they weren't referred to
  • Introduce themselves to a company they want to work at
  • Mentions: "cold email", "reach out", "intro email", "outreach", "contact hiring manager"
当用户有以下需求时，可使用该技能：
  • 为招聘经理、创始人或招聘专员撰写陌生开发邮件
  • 申请未通过推荐的职位
  • 向心仪公司自我介绍
  • 提及关键词："cold email"、"reach out"、"intro email"、"outreach"、"联系招聘经理"

Core Principle

核心原则

Cold emails fail because they sound like cover letters. The goal is to sound like a smart person who genuinely noticed something specific about the company — not a candidate broadcasting their credentials.
The email should feel like: A colleague mentioning something interesting they read, not a sales pitch.
陌生开发邮件之所以失败，是因为它们听起来像求职信。我们的目标是让邮件听起来出自一位真正留意到公司细节的聪明人，而非一个一味炫耀自身资质的求职者。
邮件应给人的感觉： 如同同事分享读到的有趣内容，而非推销话术。

The Template Structure

模板结构

Subject

主题

Quick intro — [First Name Last Name]
Simple. No clickbait. No role title. Just a name.
Quick intro — [First Name Last Name]
简洁明了，无标题党，不提及职位名称，仅标注姓名。

Opening — The Hook (2-3 sentences)

开头——钩子（2-3句话）

Start with what genuinely pulled the candidate in. Must be specific to this company — not a generic compliment.
I just came across [Company] and ended up spending more time on it than I expected.
[One specific thing that caught their attention — a stat, a product decision, a market insight from the JD or website]
What makes a good hook:
  • A specific number or stat from the company's materials ("only 5% of the market is online")
  • A product decision that shows you understand the domain ("you're building from scratch alongside underwriters, not just distribution")
  • A technical insight from the JD ("improving the data infrastructure for LLM usage, not just the model layer")
What makes a bad hook:
  • Generic: "I love what you're building"
  • Vague: "Your mission resonates with me"
  • Flattering: "You're one of the most exciting companies in the space"
从真正吸引求职者的点切入，必须是针对该公司的具体内容，而非泛泛的赞美。
I just came across [Company] and ended up spending more time on it than I expected.
[One specific thing that caught their attention — a stat, a product decision, a market insight from the JD or website]
优质钩子的特点：
  • 来自公司资料的具体数字或数据（如“仅5%的市场已线上化”）
  • 体现你对行业领域理解的产品决策（如“你们正在与承保人从零开始搭建，而非仅做分销”）
  • 来自招聘启事的技术洞察（如“为LLM使用优化数据基础设施，而非仅关注模型层”）
劣质钩子的特点：
  • 泛泛而谈：“我喜欢你们正在打造的产品”
  • 模糊空洞：“你们的使命与我产生共鸣”
  • 过度恭维：“你们是该领域最具吸引力的公司之一”

Location Disclosure (if international)

所在地说明（若为跨国求职）

If the candidate is in a different country from the company, disclose it early and casually:
Before you read further, I should mention I'm based in [country]. But if we both
feel there's a strong fit, I'd be open to figuring things out.
若求职者与公司位于不同国家，需尽早且自然地说明：
Before you read further, I should mention I'm based in [country]. But if we both
feel there's a strong fit, I'd be open to figuring things out.

Experience Gap (if applicable)

经验差距说明（若适用）

If the role lists more years than the candidate has, acknowledge it briefly and redirect:
The role mentions [X] years of experience — I'm at [Y], but the work I've
shipped is production-facing and I'd rather you judge that directly.
若职位要求的工作年限高于求职者当前年限，需简要提及并转移重点：
The role mentions [X] years of experience — I'm at [Y], but the work I've
shipped is production-facing and I'd rather you judge that directly.

The Body — Who They Are (3-5 sentences)

正文——个人背景（3-5句话）

Current role → relevant past → one or two projects. Keep it contextual, not a list.
A bit about me: I currently work at [Company], [one line on what the company does],
where I [what they actually do there — not a job title]. Before that I worked
with teams in [region], mostly around [relevant domain].

On the side I've been building [Project] ([link if applicable]) — [one line: what
it is and one proof point like "got to paying clients" or "20K downloads"].
Rules:
  • Mention work as context, not as proof of greatness
  • No achievement listings ("I increased X by Y%") — let the project speak
  • If current company is remote with a European/international team, say so explicitly
  • Keep project mentions to one or two max — the most relevant ones only
当前职位→相关过往经历→1-2个项目。需结合语境表述，而非罗列清单。
A bit about me: I currently work at [Company], [one line on what the company does],
where I [what they actually do there — not a job title]. Before that I worked
with teams in [region], mostly around [relevant domain].

On the side I've been building [Project] ([link if applicable]) — [one line: what
it is and one proof point like "got to paying clients" or "20K downloads"].
规则：
  • 将工作经历作为背景提及，而非用来证明自身优秀
  • 不罗列成就（如“我将X提升了Y%”）——让项目本身说话
  • 若当前公司是拥有欧洲/国际团队的远程公司，需明确说明
  • 仅提及1-2个最相关的项目

The Connection (1-2 sentences)

关联点（1-2句话）

Bridge between their background and the specific role. Should feel like an observation, not a claim.
I think you're looking for [what the role actually wants] — that's the kind of
work I've been doing, and honestly I feel like I'd be a strong fit.
Or more specific:
My stack maps naturally to yours — [specific tech overlap]. But more than the
stack, it's the [domain/problem] that I'm genuinely interested in.
搭建个人背景与目标职位之间的桥梁，应是观察所得，而非自我宣称。
I think you're looking for [what the role actually wants] — that's the kind of
work I've been doing, and honestly I feel like I'd be a strong fit.
或更具体的表述：
My stack maps naturally to yours — [specific tech overlap]. But more than the
stack, it's the [domain/problem] that I'm genuinely interested in.

Portfolio Link

作品集链接

More about me: [portfolio URL]
One line. No elaboration.
More about me: [portfolio URL]
仅一行文字，无需额外说明。

Closing

结尾

End with low-pressure, confident energy. Not desperate, not corporate.
I'm currently at [Company] and open to what's next. I think my experience lends
nicely to what you're building — so I think we'd both get something out of a
conversation.

[First Name]
[email]
Avoid:
  • "I look forward to hearing from you"
  • "Please find attached my resume"
  • "I would love the opportunity to..."
  • "I am excited to potentially join..."
以低压力、自信的语气收尾，既不卑微也不生硬刻板。
I'm currently at [Company] and open to what's next. I think my experience lends
nicely to what you're building — so I think we'd both get something out of a
conversation.

[First Name]
[email]
需避免：
  • “期待您的回复”
  • “附上我的简历”
  • “我渴望获得……机会”
  • “我很期待能加入……”

Research Before Writing

撰写前的调研

Before writing the email, gather:
  1. Company angle — read their website, JD, or About page. Find one specific thing worth mentioning.
  2. Recipient name — LinkedIn, team page, or AngelList. "Hi [Name]" beats "Hi Hiring Manager" every time.
  3. Relevant projects — match the candidate's most relevant work to the role domain.
  4. Stack overlap — mention it only if there's a genuine match.
If the user provides a JD but no company website, ask for it or fetch it before writing.
撰写邮件前，需收集以下信息：
  1. 公司切入点——浏览公司官网、招聘启事或关于我们页面，找到一个值得提及的具体细节。
  2. 收件人姓名——通过LinkedIn、团队页面或AngelList查找。“嗨[姓名]”永远比“嗨招聘经理”效果更好。
  3. 相关项目——将求职者最相关的工作经历与职位领域匹配。
  4. 技术栈重叠——仅当存在真正匹配时才提及。
若用户提供了招聘启事但未提供公司官网，需在撰写前询问或获取官网链接。

Length Guidelines

篇幅指南

  • Ideal: 200–300 words
  • Maximum: 400 words
  • Minimum: 150 words (don't strip out substance for brevity)
Longer is fine if every sentence earns its place. Cut anything that could apply to any company.
  • 理想篇幅： 200–300词
  • 最大篇幅： 400词
  • 最小篇幅： 150词（不要为了简洁而删减核心内容）
只要每句话都有存在的价值，篇幅长一些也无妨。删除任何适用于所有公司的通用内容。

Output Format

输出格式

Always wrap the final email in a plain code block for clean copy-paste:
Subject: Quick intro — [Name]

Hi [Name],

[Email body]

[First Name]
[email]
最终邮件需始终包裹在纯代码块中，以便清晰复制粘贴：
Subject: Quick intro — [Name]

Hi [Name],

[Email body]

[First Name]
[email]

Common Mistakes to Avoid

需避免的常见错误

Too confident: ❌ "I would be an exceptional addition to your team" ❌ "My background uniquely positions me for this role" ✅ "I feel like I'd be a strong fit" — states a belief, doesn't claim certainty
Too humble: ❌ "I know I may not have all the experience you're looking for, but..." ❌ "I'm just reaching out on the off chance..." ✅ Acknowledge gaps directly and move on — don't apologize
Too long: ❌ Three paragraphs listing every achievement ✅ One paragraph on background, one on the connection
Too generic: ❌ Opening with "I am writing to express my interest in..." ✅ Opening with what specifically pulled them to this company
No research: ❌ "I love your product and mission" ✅ "The 5% stat — only 5% of a $25B market online — doesn't feel like a feature gap, it feels like an entire industry that hasn't digitised"
过于自负： ❌ “我将是您团队的绝佳补充” ❌ “我的背景让我成为该职位的最佳人选” ✅ “我认为自己非常适合这个岗位”——表达个人看法，而非绝对断言
过于谦卑： ❌ “我知道我可能不具备您要求的所有经验，但……” ❌ “我只是抱着试一试的心态联系您……” ✅ 直接提及差距并转移话题——无需道歉
篇幅过长： ❌ 用三段文字罗列所有成就 ✅ 一段介绍背景，一段阐述关联点
过于泛化： ❌ 开头写“我写信是为了表达对……的兴趣” ✅ 开头点明吸引你关注该公司的具体点
缺乏调研： ❌ “我喜欢你们的产品和使命” ✅ “那个5%的数据——250亿美元的市场中仅5%已线上化——这不是功能缺口，而是整个尚未数字化的行业”

Example Email

示例邮件

Subject: Quick intro — Sarah Chen

Hi Marcus,

I just came across Meridian and spent more time on your site than I planned.
What pulled me in was the framing around your data infrastructure — you're not
just building an LLM layer on top of existing records, you're rethinking how
clinical data flows through the system in the first place. That's a harder
problem and a more interesting one.

I'm based in India, flagging that upfront. Happy to figure out the rest if
there's a real fit.

I currently work at Lune, a London-based climate intelligence company, where I
build event-driven data pipelines and agentic AI workflows for emissions
compliance — regulated, data-intensive systems where reliability isn't optional.
I also built Memos, a RAG system from scratch: hybrid retrieval, reranking,
ChromaDB, FastAPI. And InframetAI, an SDK for LLM cost and latency
observability that came out of seeing what breaks when the data layer isn't
designed around how models actually work.

I think you're looking for engineers who've actually built AI systems end to
end, not just wrapped APIs. That's the work I've been doing.

More about me: yourportfolio.com/about

I'm currently at Lune and open to what's next. I think my experience maps
closely to what you're building — so I think we'd both get something out of
a conversation.

Sarah
sarah@email.com
Subject: Quick intro — Sarah Chen

Hi Marcus,

I just came across Meridian and spent more time on your site than I planned.
What pulled me in was the framing around your data infrastructure — you're not
just building an LLM layer on top of existing records, you're rethinking how
clinical data flows through the system in the first place. That's a harder
problem and a more interesting one.

I'm based in India, flagging that upfront. Happy to figure out the rest if
there's a real fit.

I currently work at Lune, a London-based climate intelligence company, where I
build event-driven data pipelines and agentic AI workflows for emissions
compliance — regulated, data-intensive systems where reliability isn't optional.
I also built Memos, a RAG system from scratch: hybrid retrieval, reranking,
ChromaDB, FastAPI. And InframetAI, an SDK for LLM cost and latency
observability that came out of seeing what breaks when the data layer isn't
designed around how models actually work.

I think you're looking for engineers who've actually built AI systems end to
end, not just wrapped APIs. That's the work I've been doing.

More about me: yourportfolio.com/about

I'm currently at Lune and open to what's next. I think my experience maps
closely to what you're building — so I think we'd both get something out of
a conversation.

Sarah
sarah@email.com