ChatGPT Prompts for Recruiting Sourcers: 26 Prompts for Boolean, X-Ray Search, InMails, and Pipeline Building

If you're a sourcer, you already know the tell-tale sign of a recruiter who doesn't actually source: they search LinkedIn for "Software Engineer." You don't. You're running five-line Boolean strings through LinkedIn Recruiter, X-raying GitHub for domain signals, and writing InMail that gets double-digit response rates while your peers get 4%.

Below are 26 prompts built specifically for sourcers — not generic HR. Boolean construction, X-ray searches, passive candidate outreach, sourcing reports, diversity sourcing, outbound sequencing, and the internal reporting that keeps your seat at the table. If you want the full 200+ recruiting prompt library, browse the HR & Recruiting category on PromptLab.

Why Sourcers Need Different Prompts Than HR or Closers

Three reasons:

1. The job is a search problem, not a selling problem. Sourcers live in Boolean, X-ray, and query design. Most AI prompt lists aimed at "recruiters" focus on job posts and interview questions. Useless for sourcing work.
2. Outreach volume is high, response windows are short. You're sending 50-200 messages a week. You need prompts that generate variation without sliding into template-speak that candidates spot instantly.
3. Reporting matters. Sourcers who can't quantify their pipeline get cut when hiring slows. Half the prompts below are for making your numbers visible — funnel analytics, sourcing channel ROI, and "why the hiring manager's asks are unrealistic" memos.

Three ground rules before using these prompts:

1. Never paste candidate PII (phone, email, current comp) into free-tier ChatGPT. Use ChatGPT Team/Enterprise or your ATS's built-in AI (Gem, Findem, SeekOut Copilot) for PII-heavy work.
2. Claude Opus 4.7 is better than ChatGPT for long-form InMail sequences and complex Boolean. ChatGPT 5 is faster for quick one-offs.
3. Personalization still wins. AI gives you the frame; the custom first line from the candidate's actual profile is what triples your response rate.

Now the prompts.

Part 1: Boolean String & X-Ray Search Prompts (Prompts 1–6)

Prompt 1: Build a Boolean string from a job description

You are an experienced recruiting sourcer. Build a LinkedIn Recruiter Boolean string for this role:

Role: [title]
Location: [city, remote, or geographic scope]
Must-have skills: [list — e.g., "Kubernetes, Terraform, AWS, production SRE experience"]
Nice-to-have skills: [list]
Years of experience: [range]
Industry/domain: [e.g., fintech, healthtech, B2B SaaS]
Companies to target: [list, if applicable]
Companies to exclude: [list, e.g., current employer, no-poach agreements]

Produce:
- A primary Boolean string (paste-ready for LinkedIn Recruiter)
- An alternate string using different synonyms for the core role
- A narrow variant (fewer results, higher precision)
- A broad variant (more results, for when the primary returns too few)

For each variant, give the expected qualitative tradeoff (precision vs. recall) in one line.
Use proper Boolean syntax with quoted phrases, parens for grouping, and no unsupported operators.

Prompt 2: GitHub X-ray search for engineers

Build a Google X-ray search string to find engineers on GitHub matching this profile:

