Guides

Cold Email for a Job: 75–120 Word Structure That Gets Replies

A line-by-line structure for a short cold email to a hiring manager: subject, opener, proof, ask, and sign-off, with fictional examples and an editing pass.

· 5 min read

The best job cold emails tend to be short enough to read on a phone between meetings. This guide gives you a repeatable structure that lands in roughly 75 to 120 words, which is about four short paragraphs.

No structure guarantees a reply. Timing, fit, and whether a role is still open matter more than wording. But a tight structure gives a busy person the fewest reasons to skip you.

Why 75–120 words?

It isn’t a research-backed magic range. It’s a practical constraint:

  • Under ~75 words, you usually can’t fit both a specific reason for writing and real proof.
  • Over ~120 words, the email starts to scroll on a phone and drift into cover-letter territory.

Treat it as a budget. If you’re at 160 words, something is doing double duty or doesn’t belong.

The structure at a glance

Part Job Rough length
Subject line Get opened by the right person 4–8 words
Line 1: Why them Show you looked; name the role 1–2 sentences
Line 2: Why you One or two true, specific proof points 1–2 sentences
Line 3: The ask Small, easy yes 1 sentence
Sign-off Name + one link 2–3 lines

Subject line: plain and specific

Formula: role + relevant hook.

  • Customer Success Lead – SaaS renewals background
  • Applied: Junior Data Analyst (SQL + dashboards)
  • Frontend role – accessibility work

Skip clever puns, fake “Re:” threads, and anything with exclamation points.

Line 1: Why them

Name the role and one specific, true detail that connects to it. This proves the email isn’t a mass send.

Weak: “I came across your company and was really impressed by your mission.”

Better: “I applied for the Customer Success Lead role. The post mentions cutting churn in the first 90 days, which is the part of CS I’ve spent the most time on.”

The better version is specific, checkable, and leads directly into your proof.

Line 2: Why you

One or two proof points. Concrete beats impressive. Good proof points are:

  • Specific: a project, a system, a type of customer, a tool
  • True: something you could talk about for ten minutes in an interview
  • Relevant: tied to what the post or the person cares about

Weak: “I’m a results-driven professional with a passion for customer success.”

Better: “At my current company I built our onboarding check-in sequence and ran QBRs for about 40 mid-market accounts.”

If you have a real number you can stand behind, use it. If you don’t, describe the work clearly instead of inventing one. A made-up metric is easy to spot and painful to defend in an interview.

Line 3: The ask

Make it small. You’re asking for a few minutes or a pointer, not a job.

  • “Would a 15-minute call in the next week or two be useful?”
  • “If it’s helpful, I can send a short write-up of how I approached it.”
  • “If you’re not the right person, who should I reach out to?”

One ask per email. Two asks make the reader choose, which often means choosing neither.

Sign-off

Keep it clean:

Thanks,
Sam Rivera
portfolio.example.com

One link is plenty. LinkedIn, a portfolio, or a relevant project. Don’t attach a resume unprompted; offer it or link to it.

Full example (fictional)

Subject: Customer Success Lead – SaaS renewals background

Hi Morgan,

I applied for the Customer Success Lead role on your team. The post mentions cutting churn in the first 90 days, which is the part of CS I’ve spent the most time on.

At my current company I built our onboarding check-in sequence and ran quarterly reviews for about 40 mid-market accounts.

Would a 15-minute call in the next week or two be useful? If you’re not the right person, I’d appreciate a pointer.

Thanks, Sam Rivera linkedin.com/in/example

(Fictional example. About 80 words, greeting to sign-off.)

A second example: early career (fictional)

Subject: Junior Data Analyst – SQL + dashboard projects

Hi Chris,

I applied for the Junior Data Analyst opening. Your team’s post about moving reporting into one dashboard caught my eye.

In my final-year project I cleaned three messy public datasets in SQL and built a dashboard a local nonprofit now uses for monthly reporting. The full write-up and the queries are linked below.

Would you be open to a quick call, or is there someone else on the team I should contact?

Best, Alex Kim alexkim.example.com

(Fictional example. About 80 words, greeting to sign-off.)

Early-career proof points can come from school projects, internships, volunteer work, or side projects. Real and specific still beats impressive and vague.

The editing pass

Once you have a draft, run these cuts:

  1. Delete the first sentence if it’s warm-up. “I hope you’re having a great week” adds nothing.
  2. Cut adjectives you can’t prove. “Highly motivated,” “passionate,” “dynamic.”
  3. Swap abstract nouns for actions. “Responsible for onboarding” → “built the onboarding sequence.”
  4. Check every claim. Could you explain it in an interview without squirming?
  5. Read it aloud. If a sentence sounds like a press release, rewrite it the way you’d say it.
  6. Count the words. Most email clients or a quick paste into a word counter will do.

Using AI to draft within the structure

AI can draft quickly, but it pads and invents unless you constrain it. A simple prompt shape:

Write a cold email to a hiring manager, 120 words max.
Role: [ROLE]. Person: [NAME, TITLE].
One true detail about them or the job post: [DETAIL].
My proof points (use only these, do not invent numbers): [BULLETS].
Ask: a 15-minute call, or who else to contact.
Do not use: "I hope this finds you well", "passionate", "excited to", "leverage".
Plain, warm, direct. Sound like a person, not a cover letter.

Then edit by hand. The Hiring Manager Cold Email Kit ($17) expands this into a full prompt workflow, including a voice-sample prompt so drafts match how you actually write, and 4 fictional example threads with word counts. See what’s inside.

What comes next

Examples on this page are fictional and written for illustration. This is general writing guidance, not career counseling; results vary.

Keep reading