How to Cold Email a Hiring Manager (Without Looking Presumptuous)
To cold email a hiring manager, find the actual person who owns the team (not HR or the recruiter), reference one specific, verifiable detail about their team or product, tie it to one concrete thing in your background, keep it under 125 words, and apply through the formal process either before or right after you send it. Done well, it puts your name in front of the person who actually makes the call. Done badly, it reads as a shortcut and can work against you.
Who is actually worth emailing directly?
The hiring manager is the person who owns the role, usually the engineering manager, director, or team lead you would report to if hired, not a recruiter or an HR generalist. That distinction matters because a recruiter is filtering candidates against a spec; a hiring manager is trying to solve a problem on their team. A message that speaks to the second person reads completely differently than one written for the first.
Three ways to find them:
The job posting itself. Some postings, especially at startups, name the hiring manager directly ("You'll report to our Head of Platform, [Name]") or link to the team's page. Read the full posting before searching elsewhere.
LinkedIn, searched by team and title. Search the company name plus the likely title ("engineering manager," "director of platform," "VP engineering") and cross-reference against the team the role sits on. If the company lists an org chart or team pages on their site, use that to confirm you have the right person before the person one level up or down.
Company engineering blog author bylines. Many tech companies publish engineering blogs where team leads write about architecture decisions, incidents, or launches. A byline on a post that touches the team you're applying to is often a faster, more specific way to identify (and reference) the right person than a cold LinkedIn search.
When does emailing the hiring manager actually help, and when is it pointless?
Company size and hiring maturity decide this almost entirely. At a small company or startup, the hiring manager often reads their own inbox, screens their own applicants, and has real discretion over who gets a first call. An email from a specific, well-matched candidate can genuinely move you to the front of the line. Indeed's guidance on emailing hiring managers directly frames this as a way to increase the odds a human actually reads your resume, not a replacement for the standard process.
At a large company with an established recruiting org, the math changes. The hiring manager likely doesn't see individual inbound messages before HR or a recruiter filters them, and unsolicited email frequently gets forwarded straight back to "please apply through our careers page." Sending the same cold email you'd use for a 40-person startup to a hiring manager at a company with a mature ATS pipeline mostly signals that you didn't do the homework on how that company actually hires. It's not that it never works at scale, it's that the odds are worse and the effort is better spent elsewhere: a warm introduction, a referral, or a tailored application through the formal process will usually outperform a cold note that a director never personally reads.
If you're unsure which bucket a company falls into, headcount is a reasonable proxy: sub-200-person companies and recent-stage startups skew toward reachable hiring managers; companies with a dedicated recruiting team and a formal req process skew toward the opposite. When in doubt, a warm path in through your network beats a cold one either way. If you don't have a warm path yet, building one before you need it pays off across every job search, not just this one.
What should the email actually say?
Keep it short: 75-125 words is the range that shows up consistently in current guidance on cold outreach for job seekers. Long enough to establish who you are and why you're writing, short enough to read on a phone in under a minute.
The structure that works:
One specific, verifiable detail about their team or product. Not "I love what you're building," which is generic flattery that reads as filler regardless of how sincere it is. Instead, something you could only know from having actually looked: a specific decision from an engineering blog post, an architecture choice mentioned in a conference talk, a product feature you used and have an opinion on, a recent launch. Specificity is the entire signal here. It's the difference between "I did my homework on your team" and "I am sending this to fifty people this week."
One concrete reason you're a fit, tied to something real in your background. Not a summary of your resume; one line that connects a specific thing you've done to a specific thing their team is working on. If you cut a service's latency by a measurable amount and their engineering blog talks about a similar bottleneck, that's the line. Vague claims like "I'm a strong fit for this role" do nothing a hiring manager can act on.
A low-friction ask. Don't ask to be hired. Ask for a short call, or simply flag that you've applied and wanted to make sure it landed on their radar. The lower the ask, the easier it is for a busy hiring manager to say yes.
Skip the personalization tokens and skip the enthusiasm-as-filler. If you've built resumes tailored to specific job descriptions before, the same discipline applies here: reference what's actually true about the team, not a generic version of what could be true about any team.
Hiring manager insight
"I never hired anyone who didn't reach out to me after they sent their resume."
— LinkedIn News: Should You Message a Hiring Manager?
That same LinkedIn feature also carries the counterpoint from a hiring manager who has been on the other side of the volume: one contributor described screening hundreds of applicants for a single role and not wanting all of them reaching out individually. Both things are true depending on team size and hiring volume, which is exactly why the company-size judgment call above matters more than any universal script.
Should you still apply through the formal process?
Yes, in almost every case. Emailing the hiring manager directly should supplement the formal application, not replace it. If a role requires a formal ATS application to be considered at all (most do, for compliance and tracking reasons), skipping it and only sending a cold email can read as trying to route around the process entirely, which is the opposite of the impression you want to make.
The sequence that avoids looking presumptuous: apply through the company's normal channel first, then send the email within a day or two, briefly noting that you've applied and flagging the specific reason you're a strong match. That framing (I've done the expected thing, and here's one more piece of context that's useful) lands very differently than an email that implies the formal process is beneath you. If you're tracking multiple applications like this at once, a referral where someone internal can vouch for you still tends to outperform even a well-written cold email, so treat this as one channel among several rather than a replacement for building real connections at target companies.
Key takeaways
Target the hiring manager, not a generic company inbox
The hiring manager is the person who owns the role and would be your manager, not HR or a recruiter. Find them through the job posting, a LinkedIn search scoped to the team and title, or an engineering blog byline. Getting the wrong person defeats the purpose.
Company size determines whether this approach works at all
At small companies and startups, the hiring manager often reads their own inbox and has real discretion. At large companies with formal recruiting pipelines, the same email is more likely to get redirected back to the standard process, so weigh the effort against the odds before sending.
Specificity is the entire signal, not the tone
One verifiable detail about the team, tied to one concrete thing in your background, does more work than any amount of polite enthusiasm. Generic flattery ("I love what you're building") reads as filler no matter how sincerely it's meant.
Keep it short and end with a low-friction ask
75-125 words is the range that shows up consistently in current guidance on this kind of outreach. Ask for a short call or simply flag that you've applied, don't ask to be hired in the first message.
Apply formally too, don't treat the email as a substitute
Sending a cold email instead of the standard application can look like you're trying to skip the process. Apply through the normal channel first or in parallel, then send the email as added context, not a replacement.
Frequently asked questions
How do I find a hiring manager's email address if it isn't listed anywhere?
Check the job posting first, some name the hiring manager directly. If not, search LinkedIn by team and title to identify the person, then look for a company email pattern (often firstname.lastname@company.com or firstname@company.com) via the company's own site or a public bio page. Avoid scraping tools that generate unverified guesses at scale; a wrong guess bounces and wastes the attempt.
Is it rude to email a hiring manager if I've already applied through the website?
No, as long as the email makes clear you've already applied and adds something new, rather than repeating your resume. Framing it as "I applied and wanted to flag one specific reason I think I'm a strong match" reads as diligence, not as an attempt to skip the process.
What if the hiring manager never replies?
No reply is common and not necessarily a signal about your fit. One follow-up after about a week, adding a small new piece of information rather than just "checking in," is reasonable. Beyond that, move your energy to other applications and warm introductions rather than repeated follow-ups.
Does this approach work for entry-level roles too?
It's harder to make specific and credible with limited experience, since the "concrete reason you're a fit" section relies on real prior work. It still can work if you tie a project, an internship, or coursework to something specific about the team, but a warm introduction or referral tends to carry more weight than a cold email at the entry level.
Should I attach my resume to a cold email to a hiring manager?
Yes. Attach it as a PDF so the hiring manager doesn't have to ask, and keep the email itself focused on the one specific hook rather than restating the resume's contents. The resume does the detail work; the email earns the ten seconds of attention that gets it opened.
Track every company you're targeting, tailor the resume you attach to each one, and keep the whole search in one place at hire.monster/jobs.