Recruiter outreach generator

Messages that get answered, not ignored.

A referred or introduced candidate is interviewed at several times the rate of a cold applicant, which makes outreach the highest-leverage twenty minutes in a job search. It's also the part most people avoid, usually because the messages they imagine sending feel like begging. They don't have to. The messages that work are short, specific, and ask for something small.

The single biggest mistake is asking for the wrong thing. "Can you refer me?" puts a stranger's reputation on the line for someone they've never spoken to, which is why it rarely lands. "Can I pick your brain?" asks for an open-ended block of time with no clear end. What works is one specific question that a person doing the job can answer in two minutes — about the team's actual problems, the stack, how the role came about, or what surprised them about the work. That's a request someone can say yes to.

The structure is four short lines. Who you are, in one clause. Why them specifically — something concrete about their work, their team, or the role, which proves this isn't a template blast. The one question. And an easy exit that removes any pressure to reply. Keep the whole thing under about 120 words; long outreach reads as a demand for attention rather than a request for two minutes of it.

Cold outreach to a recruiter works differently from outreach to a peer. A recruiter is measured on filling roles, so lead with the concrete match — the role you're targeting and the two or three things that make you obviously relevant to it. A peer or hiring manager is not thinking about their pipeline, so lead with curiosity about the work instead. Sending the recruiter message to an engineer is the most common reason otherwise good outreach goes unanswered.

Follow-ups deserve care. One well-timed follow-up seven to ten days after an application or an unanswered message is professional and occasionally decisive. It should add something — a relevant thought, a piece of work, a specific reason you're still interested — rather than say "just checking in", which asks the reader to do the work of remembering you. A second follow-up is sometimes reasonable. A third is a reason to stop considering you.

The post-interview thank-you is the most under-used message of all, and the highest-return. Within twenty-four hours, send four or five sentences: thanks, one specific thing from the conversation, and — if you fumbled a question — the two-sentence answer you wish you'd given. That last part genuinely persuades, because it demonstrates reflection and interviewers remember it. Long thank-yous read as anxious rather than keen.

WarmIntro drafts these from your actual background rather than a generic template, so the specifics are yours and the message doesn't read like the hundred others that person received this week. Everything runs in your browser and nothing is sent on your behalf — you review, edit and send it yourself, from your own account. Pair it with Scout to work out who is actually worth contacting at a given company.

• ✓Cold outreach, referral request, follow-up and thank-you templates
• ✓Grounded in your real background — not a generic blast
• ✓The 4-line structure that gets replies
• ✓Free, in your browser — nothing is sent for you

Why referral outreach converts ten times better than cold applications

A resume submitted through a job portal enters a queue with hundreds or thousands of others. It's processed by an ATS, filtered by keyword match, and if it passes, reviewed by a recruiter who has thirty seconds. A resume submitted by a peer or someone the hiring manager knows goes to a different queue: the hiring manager's inbox. They read it themselves. Referred candidates convert at a far higher rate than cold applicants, and it is one of the few things almost every recruiter will confirm from their own pipeline. The specific ratios you see quoted vary enormously by company and are rarely sourced well enough to repeat as fact, but the direction is not in doubt. This is why twenty minutes spent on a referral is usually worth more than twenty more applications.

The mechanism is straightforward. A hiring manager gets fifty cold applications a week and reads about ten of them. They get one warm introduction a week and read it immediately. If the referrer says 'I know this person and they'd be great for the role', that person is no longer competing in a pool of fifty. They're being considered individually. This changes everything about what happens next - not a phone screen with fifty other people queued, but a conversation where the hiring manager is actually paying attention.

The reason most people don't do this is obvious: it requires reaching out to someone you don't know and asking for help. The typical response is to write something that sounds like begging - 'Can you please refer me?' - which puts the stranger on the spot. A better approach is to ask for something smaller and more specific. Not 'refer me', but 'tell me about this project' or 'what was surprising about this role'. Someone can answer that in two minutes. Someone can decline without feeling guilty. And if the conversation goes well, they can naturally offer a referral themselves.

The structure that gets replies and why length kills even good messages

The messages that work are short - under 120 words - and structured in four parts. First, who you are: one clause that identifies you (your name and what you do). Second, why them: something specific about their work, their company, or the role that proves this isn't a template blast. Third, the one question. Make it specific enough that someone doing the job can answer it in two minutes - not 'Tell me about the team' but 'This role mentions building for iOS; what's been the most surprising technical challenge you've hit on that stack?'. Fourth, an easy out: 'No pressure if you're busy, but I'd love to hear your thoughts if you have a couple of minutes.'

Long outreach reads as a demand for attention rather than a request for two minutes of it. Every sentence added after the core four makes it less likely to be answered. Reply rates fall sharply as length goes up. Anyone who has sent outreach at volume will tell you the short messages get answered and the long ones do not, because a long message asks the reader to decide whether parsing it is worth the time before they know what you want. You're competing for attention against their actual job. Keep it short.

The specificity is what separates a good message from a template blast. Generic proof of non-specificity includes 'I'm interested in your company', 'I'd love to join your team', or 'I admire your culture'. Specific proof includes naming the team, the project, something you actually read. 'I saw your team shipped that iOS app for enterprise clients' proves you looked them up. 'Your engineering blog post on scaling databases answered a question I've had for two years' proves you read their work. The specificity costs five minutes of research and returns hours of higher-quality replies because now you're a person, not a template.

Cold outreach to recruiters follows different rules than outreach to peers

A recruiter's job is to fill roles. They measure success on placements. This changes what you lead with. A recruiter doesn't want to know about your passion for technology or your career journey. They want to know you're a fit for the specific role they're hiring for. Lead with the concrete match: the role you're targeting and two or three things that make you obviously relevant to it. 'I'm interested in your senior engineer opening. I've got eight years of backend Python and Postgres, which matches your stack. My last role was scaling databases at a company with similar scale to yours.'

This is not the approach for a peer or hiring manager. An engineer doesn't think in terms of 'filling pipeline'. They think in terms of 'is this person smart and will they be good to work with'. So the approach is different. Lead with curiosity about the work. 'I've been following your work on machine-learning infrastructure and I'm curious about how you thought through the training pipeline. Can I pick your brain on that?' This is a request someone can say yes to, and if the conversation goes well, they'll naturally offer to refer you.

Sending the wrong message to the wrong person is one of the most common reasons outreach fails. A recruiter message to an engineer says 'This person doesn't understand how I work' and reads as a spammy templated message. An engineer-style message to a recruiter says 'This person doesn't understand this is a business conversation' and reads as unfocused. The structure depends on who you're contacting.

Frequently asked questions

Part of JobStraight — the honest AI job-search platform. Runs in your browser; your data stays on your device.