Recruiter Outreach Examples Candidates Answer

Strong candidates get a steady stream of recruiter messages, and most of them look identical: a job title, a buzzword-heavy company blurb, and "let me know if you're open to a chat." The messages that get answered do something different. They show the recruiter looked at the person's work and respect their time. These examples show how.

What candidates say they dislike

• Obvious mass messages. No evidence you looked at their profile or understood their level.
• Wrong-fit roles. Pitching a junior role to a staff engineer, or a frontend job to a data scientist.
• Hidden details. No location, no remote policy, no seniority, no compensation range. If you can share a range, do.
• Fake urgency. "Great opportunity, act fast!" signals desperation, not substance.

The anatomy of a good recruiter message

1. A specific observation about their work. A project, repo, talk, paper or portfolio piece.
2. Why it connects to your role. One sentence tying their work to what the team is building.
3. The essentials up front. Role, level, location or remote policy, and whether you can share a salary range.
4. A low-friction next step. Offer to send details first, or ask a quick question.

Example 1: Software engineer

Hi Priya, I read your write-up on migrating your team's job queue from cron to a workflow engine, especially the part about handling partial failures. We're building something similar at [company], where our payments pipeline has the same failure modes. We're hiring a senior backend engineer (remote in US time zones, [range] base). Happy to send the details first if you'd rather read than talk. Would that be useful?

Why it works: it names the specific content, connects it to a real problem, and gives the logistics immediately.

Example 2: Designer

Hi Marcus, the case study on your onboarding redesign for [product] stuck with me, particularly how you cut the setup steps by moving permissions to later in the flow. We're a small team building [product type] and design is the biggest lever we have right now. We're looking for a product designer who can own flows end to end. Is a quick look at the role worth your time?

Avoid inventing numbers about their work. Reference only what you can see in their portfolio.

Example 3: Senior or executive hire

Hi Elena, I've followed [company]'s growth in [market] and your talk on scaling support without scaling headcount. We're a [stage] company looking for our first VP of Customer Success. I'd rather not send a generic job description. Would you be open to a 15-minute conversation about whether it's even interesting to you? If it's not, I'd still value your view on what the role should look like.

Senior candidates respond to being treated as advisors, not applicants.

Example 4: Follow-up to a non-reply

Hi Priya, I'll keep this short. If the timing isn't right, no problem. If you'd like the role details and comp range first, I'm happy to send them with no call needed. Either way, thanks for the writing on workflow systems.

This follows the pacing in our follow-up sequence guide.

Channel choices

Email is better for detail and for people who guard their LinkedIn inbox. LinkedIn is better for reaching someone you can't find an address for. For engineers, a note referencing a specific repository or issue can be more credible than anything on LinkedIn. We've collected adaptable messages in LinkedIn cold message templates. If you only have a name and company, see how to find someone's email or handle.

Do the homework faster

The hard part of every example above is the first sentence, which requires reading someone's work. Avian speeds that up. Paste a candidate's GitHub username, LinkedIn URL or name and it summarizes what they work on and writes three personalized message variants you can edit. Verify the details before sending, since public profiles can be incomplete.

Sign up free and try it on your next three candidates.