Role: [e.g., senior backend engineer]
Tech stack: [e.g., Go, PostgreSQL, Kubernetes, gRPC]
Location signal: [optional — city or timezone from profile/README]
Experience signal: [e.g., "contributors to production-grade projects," "10+ followers," "owns repos 
  with 100+ stars"]

Produce:
- A Google X-ray string targeting github.com profiles
- A variant targeting specific repo signals (e.g., contributors to Kubernetes ecosystem projects)
- A variant targeting GitHub users with specific organization affiliations

Include 2-3 follow-up searches I should run to expand the candidate pool from each initial result.

Prompt 3: X-ray for LinkedIn profiles (public web)

Build a Google X-ray string to find LinkedIn profiles for [role title] in [location] with [specific 
skill or company experience].

Requirements:
- Target site:linkedin.com/in/
- Include specific skill keywords
- Include experience-level signals (senior, staff, principal, etc.)
- Exclude pattern: [companies to skip, job titles to exclude]

Produce:
- The X-ray string
- 2-3 refinement iterations if the first returns too many or too few results
- Notes on how to de-duplicate from my existing LinkedIn Recruiter searches

Prompt 4: Advanced LinkedIn Recruiter Boolean with nested logic

I need a complex LinkedIn Recruiter search for a hybrid role:

Role concept: [e.g., "someone who has moved from IC engineering into product management in the last 
3 years, with B2B SaaS background"]

Target signals:
- Current title variations
- Prior title variations (what they had 2-3 years ago)
- Company size signal (Series B-D OR 100-500 employees)
- Industry signal
- Education signal if relevant

Produce a Boolean string that captures this cross-career-stage pattern without blowing out to 
50,000 results.

Include a fallback approach if Boolean can't capture the career-movement pattern precisely (e.g., 
what manual filters to layer on the raw result set).

Prompt 5: Niche Boolean for rare profiles (diversity sourcing)

Build a Boolean search strategy for [underrepresented group — e.g., "women in senior engineering 
leadership," "Black product designers," "Veterans transitioning into tech sales"].

Requirements:
- Lead with professional signals (certifications, affiliation memberships, conference speaker 
  signals) — not demographic assumptions based on names or photos
- Include alumni networks of relevant organizations (NSBE, Society of Women Engineers, VetsInTech, 
  Lesbians Who Tech, AfroTech)
- Layer in role-specific skill requirements

Produce:
- 3 complementary Boolean strings tapping different professional signals
- A note on appropriate language and outreach framing
- A note on what NOT to do (avoiding discriminatory filtering)

Be thoughtful — the goal is widening the top of the funnel, not targeting demographics directly.

Prompt 6: Boolean string for hard-to-find hybrid roles

I need to find candidates for a very specific hybrid role: [describe the rare combination — e.g., 
"solutions engineer who has also done customer success," "SRE with security background," "marketing 
ops person with strong SQL skills"].

Produce:
- A Boolean string that identifies candidates with BOTH skill sets
- A separate string for each component role, so I can source from both funnels and cross-filter later
- 3-5 signals in profiles that indicate they actually have both skills (not just listed them)
- A plan for how to verify the hybrid claim in the screening conversation

Part 2: Candidate Outreach Prompts (Prompts 7–13)

Prompt 7: First-touch LinkedIn InMail (personalized)

Write a first-touch LinkedIn InMail for a passive candidate.

Role: [title, company, location, remote policy]
Compensation range: [if disclosable]
Candidate details (paste their LinkedIn summary or key facts): [paste]

Write an InMail that:
- Opens with a specific reference to something in their profile (a project, a job, a skill, a recent 
  post) — NOT generic "I came across your profile"
- Mentions the role by title and company (don't be cagey)
- Names 2-3 specific reasons they'd be a fit (tied to their profile)
- States why NOW is the right time to explore (growth, funding, mission, team expansion)
- Closes with a low-friction ask (15-minute chat, reply yes/no, link to JD)

Under 120 words. No buzzwords ("rockstar," "ninja"), no flattery ("your amazing background").

Prompt 8: Follow-up InMail (no response after 5 days)

Write a second-touch InMail follow-up to a candidate who didn't respond to the first message.

Original InMail context: [what I said, when]
Candidate profile: [paste key facts]
New angle to introduce: [one new piece of info — a team announcement, a customer case study, a 
  specific technical problem they'd be working on]

The follow-up must:
- NOT repeat the pitch from the first message
- Introduce the new angle as the reason for reaching out again
- Be shorter than the first InMail (under 80 words)
- End with a specific, low-friction ask (reply with "interested" or "not right now")

Tone: respectful, not persistent to the point of annoying.

Prompt 9: Breakup InMail (final touch)

Write a breakup InMail — the final message after no response to two previous outreach attempts.

Candidate: [name, role target, what made me think they were a fit]

The message should:
- Acknowledge this is my last outreach on this opportunity
- Not guilt-trip or scold
- Leave the door open for future roles (invite them to tell me what they'd consider)
- Be under 70 words

Sometimes breakup messages get the best responses because they show respect for the candidate's time.

Prompt 10: Email outreach (when no InMail credit)

Write a cold email to a passive candidate you found through X-ray search.

Role: [title, company, location, key comp/benefits]
Candidate email source: [e.g., GitHub profile, public company site, LinkedIn email field if 1st 
  connection]

The email must:
- Have a subject line under 50 characters that references something specific (their repo, their 
  company, their recent work)
- Open with a personalized hook from their public profile
- Explain the role briefly (3-4 lines)
- Close with a specific, low-friction ask

Under 150 words total. No marketing language. Written like a peer, not a recruiter.

Compliance note: if I'm outreaching EU candidates, add GDPR-compliant language about where I got 
their contact info and their right to opt out.

Prompt 11: Warm referral intro request

Write an email asking an existing employee for an introduction to a candidate I want to source.

Target candidate: [name, current company, role]
Employee I'm asking: [name, their relationship to the target — e.g., "they worked together at 
  CompanyX 2019-2022"]

The email should:
- Explain specifically why I'm targeting this candidate (fit for which role, why they're a great match)
- Make the intro easy: a short blurb the employee can forward or adapt
- Acknowledge their time (don't pester if they're busy)
- Offer something in return (a referral bonus, a visible thank-you, their pick of a company swag item)

Under 150 words. Grateful without being obsequious.

Prompt 12: Outreach to a candidate at a no-poach company

Write a careful InMail to a candidate at a company where we have a known or implied no-poach 
restriction.

Our company: [name, industry]
Their company: [name, relationship to ours]
Role we're filling: [title]

The message should:
- NOT mention the other company by name
- NOT suggest we'd target them specifically because of their current company
- Frame the outreach around their visible work or thought leadership (something they posted publicly, 
  a talk they gave, etc.)
- Make the role opportunity attractive on its own merit

Be careful — legal sensitivity here. Written conservatively.

Prompt 13: Outreach to a boomerang candidate (former employee)

Write an InMail or email to a former employee we want to re-recruit.

Candidate: [name, role when they left, when they left, where they went]
Our context: [what's changed at our company since — team, product, leadership, culture]
Role we want them for: [title, how it differs from their prior role]

The message must:
- Acknowledge they left (don't ignore the history)
- Reference specifically what's different now
- Respect that they chose to leave — don't assume they want to come back
- Make the case for a conversation, not a commitment

Under 180 words. Warm, specific, no groveling.

Part 3: Screening & Pipeline Prompts (Prompts 14–18)

Prompt 14: Initial screening call agenda

Write an initial sourcer screening call agenda for a [role title] opportunity.

Role context: [brief — skills, level, comp range, location, growth opportunity]
Candidate profile: [what their LinkedIn shows]

The agenda should cover:
- Intro (3 min): who I am, why I reached out, context on the company
- Their situation (5 min): what they're doing now, what they'd want next, what's motivating them
- Role fit (10 min): walk through role highlights, their core questions, alignment check
- Compensation (4 min): their comp expectations, our range, any deal-breakers
- Process (3 min): what happens next if both sides interested

Total call: 25 minutes. Written for the sourcer to lead the call without scripting every word.

Prompt 15: Candidate submission write-up to hiring manager

Write a candidate submission memo to the hiring manager.

Candidate: [name, current role, location]
Core background: [5-year summary of experience, titles, relevant skills]
Why they're a match: [3-4 specific fit reasons]
Screening takeaways: [what I learned in the screen that isn't on the resume]
Their questions/concerns: [what they asked about, what might need addressing]
Comp expectations: [their range, how it matches ours]
Timeline: [their availability for next step]

The memo must:
- Lead with a 2-line summary: "Recommend for first round — strong technical match, motivated by 
  [driver], comp aligned."
- Attach or reference their resume / LinkedIn
- Flag any concerns honestly (tenure, comp gap, timing)
- Make it easy for the hiring manager to say yes/no in 60 seconds

Format: structured memo, scannable. Not a sales pitch.

Prompt 16: Rejection message to candidate after screen

Write a rejection message to a candidate after an initial screening call.

Context:
- Why we're passing: [specific reason — skills, level, comp, timing]
- Their strengths: [what was good about them]
- Possibility of future roles: [yes/no — and if yes, which]

The message must:
- Be honest about the pass (without giving detailed feedback that could be used against us legally)
- Thank them for their time specifically
- Leave the door open for future roles if genuine
- NOT include vague "we'll keep your resume on file" unless I actually will

Under 120 words. Respectful, direct.

Prompt 17: Pipeline status update to hiring manager (weekly)

Generate a weekly sourcing pipeline status update for a hiring manager.

Role: [title]
Open since: [date]
Target first-round count: [X]
Current pipeline:
- Outreach volume this week: [# sent, # responded, response %]
- In screen: [count]
- In first-round interview: [count]
- Advanced rounds: [count]
- Offers out: [count]
- Declines: [count with reasons]

Produce a 1-page update with:
- Headline numbers
- Insights on response rates by channel / Boolean / message variant
- 3 candidates worth highlighting (why)
- Blockers or asks (e.g., comp adjustment, JD rewrite, hiring manager time to interview)
- Next week's plan

Short and action-oriented. Written for a hiring manager who has 2 minutes.

Prompt 18: Sourcing funnel analysis

Analyze my sourcing funnel data for a [role] search.

Inputs:
- Candidates contacted: [#]
- Responded: [#]
- Screened: [#]
- Submitted to HM: [#]
- First-round interviews: [#]
- Advanced rounds: [#]
- Offers: [#]
- Hires: [#]
- Channels used: [LinkedIn Recruiter, X-ray, employee referrals, ATS re-engagement, events]
- Timeline: [search duration]

Produce:
- Funnel conversion rates at each stage
- Comparison to industry benchmarks (acknowledge these vary; use SourcingPioneer / LinkedIn / Lever 
  published benchmarks where applicable)
- Identification of the weakest conversion stage (where are we losing candidates)
- 3 specific recommendations to improve the biggest drop
- One experiment to run next week

Framed as a data-driven sourcing postmortem.

Part 4: Reporting & Internal Communication Prompts (Prompts 19–23)

Prompt 19: Monthly sourcing KPI report to recruiting leadership

Write a monthly sourcing report for recruiting leadership.

Month: [month]
Roles I sourced for: [list]
Key metrics:
- Outreach sent: [#]
- Responses: [#, %]
- Screens completed: [#]
- Submissions to hiring managers: [#]
- Submit-to-first-round conversion: [%]
- First-round to offer conversion: [%]
- Hires attributed to sourcing: [#]
- Avg time from first contact to offer: [days]

The report must include:
- Executive summary (top 3 takeaways)
- Performance against targets
- Channel performance comparison (LinkedIn Recruiter vs. X-ray vs. referrals)
- Pipeline health (hot/warm/cold counts)
- Process improvements made this month
- Next month's priorities

Visual suggestions: funnel chart, channel comparison bar chart, trend line.

Prompt 20: "Why this role isn't filling" memo to hiring manager

Write a diplomatic memo to a hiring manager explaining why their open role isn't filling after 
[X weeks].

Evidence:
- Outreach volume: [sufficient vs. limited]
- Response rate: [vs. benchmark]
- Interview pass-through rate at each stage: [numbers]
- Candidate feedback on decline: [common themes — comp, location, role scope, company stage]
- Market data: [talent supply, competing offers, comp benchmarks]

The memo must:
- Open with data, not blame
- Identify the 2-3 specific constraints that are causing the slowdown
- Propose concrete changes (JD rewrite, comp adjustment, location flexibility, interview process 
  simplification)
- Frame it as collaboration, not "your role is broken"
- Close with next steps and accountability

Professional, direct, data-supported.

Prompt 21: Channel ROI analysis for sourcing tools

Analyze the ROI of our sourcing tools and suggest reallocation.

Tools and costs:
- LinkedIn Recruiter: $[cost], seats: [#]
- SeekOut / Gem / hireEZ: $[cost]
- Findem: $[cost]
- Paid InMail credits: $[cost]
- Job ads (LinkedIn, Indeed, etc.): $[cost]
- Referral bonuses paid: $[cost]

Outputs by channel:
- Hires attributed: [# per channel]
- Cost per hire by channel: [$]
- Time to fill by channel: [days]
- Candidate quality rating by channel: [subjective]

Produce:
- Cost-per-hire table ranking channels
- Recommendation: keep, cut, or expand each channel
- Suggested next-quarter budget allocation
- One tool worth piloting that we're not using

Framed as a business case for recruiting leadership or finance.

Prompt 22: Sourcer performance self-review

Help me write my quarterly performance self-review as a sourcer.

Q [X] achievements:
- Roles supported: [list with level]
- Hires attributed: [#, with candidate summaries]
- Pipeline built: [# active candidates delivered to hiring managers]
- Process improvements I led: [list]
- Tools or workflows I built: [list]
- Diversity sourcing outcomes: [specifics]
- Mentorship / team contributions: [specifics]

Challenges and learnings:
- [What didn't work and what I learned]

Goals for next quarter:
- [list]

Produce a 1-page self-review with:
- Opening summary paragraph
- Sections for achievements, challenges, goals, and professional development
- Specific numbers, not vague language
- Evidence-based framing

For a manager who reads 20 of these. Make mine stand out without sounding braggy.

Prompt 23: Diversity sourcing strategy memo

Write a diversity sourcing strategy memo for [role type, team] to present to our DEI lead and 
recruiting leadership.

Current state:
- Applicant pool diversity data: [if available]
- Pipeline diversity data: [if available]
- Historical hiring demographics for similar roles: [if available]

Proposed strategy:
- Specific sourcing channels to expand (affinity groups, HBCUs / MSIs, Lesbians Who Tech, Women Who 
  Code, NSBE, SHPE, etc.)
- Boolean and X-ray refinements to widen funnel
- Process changes (blinded resume review, structured interviews, debiased rubrics)
- Outreach language adjustments
- Target metrics and timeline
- Partners / budget needed

Tone: evidence-based and pragmatic. Not performative. This is a process improvement memo, not a 
manifesto.

Part 5: Specialized Sourcer Prompts (Prompts 24–26)

Prompt 24: Technical role JD decomposition

I have a technical JD that was written by the hiring manager. It's vague and has a massive 
"must-have" list. Help me decompose it into a sourceable search.

JD: [paste]

Produce:
- The 3-5 actual must-have signals (not the 25 on the list)
- The 3-5 nice-to-haves that we should be flexible on
- Title variations this candidate might have (current + recent past)
- Company types where this candidate likely works
- Red flags to avoid in the resume (mid-career pivots, too-senior-for-this-role, etc.)
- Questions to ask the hiring manager to clarify
- A draft Boolean string based on the decomposed must-haves

Written so I can send the decomposition back to the hiring manager and realign expectations.

Prompt 25: Competitive intel on passive candidates (public signal only)

I want to build a candidate target list based on public signals only. No PII scraping.

Target profile: [role, level, company stage]
Public signals to leverage:
- GitHub profile activity (contributions, repos, stars received)
- Conference speaker lineups (list relevant conferences)
- Medium / Substack / personal blog authorship
- LinkedIn thought leadership (public posts with engagement)
- Open source committer status to specific projects
- Podcast guest appearances

Produce:
- A search strategy for each public signal
- Example X-ray queries
- A prioritization rubric (which signals indicate best fit)
- Notes on ethical use (respect the public context — don't treat thought leadership as an invitation 
  to spam)

Prompt 26: Handoff doc when sourcing role is paused

Write a handoff document for a sourcing search that's being paused.

Role: [title, level]
Why paused: [hiring freeze / headcount shift / HM change / comp reset]
Work completed:
- Boolean strings built and refined: [link or paste]
- Candidates contacted: [#, with breakdown by channel]
- Candidates in active pipeline at pause: [list with status]
- Candidates in "warm/nurture" pool: [list]
- Intel gathered on compensation, competition, market: [summary]
- Recommended changes if role reopens: [list]

The doc must:
- Capture institutional knowledge so the search doesn't restart from zero
- Include specific contacts to re-engage first when the search resumes
- Note any commitments made to candidates (follow-up, timeline expectations)
- Be usable 6 months later by someone who wasn't involved

Framed as: future me (or a teammate) will thank present me.

ChatGPT vs. Claude vs. Specialized Sourcing AI

Here's the practical breakdown for sourcing workflows:

For a sourcer making $70-100K, paying $20/month each for ChatGPT Plus and Claude Pro is a no-brainer. If your company pays for Gem, Findem, or a similar tool, use that for outreach at scale and keep the general-purpose AI for one-offs, analysis, and reporting.

More specific prompt variants for technical sourcing, executive search, and global roles live in the HR & Recruiting library on PromptLab.

Frequently Asked Questions

Q: Can ChatGPT replace a sourcer? No. It replaces the 20% of sourcing work that's mechanical (Boolean construction, first-draft outreach, reporting formats). The 80% that's judgment — who to approach, how to read a profile, when to push on a JD — still requires a human with taste and experience.

Q: Will candidates know I'm using AI to write outreach? If you copy-paste the AI output raw, yes. Candidates now see 50+ recruiter messages a month and AI tells are obvious (generic compliments, overly structured paragraphs, no specific references). The fix is personalizing the first 2 lines with something from their actual profile. That 60 seconds of editing triples response rates.

Q: Is it legal to use AI to filter candidates? Using AI to source or screen requires careful implementation under Title VII, ADA, OFCCP regs, and emerging state laws (NYC LL 144 requires bias audits for AI hiring tools). Use AI for sourcing (finding) and outreach. Use AI cautiously for screening. Involve your legal and DEI teams before deploying AI as a decision-making filter.

Q: What's the best AI tool specifically for sourcers? Depends on scale. Solo sourcer: ChatGPT Plus + Claude Pro ($40/month total). In-house team at a growth-stage company: Gem or Findem layered on ATS. Large enterprise: SeekOut Copilot or Eightfold for talent intelligence combined with ChatGPT/Claude for drafting.

Q: How do I keep my outreach from getting flagged as spam? Volume + homogeneity = spam. Vary your message structure, subject lines, and opening hooks. LinkedIn and email filters look for template patterns. Use AI to generate 4-5 variants per campaign and alternate them.

Q: Can AI generate diverse candidate pools? AI can help widen the top of funnel by suggesting channels and signals, but it doesn't fix underlying sourcing bias. Review your outreach data monthly. If your funnel looks demographically homogeneous, the fix is sourcing channel expansion and JD rewrites, not more AI.

Q: Is "AI-generated" a deal-breaker for candidates? Increasingly yes for senior candidates. Executive candidates especially expect personalized, thoughtful outreach. Use AI to scale volume for junior and mid roles; hand-craft for senior and executive searches.

Related Prompt Libraries for Sourcers and Recruiters

• HR & Recruiting prompts — sourcing, interviewing, offers, onboarding
• Sales & Outreach prompts — cold messaging, follow-ups, sequences
• Career & Job Search prompts — resume writing, interview prep (for your candidates)
• Marketing prompts — employer branding, careers page content
• Content Creation prompts — team blog posts, recruiting videos
• Business Automation prompts — ATS workflows, Gem/HubSpot automations
• Productivity prompts — pipeline reviews, reporting templates
• Legal & Contracts prompts — offer letter review, contractor agreements
• Model-Specific prompts — Claude and Gemini variants for sourcing work
• Education prompts — team training on sourcing tools

Browse the full PromptLab library for 40,000+ prompts, including the deepest recruiting-specific collection available.