Cold emailing the hiring manager

Six sentences: who you are, one piece of evidence that maps to their problem, one specific ask. Send it to the person who would manage the role, not to a careers inbox. Expect most of them to go unanswered — the ones that land are worth the rest.

This works because the alternative is a queue of four hundred applications and because hiring managers are the people who feel that queue as a problem. It fails when it reads as a template, which is what every long one does.

Finding the person

1. LinkedIn, by title and company. “Engineering Manager” plus the company plus the team name from the posting. The job description often names the team or the product; that is your search term.
2. The posting itself. Some list the manager. Many list the recruiter, who is the second-best target and often a better one — they are paid to reply.
3. Engineering blogs, conference talks, GitHub, release notes. Whoever wrote about the system you would work on.

For the address, the company’s format is usually deducible from any public email at the domain. Guessing works often enough to try once. But a LinkedIn message to the right person beats a guessed email to the right person, because it cannot bounce and cannot land in a spam filter. If you have no LinkedIn premium, a connection request with a note is free and carries 200 characters — enough for the ask.

The message

Subject: Backend role — pricing service

Hi Priya,

I saw the Senior Backend Engineer opening on your team. I’ve spent the last three years on payments infrastructure at [Company], most recently splitting our pricing service out of the monolith — cut p99 latency about 40% and survived two festive peaks.

Your posting mentions moving off a shared database, which is roughly the problem I just spent a year on. I’ve applied through the portal (req 4412), but wanted to reach you directly in case it’s useful.

Resume attached. Happy to talk whenever suits — and no worries at all if the role’s moved on.

Anand

Why each part is there

• The subject names the role and one concrete thing. “Job application” is deleted; “Interested in opportunities” is worse.
• Evidence, not adjectives. One thing you did, with an outcome. “Passionate about scalable systems” is what everyone writes when they have nothing to point at.
• A line that is about them. Something from the posting or their engineering blog. This is the sentence that proves the email is not a mail merge, and it is the one people skip.
• Say you already applied. Removes the awkwardness of asking them to bypass a process, and gives them a one-click action: forwarding your name to the recruiter.
• An easy exit. Once, briefly.

What sinks these

• Length. Anything past 150 words is read on a phone, badly, then archived.
• Asking for “15 minutes to pick your brain” with no role attached. That is a meeting request with no agenda from a stranger.
• Flattery. Two sentences admiring the company reads as the opening of a sales email, because it is.
• The same email to eight people at one company. They are in a Slack channel together.
• Attaching nothing. If they are interested, the next step should be zero effort for them.

Volume, and one follow-up

Five to ten a week, each genuinely written for that company. Reply rates on a well-targeted cold email are in the low tens of percent at best, and a template blasted at fifty companies is close to zero — so the trade is real: fewer, specific, with evidence.

One follow-up after a week, two lines, then stop. “Bumping this in case it got buried — still very interested in the backend role.” A second chase costs more than it recovers.

Where this site fits

The attachment is the point of contact here, and it is being opened by a person on a phone rather than by a parser — so what matters most is that the first third of page one says the thing your email just claimed. If the email leads with payments infrastructure and the resume opens with a generic objective, the two do not agree.

GetFinalCV renders the same document through the same pipeline every time, and it shows you the preview of what you are actually attaching before you send it. That is the narrow claim; the email is the part that does the work.