Most job seekers who finally email a hiring manager directly have already sent a hundred applications into portals and heard nothing back. So the first cold email carries a lot of hope and, usually, a lot of words. Below is a cold email to a hiring manager example built the way most of them get written, followed by a rewrite and a reason for every change.
The “before” message is a composite. It is assembled from patterns that show up again and again in job seekers’ outreach, and it is not a real person’s email. The rewrite uses the same candidate and the same job, so the only variable is the writing.
Why the portal pile makes this email worth getting right
Greenhouse CEO Daniel Chait told Fortune in August 2026 that for every 10 open roles on Greenhouse’s platform, there are 2,539 applicants. That works out to roughly 254 people per posting. The same article reports that applications per recruiter are up 412%. A recruiter carrying that load is skimming. Nobody reads the 254th cover letter closely.
Chait’s own advice in that piece points away from the crowd: skip the famous names that are “in the news every day” and look at lesser-known companies doing the same kind of work, because those often have far fewer applicants. That logic extends to the channel too. The application portal is where everyone else is. A hiring manager’s inbox is much less crowded.
The catch is that cold email has its own bad odds. Backlinko and its data partner Pitchbox analyzed 12 million outreach emails and found that only 8.5% got any response at all. Those were marketing outreach messages, the kind of link-building pitches sent to publishers, so the numbers are a rough guide for job seekers and not a promise. Still, the direction is useful. Most cold email gets ignored, and the details below are what separated the replies from the silence in that data.
The “before”: a cold email to a hiring manager example that got ignored
Here is the composite. Read it the way a busy engineering or product leader would: on a phone, between meetings, with 40 other unread messages above it.
Subject: Application for Senior Product Manager Position
Dear Hiring Manager,
My name is [Your name] and I am a results-driven product manager with over eight years of experience in B2B SaaS. I am writing to express my strong interest in the Senior Product Manager role at [Company]. I have been following [Company] for some time and I am truly passionate about your mission to transform the logistics industry.
Throughout my career I have led cross-functional teams, launched multiple products, and consistently exceeded my goals. I am a strategic thinker with a strong analytical mindset and excellent communication skills. I thrive in fast-paced environments and I am confident that I would be a great fit for your team and your culture.
I have already applied through your careers page, but I wanted to reach out directly as well. I have attached my resume for your review. I would love the opportunity to discuss how my skills and experience can contribute to [Company]’s continued success. Please let me know if there is a convenient time to connect.
Thank you so much for your time and consideration. I look forward to hearing from you.
Best regards, [Your name]
Nothing in it is rude. Every sentence could be sent to any company with the name swapped, and the reader can tell within two lines.
What went wrong, line by line
The subject line. “Application for Senior Product Manager Position” reads like an automated notification from the applicant tracking system. It also tells the hiring manager that the email duplicates something already sitting in the portal, which is a reason to skip it. Backlinko found that subject lines between 36 and 50 characters drew the best response rates, and that personalized subject lines lifted responses by 30.5%. This one is personalized to nothing.
“Dear Hiring Manager.” The sender went to the trouble of finding this person’s email and then didn’t use their name. That undoes most of the effort.
“My name is… results-driven… over eight years.” The first sentence is about the sender. So is the second. The reader still has no idea why this email landed in their inbox and not someone else’s.
“Truly passionate about your mission.” Every company’s mission page gets quoted back to its managers constantly. It signals that the sender read the homepage, which takes a minute. Nothing in it proves interest in the team’s actual work.
The adjective paragraph. Strategic thinker, analytical mindset, excellent communication skills, thrives in fast-paced environments. Each claim is unverifiable and identical to the ones in the 254 applications already in the queue. A hiring manager can’t do anything with an adjective.
“I have attached my resume.” Unsolicited attachments from strangers are easy to ignore and sometimes get flagged. The resume is already in the portal anyway, by the sender’s own account.
The ask. “A convenient time to connect” asks the reader to do the work: figure out what the call is for, decide whether it’s worth it, and propose times. A vague ask is the easiest kind to put off, and an email that gets put off usually gets forgotten.
The length. Close to 200 words, with the one relevant fact (eight years of B2B SaaS product work) buried in the first paragraph under a label.
The rewrite, change by change
Same candidate, same role. The rewrite assumes 20 minutes of research: the posting, the hiring manager’s recent public posts, and the company’s product changelog. For how to do that research without coming across as invasive, see the guide on how to research a hiring manager before you reach out.
Subject: Carrier onboarding drop-off, from a PM who fixed it
Hi [First name],
Your post last week about carrier onboarding stalling at the document-upload step is why I’m writing to you directly.
At my last company I owned onboarding for a B2B freight product. Our upload step lost about a third of new accounts. We cut it to two fields and moved the rest after first load, and completed onboarding went up within a quarter.
I applied for the Senior PM role on your team. Would you be open to a 15-minute call next week so I can ask how you’re thinking about that step? If the timing is wrong, a pointer to the right person would help just as much.
[Your name] [LinkedIn URL]
The specifics in this example (the onboarding step, the fix) are placeholders for whatever the real candidate has done. The structure is the part to copy. Here’s what changed.
The subject line is 45 characters and it is about their problem. It sits inside Backlinko’s 36-to-50 range and names something the hiring manager cares about. It also implies the email contains something useful, and that is usually what gets a stranger’s email opened.
The first line answers why this person. One sentence that says why the email went to them specifically. It points at something they said or built, so the reader knows within five seconds that this is not a mass send. Backlinko found that personalized message bodies got 32.7% more replies than generic ones.
The second paragraph swaps the adjectives for a single story with a problem, an action and a result, chosen because it maps onto what the team is dealing with right now. One relevant proof point beats five generic ones, because the reader can picture it happening on their team.
The ask is small. Fifteen minutes, next week, with a stated purpose. It also offers an exit (“a pointer to the right person”) so declining doesn’t feel awkward. That second option matters. Backlinko found that emailing more than one contact improved response rates by 93%, and a referral inside the company is the cheapest way to reach a second contact.
There’s no attachment. The LinkedIn URL in the signature lets the reader check the sender in one click. In Backlinko’s data, messages with social profile links in the signature had a 9.8% higher response rate.
The whole thing is under 120 words and fits on a phone screen without scrolling. Everything that was cut was either already in the portal or was an adjective.
The follow-up most people never send
The single biggest lever in Backlinko’s data was not in the first email at all. Sending one additional follow-up boosted replies by 65.8%. Sequences of three or more messages did best overall, and campaigns that combined multiple messages with multiple contacts did 160% better than a one-off email to one person.
Most job seekers send one cold email to a hiring manager, hear nothing, and assume it was a no. Often it was a “not right now” that slid down the inbox. A short follow-up four or five business days later gives the message a second chance:
Subject: Re: Carrier onboarding drop-off, from a PM who fixed it
Hi [First name], bumping this in case it got buried. Happy to send the before-and-after numbers from that onboarding change if that’s more useful than a call.
[Your name]
Two sentences. It adds something new (an offer of concrete material), it doesn’t guilt the reader, and it lowers the ask further. If a second follow-up still gets nothing, move to a different person on the same team. The playbook in how to follow up on a job application with no response covers timing in more detail.
Day of week matters a little too. In Backlinko’s data, emails sent Monday through Friday converted 23.3% better than weekend sends.
A cold email hiring manager template built from the teardown
If a reusable shape helps, this is the rewrite stripped down to its parts. Treat it as scaffolding, not a fill-in-the-blanks form. The more a message reads like a template, the more it performs like one.
- Subject, 36-50 characters: their problem or project, plus a hint of why it’s relevant to the sender.
- Line one: why this person. A post, a launch, a talk, a changelog entry, a job posting detail.
- Proof: one result from past work that maps to what they are dealing with. Numbers if the candidate has them, a concrete before-and-after if not.
- Ask: 15 minutes, a time window, a stated purpose, and an easy alternative.
- Signature: name and one profile link. No attachment.
- Follow-up: four or five business days later, adding something new.
A personalized job outreach message like this takes longer than a portal application. That’s a fair complaint. But it is competing against a far smaller pile, and the job application response rate for the portal route, at 254 applicants per posting, isn’t a number anyone should want to bet on.
Send fewer, better messages
The “before” in this cold email to a hiring manager example failed because it could have been written without knowing anything about the reader. The rewrite works because it couldn’t have been. Twenty minutes of research per message is a better use of an afternoon than another 20 applications.
Doing that research for every role is the slow part: finding the hiring manager, figuring out what they’re working on, and turning it into a first line worth reading. angld.AI handles that research-to-outreach work, so the time goes into the conversations that come back.
