The short answer
A cold message to a hiring manager works when it is short, addressed to the right person, tied to a real role or a real problem, and asks for something small. It fails when it is a resume with a covering paragraph. Expect most to go unanswered and send them anyway, because the ones that land skip several queues at once.
What matters most
- Message the person who owns the work, not a generic address. The whole advantage disappears if it lands in a shared inbox.
- Five or six sentences. A long message signals that you have not worked out what matters, and it will not be read on a phone.
- Ask for something small — a short call, or an answer to one question — rather than for consideration.
- Most will not reply, and that is the normal rate rather than a verdict. Volume is not the fix; specificity is.
When cold outreach is the right move
It is not a universal technique. There are situations where it clearly beats the ordinary route, and situations where it is a waste of a good afternoon.
It works best when there is a live posting and you want your application read by the person who wrote it rather than the person who filters for it; when you have a genuinely specific reason to want to work with that team, rather than that company; and in smaller organisations where the hiring manager is reachable and the process is not fully mediated by a recruitment function. It works least well at very large employers with strict routing, in regulated public-sector processes where contact outside the formal channel is discouraged or prohibited, and when you have nothing specific to say beyond wanting a job.
The sequence
- 1Identify the actual owner of the work
Not the CEO, not HR. The person the role reports to — usually a head of department or a team lead. On a posting this is often inferrable from the reporting line described in the advert.
- 2Find a legitimate route to them
A professional profile's messaging function, a public work address, a conference talk, an industry forum. Do not use scraped personal addresses or guessed mobile numbers; the method you use is part of the first impression.
- 3Work out the one thing you would say if you had ten seconds
This is the message. Everything else is packaging. If you cannot name it, you are not ready to send anything, and no amount of polish will cover the gap.
- 4Write five sentences
Who you are, why them specifically, one piece of concrete evidence, the small ask, the easy out. In that order, on one screen.
- 5Send it, log it, and move on
One follow-up after about a week if there is no reply. Then stop. Record it in your tracker so you do not accidentally approach the same person twice.
What good and bad look like
Dear Mr Okafor, I am writing to express my strong interest in opportunities within your engineering organisation. I am a highly motivated professional with extensive experience across the full software development lifecycle and a proven track record of delivering results in fast-paced environments. Please find my resume attached for your consideration. I would welcome the opportunity to discuss how my skills and experience could add value to your team. I look forward to hearing from you.
Hi Daniel — I saw the platform engineer role on your careers page. I have spent the last three years on payments infrastructure at Kestrel, most recently cutting our settlement reconciliation job from six hours to about forty minutes, which is the same class of problem the posting describes. I have applied through the site, but wanted to flag it here in case it is useful. Happy to answer anything by email if a call is not practical — and no problem at all if this is not the right time.
The parts people get wrong
- Length. The most common failure by a distance. If it does not fit on a phone screen, it will be deferred, and deferred means never.
- Flattery. A sentence admiring the company reads as filler. A sentence showing you understand a specific problem they have reads as competence. Only one of these is worth including.
- The unbounded ask. "I would welcome the opportunity to discuss" is not a request anyone can act on. "Would fifteen minutes on Thursday work, or is email easier?" is.
- Attachments in the first message. Some filters strip them and some recipients will not open them. Say the one thing in the body and offer the resume; the attachment is not what earns the reply.
- Chasing. One follow-up, once, after about a week. Beyond that you are not being persistent, you are being remembered for the wrong reason.
- Sending the same thing to twelve people. The single variable that affects reply rates is whether the message could only have been written to that person. Volume actively works against it.
When there is no posting
Approaching a company with no advertised role is a different exercise, sometimes called a speculative application, and it has a lower hit rate but a much better ratio when it works — you are the only candidate in the conversation. It requires more of you: instead of matching a posting you have to identify something the team is plausibly dealing with and show you have handled that class of problem. Generic speculative applications are the least effective thing in the whole job search. Specific ones occasionally produce roles that are created around the candidate.
The National Careers Service guidance on speculative applications is a sensible short summary if you want a second view, and Purdue's writing lab material on job search letters is useful on structure. Both make the same underlying point: the burden of relevance is entirely on you when nobody asked you to write.
- It is addressed to the person who owns the work, by name.
- It fits on a phone screen without scrolling twice.
- It names a specific role, team or problem.
- It contains one concrete piece of evidence, not a list of qualities.
- The ask is small and specific enough to answer in two minutes.
- There is an explicit, gracious way to say no.
- It could not have been sent to anyone else.
Questions people actually ask
Is it acceptable to email a hiring manager directly?
In most private-sector contexts, yes, provided the message is short, relevant and reached them by a legitimate route. It is generally discouraged or prohibited in structured public-sector and federal processes, where contact outside the formal channel can create fairness problems, so check the announcement first.
How long should a cold outreach message be?
Five or six sentences. It should fit on a phone screen without scrolling, because that is where it will be read. Length works against you here: a long message suggests you have not identified what actually matters, and it is much more likely to be deferred and then forgotten.
What should I ask for in the message?
Something small and specific — fifteen minutes, or an answer to one question. Asking to be considered for opportunities is not a request anyone can act on, so it produces no reply even from people who were interested. Make it easy to grant and easy to decline.
How many people should I contact at one company?
One, in almost all cases. Multiple approaches to the same organisation get noticed and read as scattershot rather than keen. If the first person does not reply, follow up once and then leave it rather than trying someone else on the same team.
What if the hiring manager does not reply?
That is the common outcome and it carries very little information. Follow up once after about a week, then stop and let the normal application take its course. A non-reply usually means a full inbox and a busy week, not a decision about you.
