LinkedIn Recruiter for Talent Sourcing

Primary intent: give TA teams direct sourcing access to LinkedIn's full member database via Boolean and AI-powered search filters, InMail credits, Pipeline projects, and ATS push-back, as of early 2026. LinkedIn Recruiter has been the default enterprise sourcing seat since around 2011. The 2024 update added AI-assisted search (convert a job description into a Boolean string), AI InMail drafting (generate a first draft from a profile), and Recommended matches surfaced automatically from saved searches.

The platform works best when you treat it as a structured workflow, not an open search engine. Build a tight Boolean string (or paste the JD into the AI search box and then verify the output), work a saved search with daily alerts, and push qualified profiles into a Pipeline project before you message anyone. That sequence gives you an auditable list, prevents double-messaging across team seats, and keeps InMail credits targeted at your strongest shortlist.

If your question today is which sourcing tool should we buy, read How it compares to similar tools first, then follow Practical steps to run a real first session before you benchmark reply rates across seats. The comparison table covers Recruiter Lite, LinkedIn Sales Navigator, HireEZ, and SeekOut so you can match the tool to the req type.

Pair LinkedIn Recruiter with ChatGPT for fast outreach draft iteration or Claude for longer profile-to-brief passes when you are presenting a slate. For automated follow-up that stays off-platform and compliant with LinkedIn usage policies, see n8n for recruiting automation: n8n workflows typically handle post-export email sequences, not in-platform sends.

If you are deciding whether LinkedIn Recruiter is the right seat for your team, match your most common req type against the table before committing.

Where to start (opinionated): if you are sourcing knowledge-worker roles at volume and your ATS supports RSC, LinkedIn Recruiter full-seat is the defensible default. Solo recruiter on a tight budget with fewer than 20 active reqs? Recruiter Lite covers the core workflow at a fraction of the cost. Sourcing engineering roles where diversity data and GitHub signal matter? Pilot SeekOut alongside Lite before buying a full seat. Only need headcount and market mapping, not outreach? Sales Navigator at a lower price point may be enough.

A 15-minute first sourcing session (no ATS integration required)

1. Open a new Project in LinkedIn Recruiter: give it the req ID and role title so two seats on your team cannot accidentally search the same pool simultaneously.

2. Build your Boolean string first. Either write it manually (required: target title OR synonyms, company type if relevant, location radius or remote flag) or paste the JD body into the AI-assisted search box and review the generated string before running it. Edit the output: AI-generated strings often include overly broad skill keywords that inflate the result set from dozens to thousands.

3. Run the search, then apply the "Open to work" or "Open to new opportunities" spotlight filter. This narrows to members who have signalled openness without publicly broadcasting it, which raises reply rates.

4. Save the search with a daily alert so new-to-database profiles surface tomorrow without re-running the string manually.

5. Shortlist 10 to 15 profiles into the Pipeline project. Do not InMail yet. Read each profile: note one specific detail per person (recent project, unusual skill pairing, company milestone) to reference in the message.

6. Draft InMails in batches: use the AI draft as a starting point, add the profile-specific detail you noted, then trim to under 150 words. Keep the subject line to 6 words or fewer. Send in batches of 10 per day if the credit budget allows; this lets you measure reply rate before sending the rest of the list.

ATS handoff via Recruiter System Connect

If your ATS supports RSC (Greenhouse, Workday, Lever, iCIMS, SmartRecruiters, and others), set up the field mapping before your first push:

• Confirm which profile fields transfer: name, headline, current company, location, LinkedIn URL are standard. Custom fields are ATS-specific.
• Verify the ATS creates a net-new candidate record rather than a duplicate when you push.
• Stage mapping in RSC is usually manual per pipeline; configure it once per req type and document it for the team.

If your ATS does not yet support RSC, export a CSV from the Pipeline project and import manually. Flag this to your ATS admin if you are doing it repeatedly: it is a clear argument for RSC setup or a migration conversation.

Second prompt: InMail personalisation check (paste into ChatGPT or Claude)

Use this after you draft a batch of InMails to catch generic filler before it ships.

You are a recruiting editor reviewing outreach messages. For each InMail below, identify:
1. Any claim about the candidate that is NOT sourced from the profile summary I pasted.
2. Any line that could apply to any candidate on any list (generic filler).
3. One suggested edit to make the opening line more specific to this person.

Do not rewrite the full message. List findings only.

CANDIDATE PROFILE SUMMARY (paste only what you are allowed to share):
[paste]

INMAIL DRAFT:
[paste]