Outbound Recruiting: How to Reach Candidates Who Aren't Applying

Decide when to go outbound, build a list from the job's real requirements, and write first messages busy people answer

woman with red hair in an interview with another woman at a large table

Outbound recruiting means a recruiter identifies qualified people who haven't applied and reaches out to start a conversation about a specific role. It's how you fill a role when the right people aren't applying, because it reaches people who would never see your posting.

It takes more work per candidate than waiting for applications. The effort pays off when each message gives the person a clear reason they were chosen, which is what the rest of this workflow is built around.

Key takeaways

  • Go outbound when inbound applicants keep missing the same core requirements.
  • Build your list from the job's real requirements, not from job titles alone.
  • Open every first message with one specific, verifiable reason this person fits.
  • Follow up with something new each time, honor every opt-out, and know when to stop.

Inbound vs outbound recruiting: what's the difference?

Inbound recruiting waits for candidates to come to you, while outbound recruiting has you go to them. Inbound covers job postings, your careers page, and referrals that arrive on their own. Outbound means you pick out people who haven't applied and contact them yourself. Most desks need both, so the useful question is which one this role needs right now.

ApproachHow candidates arriveBest forWatch for
InboundThey find the posting and applyCommon roles with a wide applicant poolVolume that misses the core requirements
OutboundYou find them and reach out firstSpecialized roles and people who aren't lookingGeneric messages that waste a candidate's time

When outbound recruiting makes sense

Go outbound when inbound can't give you the people the role needs. That often happens when the role is specialized, when applicants keep missing the same core requirements, or when the people you want are employed and not looking. Outbound recruitment takes more of your time per candidate, so save it for roles where inbound falls short.

The U.S. Bureau of Labor Statistics (BLS) tracks job changes through its Job Openings and Labor Turnover Survey (JOLTS). Its August 2026 release reported quits unchanged at 3.1 million, with openings little changed. That's one month of data, but it's a fair reminder that strong candidates aren't necessarily on the move.

Thin applicant pools are common as well. The Society for Human Resource Management (SHRM) reported in its 2025 Talent Trends release that 51% of U.S. organizations filling full-time roles saw low applicant numbers.

Consider an agency recruiter filling a senior data engineer role for a healthcare client. The applicants have solid general data experience, but few have built on the client's cloud platform or handled regulated health data. That combination is the whole point of the hire, so reposting the job won't fix it.

Build your list from the brief, not the title

Start your list from the job's real requirements, because titles alone pull in the wrong people. A senior data engineer at one company may do very different work than one at another. Good outbound sourcing breaks the brief into search terms instead: skills, credentials, project types, and the kind of data a person has handled.

A clear search-ready job description makes this step faster. In the healthcare search, the must-haves become terms for the cloud platform, for migration work, and for health data privacy. You can then combine those terms with Boolean search operators and leave nice-to-haves out of the first pass so the list doesn't shrink too early.

People you already know belong on the list as well. Past finalists for similar roles have been vetted once and may be ready to move now. Add them, but keep searching past them so the list reflects the role and not only your history.

Research one specific reason before you write

Before you write, find one specific, verifiable reason this person fits the role. It might be a project they've described publicly, a stack they list, or a credential they hold. One real detail does more than a paragraph of praise, because it shows you read their background.

Stick to what the person has shared about their own work. Don't guess at their situation, such as whether they're unhappy or ready to leave. A wrong guess reads as presumptuous, and a right one can feel intrusive.

For the data engineer search, a good reason might be that the candidate wrote about moving claims data to the cloud. That pairing of cloud work and regulated health data is what the applicants lacked, so it belongs in your first line.

Check the match before you start writing

A structured search can show you why each person matched, which hands you the opening line of your message.

Turn your brief into a structured search

Book a demo

Candidate outreach: how to write a first message people answer

A first message that earns a reply has three parts: why you chose them, what about the role matters to someone like them, and a small ask. The second part isn't a perks list but the thing this kind of person cares about, such as the problem they'd own. The ask should be a short call, not a resume or a commitment.

