Recruiter Email Subject Lines That Get Opened

The subject line is the entire product. A recruiter decides in under two seconds whether to open, archive, or ignore your email. Below are 24 subject lines that consistently outperform, grouped by the situation you’re writing from.

Four principles behind the good ones

• Specificity beats persuasion. Name the role, the team, or a mutual contact. Persuasion words (“great,” “perfect,” “amazing”) trigger a triage-and-archive reflex.
• Under 55 characters. Mobile Gmail truncates at around 55. If the important part is at character 62, it’s invisible.
• Talk like a person, not a marketer. No all-caps, no emoji, no exclamation marks. Sentence case with standard capitalization reads as human.
• Front-load the pattern-match. The word the recruiter is scanning for (the role, the team, the mutual name) should be in the first three words when possible.

Cold intros (no prior contact)

• Interested in your {Role} req — {years} yrs {skill}
• {Role} at {Company} — quick intro?
• Ex-{Prev Company} engineer, targeting {Company}
• {Role} candidate for {Team} at {Company}
• Following up on your {Role} posting
• 15 min to talk about the {Team} role?

Warm intros (referred, mutual contact, prior interaction)

• {Mutual Name} suggested I reach out re: {Team}
• Referred by {Name} — {Role} on {Team}
• Following up from {Event/Conf}
• {Mutual Name}’s intro — {Role} for {Team}
• Met at {Event} — resurfacing {Role} chat
• {Company} alumni — interested in {Team}

Follow-ups (day 4–5 and day 10–12)

For follow-ups, don’t change the subject — reply in the same thread so Gmail keeps it grouped. But if you’re re-approaching after a longer gap, these open well:

• Bumping this — {Role} on {Team}
• Quick nudge re: {Role}
• Last note on {Role} — timing question
• {Role} update — new context
• Re-surfacing this in case it slipped
• Closing the loop on {Role}

Niche situations

Post-layoff, career pivot, or reaching out about a specific event:

• Impacted by {Prev Company} layoffs — {Role} search
• Pivoting into {Role} — {transferable-skill} background
• {Prev Company} → {Company} — {Role} candidate
• Interested in {Team} after seeing {project/launch}
• Applied for {Role} — 30 sec context?
• Returning to {Role} after {event} — {years} yrs prior

Subject lines to never use

• “My resume” / “Attached resume” — zero context.
• “Opportunity!” — sounds like a scam.
• “URGENT” or ALL CAPS — spam-filter magnet.
• “Following up” with no object — recruiter has no idea what.
• “Hi {First Name}” — feels like the merge field failed.
• “Quick question” — overused and dishonest (they know it’s a pitch).

The subject-line testing loop

If you’re sending 20+ per day, A/B test one variable at a time. Split the day: send template A in the morning batch and template B in the afternoon batch, then compare reply rates over 10 business days. Small samples lie — 100+ sends per variant is the minimum meaningful test.

What Fwalla does with subjects

Fwalla merges the recruiter’s role/team/company into your subject line automatically and keeps the length under the mobile Gmail truncation threshold. Follow-ups reuse the original subject so Gmail threads them cleanly.