A cold email that works has four parts: a subject line naming the role or problem, one sentence proving you researched them specifically, two sentences of concrete evidence you can do the work, and one small ask — a short call, not a job. Send it to the hiring manager, not HR, and keep the whole thing under 120 words.
The person you're emailing gets dozens of unsolicited messages and gives each a two-second scan. Length reads as cost; specificity reads as signal. A 400-word life story gets archived unread. A 100-word note that names their team, their product, and one thing you've done that maps to their problem gets a real look, because it's obviously not a mail-merge.
Cold email works best where postings don't: small companies, teams that hire before opening a req, and roles where the manager owns hiring directly. At large companies with formal pipelines, a cold email mostly works as a nudge to go look at your application — still useful, but different physics.
Subject: name the thing, not yourself. "Backend engineer — interested in your payments team" beats "Opportunity inquiry." Then: "Hi Dana — I saw your team just launched instant payouts, and noticed you're hiring backend engineers. I've spent three years building payment reconciliation systems at a fintech, including an idempotent retry layer that eliminated our double-charge incidents. If you're still hiring, I'd love fifteen minutes to hear what the team needs — and if not, no worries at all."
That's the whole email: hook proving research, evidence with texture, small ask, graceful out. Attach nothing on the first send; offer your resume when they reply. An attachment from a stranger triggers both spam filters and suspicion.
Aim for the hiring manager — the person the role reports to — or a senior member of the target team. LinkedIn plus the company's team page usually identifies them; standard email patterns like first.last at the company domain are guessable, and one wrong guess bounces harmlessly.
Follow up once, about a week later, with two sentences on top of the original thread. Then stop. Cold outreach is a numbers-plus-quality game: ten researched emails to well-chosen managers will outperform a hundred generic ones, and each no costs you nothing but the ask.
Not on the first message. Attachments from unknown senders trip spam filters and feel presumptuous. End with a small ask instead; when the person replies with any interest, send the resume immediately — now it's a requested document, not unsolicited bulk.
The hiring manager, almost always. Recruiters are staffed to process pipelines, not create them, so an unsolicited email to HR usually gets routed to the careers page. The manager owns the problem you're offering to solve and can pull you into the process directly.
There's no honest universal number — it depends on your targeting and market. The controllable variables are research quality and volume of well-chosen targets. Expect most to go unanswered even when well-written, and treat every reply as the top of a funnel, not a verdict.
When they reply asking for your resume, it needs to land in one read — score it free against the kind of role you're pitching before you start sending cold emails.