Keep the message short enough to read on a phone, and leave room to say no. For the healthcare search, a first message might read like this:

Hi [Name],

I read your write-up on moving claims data pipelines to the cloud. I'm recruiting a senior data engineer for a healthcare company that needs that exact mix of cloud migration work and privacy-aware data handling.

The team is rebuilding how patient data moves between systems, and this person would own that design. Would you be open to a short call next week to hear more? If the timing's wrong, tell me and I won't keep following up.

[Your Name]

The message leaves out a compensation pitch, a list of perks, and any pressure to decide. Its last line gives the candidate a polite way out, and a quick no is more useful to you than silence.

Follow up with something new, then stop

Follow up a few times with space between messages, and make each one add something the first didn't. A second note might share a detail about the team or the data problem. A later one might move to a phone call, if you have the person's number and permission to use it. Then stop, because more messages after silence won't change the answer.

A reply of "not now" is a lead, not a rejection. Ask when they'd like to hear from you again, note it, and add them to your talent pipeline. In the data engineer search, someone who can't move this quarter may be your first call when the client opens a second role.

Choosing channels: email, phone, text, and professional networks

Pick the channel that fits the person and the contact details you have permission to use. Email gives you room for your specific reason and lets the candidate answer on their own time. Phone works well as a second touch, and cold calling needs its own preparation. Professional networks help when you don't have direct contact details, though messages there compete with a lot of noise.

Texting carries specific federal rules. The Federal Communications Commission (FCC) set a 10-business-day limit in a 2024 order for honoring requests to stop autodialed calls and texts. People can revoke consent in any reasonable way that makes their wish clear. The rule covers autodialed or prerecorded calls and autodialed texts, and whether your tool counts is a legal question.

Whatever the channel, treat any opt-out as final and record it where your whole team can see it.

Keep your outreach lists fair

Target people on job-related criteria, and widen your list past the people you already know. Federal guidance from the U.S. Equal Employment Opportunity Commission (EEOC) says it's illegal to recruit in ways that discriminate by race, sex, or other protected traits. It notes that relying on word-of-mouth recruiting can violate the law when new hires end up drawn almost entirely from one group.

For the data engineer role, that means searching on the cloud and privacy experience the client needs. Don't limit the list to the companies your last few placements came from.

How to measure outbound recruiting results

Measure what happens after each message so you know what to change. Track reply rate, positive reply rate, screens booked, and placements, broken out by message version and by channel. If you already track sourcing metrics, add these to the same report.

Judge channels by what they produce, not by how popular they are. U.S. HR professionals in SHRM's 2026 Talent Trends research used social media more than any other recruiting strategy but ranked it ninth for filling roles.

In the healthcare search, you might find that messages leading with privacy work draw more positive replies than messages leading with the cloud platform. That tells you what to open with the next time the client needs a similar hire.

Check your reason to reach out before you hit send

Outbound recruiting works when each message shows the candidate you did the homework. Start from the role's real requirements, find one detail that connects this person to the work, and ask for something small. Follow up with something new, respect every no, and track results by message and channel so you know what to repeat. Before your next round of messages goes out, reread each opening line and make sure it names something specific to that person.

Reach candidates through details they chose to share

Book a demo

Frequently asked questions

Is outbound recruiting the same as sourcing?

Not quite. Candidate sourcing is the work of finding people who might fit a role. Outbound recruiting includes that step and adds the outreach, follow-up, and handoff to a screen.

Should agency recruiters name the client in a first message?

It depends on your agreement with the client and whether the search is confidential. If you can't name the company, describe it specifically, such as its industry or the problem the team is solving.

About the author

Mihailo Bozic
Mihailo Bozic

Founder & CEO @ Rotto

Founder & CEO of Rotto, building tools that help tech recruiters source better candidates, faster.

Related articles

Rotto

Built for recruiters who work from a brief, not a boolean.

rotto.com