How to write a cold email from a job post
Open with the job post, quote the line that shows the problem, connect it to the one thing your product does about that problem, and ask one short question. Write to the person doing the hiring, not the role being hired, keep it under about 100 words, and send it while the post is still open.
Why a job post is a good reason to write
Most cold emails fail at the first line, because there is no reason for the email to exist today. A job post fixes that. It is public, it is dated, and it describes a problem in the company's own words: what they are building, what is slowing them down, and which team owns it.
That gives you three things a generic email never has: a reason to write now, a line you can quote back, and the name of the team that cares.
The steps
- Pick posts that show your problem. A company hiring is not enough. Look for a sentence that describes the work your product helps with. If you cannot point to one, skip the company.
- Write to the person hiring. Usually the founder at a small company, or the head of the team the role reports to. Not the role itself, which is still empty.
- Open with the post. Name the role and quote or paraphrase the one line that matters. This is your whole introduction.
- Connect it to one problem. One sentence on the difficulty that line points to, in plain words.
- Say what you do about it. One sentence. No feature list.
- Ask one short question that they can answer in a few words, about how they handle it today.
- Send it soon. Posts close, and the problem moves on with them.
Three examples from this week's job posts
Each quote below is copied word for word from a real job post published this week, with the company name hidden. The emails are examples we wrote to show the method, each for a different kind of product. Replace the bracketed parts with your own.
A first sales hire
“As the first sales hire, you’ll do the work and write the playbook while you do it.”
There is no sales team yet, so the founder is still deciding how selling will work. Write to the founder. This one suits anything a first salesperson needs: prospect data, a CRM, call coaching.
Subject: Your founding AE post
Hi [first name],
Saw your post for a founding Account Executive. The line about doing the work and writing the playbook at the same time stood out.
That usually means building the first prospect list too. [Product] gives a new rep a list of accounts that need what you sell, so the playbook starts with real conversations.
Who will own that first list, you or the new hire?
AI in customer support
“An AI agent already handles routine requests.”
The team has automated the easy tickets and is hiring a person for the rest. Write to the head of support. The opening is what happens after automation, not whether to automate.
Subject: The AI agent in your support post
Hi [first name],
Your Customer Support Specialist post mentions that an AI agent already handles routine requests.
Once an agent takes the easy tickets, the hard part is knowing which of its answers are wrong. [Product] reviews AI answers and flags the ones a person should check.
How are you checking the agent's answers today?
SOC 2 work
“Supporting audits like SOC 2 with automated evidence collection.”
Notice what the post already tells you: they automate evidence collection. Pitching that would miss. Write to the head of security or the CTO about a part of the audit the post does not cover.
Subject: SOC 2 and access reviews
Hi [first name],
Saw you're hiring a Senior Security Engineer to support audits like SOC 2 with automated evidence collection.
Access reviews are one part that is easy to leave manual. [Product] runs them from your identity provider and keeps the record for the auditor.
Is that already automated on your side?
A template
Subject: Your [role] post
Hi [first name],
Saw your post for a [role]. The line about [the part that shows the problem] stood out.
[One sentence on the difficulty behind it.] [Product] [does one thing about it].
[One question about how they handle it today]?
Mistakes to avoid
- "I noticed you're hiring." Every company is hiring. Quote the specific line or do not mention the post.
- Congratulating them on the role. It reads as filler. Go straight to the line that matters.
- Claiming to know more than the post says. If the post does not mention a problem, do not invent one.
- Pitching the person being hired. They are not there yet, and they did not write the post.
- More than one ask. One question. No calendar link in the first email.
Where to find posts like these
Each week we publish counts and quotes for a few patterns in the hiring signals report. To check a single post, paste it into the hiring signal checker, then run your draft through the cold email checker. For the difference between hiring signals and other data, read hiring signals vs intent data.
Questions
Is it okay to mention a job post in a cold email?
Yes. The post is public and the company wrote it to be read. Mentioning it tells the reader why you are writing now. Stick to what the post says about the work, and leave out salary, the candidate or guesses about the company's problems.
Who should I email, the hiring manager or the person being hired?
The person doing the hiring. The new hire has not started yet, and the problem in the post belongs to whoever is hiring for it. At a small company that is often a founder; at a larger one it is the head of the team the role reports to.
How soon after a job post appears should I write?
Within the first week or two, while the role is open and the problem is on their mind. Posts close once the role is filled, and by then the new hire may already have chosen their tools.
How long should the email be?
Under about 100 words: one line on the post, one on the problem, one on what you do, and one question. No attachments, and no links in the first email, so it reads like a note from a person.