Email Subject Lines for Recruiters — Free AI Generator
Table of Contents
Recruiters reaching out to passive candidates have a unique problem: the candidate is happy in their current job, gets 5-10 LinkedIn InMails per week, and has trained themselves to ignore recruiter outreach. Generic subject lines like "Exciting opportunity at [Company]" go straight to archive.
Our generator produces recruiter subject lines that get past the candidate's mental filter. Pick the role you are sourcing for, describe the candidate's background, and get 10 options that feel personal and respectful of the candidate's time. No signup, runs in your browser.
Why Sourcing Passive Candidates Is Harder Than Ever
Software engineers, product managers, and data scientists in 2026 receive 5-15 recruiter messages per week. They have learned to filter:
- Generic subjects = archive. "Exciting opportunity at [Company]" or "Senior Engineer role" gets ignored.
- Vague compensation = archive. Without a salary range, the candidate assumes the offer is below market.
- Boring company names = lower priority. Candidates prioritize messages from companies they recognize and admire.
- InMail vs email. Direct email tends to outperform LinkedIn InMail because it feels more intentional (the recruiter had to find their email).
- Mass-send patterns. Anything that looks like it could have been sent to 100 people gets archived.
The recruiter who breaks through is the one who treats each candidate like an individual. The subject line is the first signal of that approach.
Recruiter Subject Line Patterns That Get Replies
The personal observation: "Your work on [specific project] caught my attention" — shows you researched.
The role specificity: "Senior [Role] at [Recognizable Company]" — instantly clear what the role is.
The compensation tease: "[Role] role at [Company] - $200K-280K" — leads with the most interesting fact for most candidates.
The location mention: "[Role] in [City] (remote-friendly)" — answers the geography question upfront.
The team size: "[Role] joining a [Number]-person team at [Company]" — answers a key question for candidates evaluating fit.
The shared connection: "[Mutual contact] suggested I reach out about a [Role] opening" — uses social proof.
The technical specificity: "[Specific tech] role at [Company] - quick question" — answers the tech stack question.
The casual professional: "Worth a 15-minute chat? [Role] at [Company]" — explicit, low-pressure ask.
How to Use the Generator for Sourcing
- Open the generator in your browser.
- Describe the role — title, company, salary range, location, team size, key tech stack, what makes the role interesting.
- Add candidate context — what made you reach out to this specific candidate (their LinkedIn, their GitHub, their portfolio, a mutual contact).
- Pick email type: Cold Outreach.
- Pick a style — Personal for warm sourcing, Benefit for compensation-focused roles, Question for engagement-focused, Curiosity for dream-job pitches.
- Click Generate 10 Subject Lines.
- Pick the strongest 1 for direct outreach, or 2-3 if you are A/B testing in a sequencer like Gem or hireEZ.
- Use it as the email subject in your sourcing tool.
Works With Every Sourcing Platform
The generator produces text. Drop the subject line into any sourcing platform:
- Gem — most popular sourcing tool, supports custom subject lines and A/B testing.
- hireEZ — sourcing automation platform, accepts custom email subjects.
- SeekOut — sourcing intelligence tool, supports custom outreach.
- LinkedIn Recruiter — InMails support custom subjects, though LinkedIn limits the message length.
- Lever (CRM) — supports custom email templates.
- Greenhouse Sourcing — supports email outreach with custom subjects.
- Ashby Recruiting CRM — full sourcing automation with custom subjects.
- Outreach (sales tool, used by some recruiters) — supports A/B testing of subject lines.
- Direct Gmail/Outlook — for one-off direct outreach to specific candidates.
The generator is platform-agnostic.
Recruiter Subject Line Mistakes That Tank Open Rates
"Exciting opportunity" — every recruiter uses this. Candidates are immune.
Hiding the company name. Sourcing for a "stealth startup" without naming it makes candidates assume the company is not impressive.
Hiding the salary. "Competitive compensation" reads as below-market. Lead with the range.
Generic personalization. "Hi [first_name]" with the brackets visible signals broken automation.
Excessive flattery. "Your incredible background blew us away" is over the top. Be professional, not gushing.
Multiple roles in one outreach. Pitching "we have several roles you might be interested in" feels like a fishing expedition. Pitch one specific role.
Asking for time before earning interest. "Can we schedule 30 minutes?" in the subject is too aggressive. Lead with the role; save the meeting ask for the body.
Using "URGENT" or "Time-Sensitive." Manufactured urgency from a recruiter feels manipulative.
Sending the same subject to every candidate. Candidates talk to each other. Identical subject lines to multiple engineers in the same Slack community is a credibility hit.
InMail vs Direct Email — Which to Use When
If you have the candidate's email, use email. If not, use InMail. The reasoning:
- Direct email feels more intentional. Finding someone's email takes effort, and candidates can tell. InMails feel like you clicked a button.
- Open rates are higher. Direct email outperforms InMail for response rates by 30-50% in most studies.
- Email has no character limit. InMails are capped at 2000 characters, which forces awkward truncation.
- Email lands in primary inbox. InMails land in the LinkedIn notification system, which candidates may check less often.
The catch: getting the candidate's email is harder than sending an InMail. Use tools like Apollo, Hunter, RocketReach, or SignalHire to find emails for high-priority candidates.
The same subject line works for both channels — the platform does not change the messaging.
Try It Free — No Signup Required
Runs 100% in your browser. No data is collected, stored, or sent anywhere.
Open Free Subject Line GeneratorFrequently Asked Questions
Should I include the salary in the subject line?
Yes if you can. Salary is the #1 piece of information passive candidates want before deciding whether to engage. Including it in the subject is a strong differentiator.
Is "exciting opportunity" really that bad?
Yes. Candidates have seen the phrase in 100+ messages. It triggers an instant "this is a recruiter" filter and most candidates archive without reading. Replace it with anything more specific.
Should I A/B test recruiter outreach subject lines?
Yes if your sourcing tool supports it (Gem, hireEZ, Outreach all do). Test 2-3 variants per role and pick the winner. The compounding effect over hundreds of candidates per quarter is real.
Can I use this for technical recruiting (engineering, data, ML)?
Yes — be specific about the tech stack in your description. The generator will weave the technical context into the subject line for relevance to the candidate.
Will this work for executive search?
The patterns work but executive search outreach should be even more personalized and less templated. For C-level outreach, use the generator for inspiration but always rewrite the final subject line by hand to match the executive seniority.

