Recruiters ignore generic “open to opportunities” blasts. LinkedIn’s own guidance stresses personalization, clarity, and a light ask. Premium Careers advice also pushes profile readiness before outreach. Practical playbooks from hiring tools and job-search coaches add an important layer: your message should fit the situation, whether you are applying cold, following up on a live req, or trying to get routed to the right person.
This guide shows you how to find the right recruiter, write under-300-character connection notes, use req IDs in the first line when relevant, and follow up without sounding desperate. You will also get copy-ready scripts for LinkedIn, including variants inspired by common outreach flows used in tools and teams like Kanbox, Hireflow, and Overloop.
This page was reviewed on October 1, 2026.
TL;DR
- Fix your headline and About before you message anyone.
- Message the right recruiter for the role, team, or geography.
- Keep connection notes under 300 characters.
- For live jobs, put the req number in the first line when possible.
- Use one proof point, not your whole life story.
- Follow up once after 5 to 7 days; stop after two attempts.
- Do not open with “Can you get me a job?”
Before you message: profile readiness
When a recruiter opens your note, they usually click your profile right away. If your profile looks vague or unfinished, even a strong message can die there.
Prepare these basics first:
- Headline that states role + proof: LinkedIn headline examples
- About section that makes your target roles obvious
- Experience bullets that match your resume and current direction
- Open To Work visible to recruiters if that fits your privacy preference
- Professional photo and clean custom URL
- Recent activity that does not contradict the role you are targeting
A recruiter should be able to answer three questions within 10 seconds of landing on your profile:
- What role does this person want?
- Are they plausibly qualified?
- Is there a reason to reply now?
For a fuller tune-up, use: LinkedIn profile tips.
How to find the right recruiter
A great script sent to the wrong recruiter still goes nowhere. Spend a few extra minutes on targeting.
- Open the company LinkedIn page.
- Go to People.
- Search terms like “recruiter,” “talent,” “technical recruiter,” or “campus recruiter.”
- Add the function if needed, such as “engineering recruiter” or “sales recruiter.”
- Read their About section, recent posts, and listed focus areas.
- Prefer recruiters tied to your region, seniority level, or job family.
- From the job post, check whether a hiring contact or poster is named.
- Use alumni or mutual connection filters when available.
A few rules help here:
- Engineering role: message the technical or engineering recruiter, not a campus recruiter.
- Senior role: target someone who hires for experienced candidates, not internships.
- Global company: pick the recruiter in your geography if location matters.
- No clear recruiter: message the recruiter most aligned to the function and ask for a pointer if needed.
Wrong recruiter plus perfect message feels like spam. Right recruiter plus good message feels useful.
Connection request notes (short)
Connection notes have a tight character limit, so every word must work. The safest pattern is:
Hi [Name], applying for [Role] / Req [#] at [Company].
[One proof point]. Would value connecting. - [Your Name]
Keep it under 300 characters. If there is a req number, put it in the first line. That makes the note easier to route and instantly shows you are talking about a real opening.
Script: connection before applying
Hi Asha, targeting Product Analyst / Req PA-118 at Northstar.
2 years in SQL + experiment analysis for B2B SaaS. Would value connecting.
- Maya
Script: after applying
Hi Jordan, applied for Backend Engineer / Req BE-220 at Northstar yesterday.
I build Go services + Kafka pipelines in payments. Happy to connect.
- Rajiv
Script: after engaging with their content
Hi Elena, your post on PM hiring was useful.
I’m targeting Product Ops / Req PO-77 at Northstar and currently run launch ops at a Series A startup.
Open to connect? - Nina
Engaging genuinely first can help. LinkedIn’s guidance on connecting with recruiters often suggests liking or commenting before outreach so your name is at least a little familiar.
First message after they accept (or InMail)
Once they accept, or if you are using InMail, switch from connection-note brevity to a compact, scannable message. LinkedIn’s best-practice structure is still the right one:
- Personalize
- Get to the point quickly
- Show one proof point
- Make a light ask
Hi [Name],
Thanks for connecting. I’m a [title] with [X years] in [domain], currently exploring [specific role or job family] at [Company].
Most relevant proof: [1 metric, project, or ownership line].
I applied on [date] for [Role / Req #] via [portal], or I’m planning to apply today.
If helpful, I can send a tailored resume or a short summary of fit.
Open to a brief 10–15 minute chat if that’s useful.
Thanks,
[Name]
[Email] | [Phone]
Script: cold outreach with a live req
Hi Priya,
Thanks for connecting. I applied yesterday for Senior CSM / Req CS-441.
I have 5 years in B2B SaaS success, currently own a 40-account mid-market book, and improved gross retention by 8 points in my current role.
If helpful, I can send a tailored resume or short account summary.
Open to a quick fit check this week?
Thanks,
Lena Ortiz
Script: no open role, ask for direction
Hi Sam,
Thanks for connecting. I’m a full-stack engineer focused on TypeScript, Postgres, and marketplace infra.
I did not see an exact match open today, but your team’s work is closely aligned with my background. If you are not the best contact, would you point me to the right recruiter or let me know when similar reqs usually reopen?
Appreciate any steer,
Devon Brooks
Script: referral or mutual connection
Hi Alex,
Chris Park suggested I reach out. I’m applying for Marketing Ops / Req MO-19 and have 4 years running HubSpot lifecycle automation at a Series B SaaS company.
Happy to send a short fit summary if useful, or I can simply apply through the portal first if you prefer.
Thanks,
Sam Okonkwo
Confirm first that the referrer is comfortable being named.
A practical outreach matrix
Use this quick matrix to pick the right message shape instead of sending the same script every time.
| Situation | First line | Main proof | CTA |
|---|---|---|---|
| Live role, not yet applied | Targeting [Role] / Req [#] | 1 relevant metric or scope line | “Worth applying?” or “Any fit guidance?” |
| Live role, already applied | Applied for [Role] / Req [#] on [date] | 1 role-matching proof line | “Happy to send tailored resume” |
| No live role | Interested in [team/function] | Domain fit or adjacent experience | “Point me to the right recruiter?” |
| Referral route | [Mutual name] suggested I reach out | Proof tied to role | “Prefer portal first or summary?” |
| After content engagement | Your post on [topic] was useful | Skill line tied to role | “Open to connect?” |
Quick checklist before you hit send
- Is this the right recruiter for the function?
- Did you name the role and req number if one exists?
- Is the connection note under 300 characters?
- Did you include only one proof point?
- Is your CTA light, not demanding?
- Does your profile support the claim you just made?
After you apply: status check message
This is one of the best reasons to message a recruiter because the ATS record already exists.
Hi Jordan,
Quick note that I applied for Backend Engineer / Req BE-220 on 18 March via the careers portal.
Most relevant fit: I own Go services in payments and reduced p95 latency by about 35% on our authorization path last year.
If helpful, I can share a brief architecture summary or tailored resume.
Thanks for considering my application.
- Rajiv Nair
Notice what works:
- Req number appears early
- The message is specific
- One strong proof point replaces a paragraph of claims
- The ask is light
Kanbox / Hireflow / Overloop-style scripts
A lot of outbound tooling encourages concise, pattern-based prospecting. That is useful here too, as long as the message still feels human. The common winning traits are:
- short first line
- role or req named immediately
- one personalization element
- one proof point
- low-pressure CTA
Below are recruiter-safe versions that follow that style.
Kanbox-style: concise and familiar
Best when you want a message that feels direct and natural.
Hi Nina, applied for RevOps Manager / Req RO-54 this morning.
I currently run Salesforce + forecasting operations for a 25-rep SaaS team and cut lead-routing time by 60%.
If useful, I can send a short fit summary. Thanks for taking a look.
Hireflow-style: tailored to application context
Best when you want the note to feel optimized for resume-to-role fit.
Hi Marcus, I applied for Data Analyst / Req DA-203 on 27 Sept.
My background lines up closely with the SQL + experimentation focus in the posting. Most relevant result: built funnel reporting that improved activation by 11%.
Happy to send a tailored resume if helpful.
Overloop-style: polite outbound with clear next step
Best when you want a soft CTA and easy reply path.
Hi Talia, targeting Customer Education Lead / Req CE-88 at Northstar.
I’ve built onboarding webinars and self-serve learning content for SMB SaaS users, which cut repeat support tickets by 18%.
If you’re the right contact, I’d value any fit guidance. If not, a pointer would help.
These are useful templates, not excuses to automate blindly. If your message reads like it was blasted to 200 people, recruiters can tell.
Follow-up timing
Timing matters almost as much as wording.
| Touch | When | Goal |
|---|---|---|
| Connection note | Day 0 | Start relationship |
| First message | On accept or via InMail | State fit + light CTA |
| Follow-up 1 | 5–7 days later | Polite bump |
| Follow-up 2 optional | About 7 days later | Final check-in, then stop |
LinkedIn recruiter-message advice commonly cites a 5 to 7 day follow-up window. Many job-search playbooks also recommend stopping after one or two attempts.
Parallel email cadence: job application follow-up.
Follow-up script
Hi Priya, circling back on my note about Senior CSM / Req CS-441.
Still very interested and happy to send a tailored resume or work around your schedule for a brief fit check.
Thanks either way,
Lena
What not to do
- Mass identical InMails
- “Dear recruiter, please give me a job”
- Eight dense paragraphs
- No role name or req number when one exists
- Attaching a resume with no context
- Sending daily bumps for two weeks
- Arguing if they say the req is filled
- Asking a stranger for an internal referral in message one
- Pretending you know their work when you obviously do not
The fastest way to look unserious is to make the recruiter do all the decoding.
Should you attach a resume in message one?
It depends.
Attach a tailored PDF when:
- you already applied
- the role is a close match
- the recruiter is likely screening quickly
- the file adds convenience, not clutter
Hold off and offer to send it when:
- the outreach is exploratory
- you are not yet sure the recruiter is the right contact
- your profile already tells the story well
- the role fit is adjacent rather than exact
If you do attach it, name the file clearly, like:
Firstname_Lastname_Role_Resume.pdf
Do not password-protect it.
Building familiarity without spam
Recruiter outreach works better as part of a system, not as a one-off cold ping.
Try this instead:
- Comment thoughtfully on 2 to 3 relevant posts over a week
- Share a short project or work sample update
- Keep your headline and Open To Work settings current
- Apply through the portal so your ATS record exists
- Use a tracker so you do not accidentally double-message people
Tracking sheet (simple)
| Recruiter | Company | Role / Req | Date sent | Follow-up due | Status |
|---|---|---|---|---|---|
A basic tracker prevents the most common outreach mistakes: forgetting who you contacted, following up too soon, or mixing up roles.
InMail vs connection request vs email
| Channel | Use when | Watch-out |
|---|---|---|
| Connection note | You have a clear role target | Character limit; keep it ultra short |
| Message after connect | They accepted | Still keep it scannable |
| InMail | You cannot connect easily | Costs credits; personalization matters more |
| Company email | Posting lists it | Keep format professional |
If you have both InMail and a portal, apply in the portal first so the ATS record exists, then message with the req number.
Personalization cheatsheet: 30 seconds of research
Before you hit send, capture at least one of these:
- Exact job title and req ID
- A post they wrote recently
- Shared school, city, or mutual connection
- Product launch or team expansion note
- Geography match if the role is location-specific
One real detail beats three generic compliments every time.
Sample week of recruiter outreach
| Day | Actions |
|---|---|
| Mon | Apply to 5 roles and list recruiters for 3 of them |
| Tue | Send 3 personalized connection notes |
| Wed | Message anyone who accepted; engage with 2 posts |
| Thu | Apply to 5 more roles; update tracker |
| Fri | Send one follow-up batch for notes aged 6+ days |
| Weekend | Improve profile gaps and tighten resume bullets |
Volume without personalization burns your reputation. Personalization without applications wastes warm replies.
When they say no or stay silent
Thank them, ask whether another team may fit your profile, and move on. Do not debate or guilt-trip them.
A good closing line is:
Thanks for the update. If another role closer to my background opens on your team, I’d be glad to be considered.
Then revisit the company later. Keep your profile current so inbound opportunities can do some of the work for you.

Run it on Parlel
LinkedIn messages capture busy humans. A public skills profile helps founders, recruiters, and agents find you even when your direct outreach gets missed.
profile.headline: backend engineer, go + kafka, open to platform roles
profile.skills: go, kafka, postgres, kubernetes
profile.open_to_work: true
digest: weekly roles matching skills + companies you messaged
Digest shape:
{ role, company, matched_skills, location_eligibility }
Cross-check openings on /jobs so your messages always reference a real role or req.
Frequently asked questions
Should you message a recruiter on LinkedIn before applying?
Yes, if you have a specific role, fit question, or a reason to believe they own that req. But for many jobs, the strongest sequence is apply first, then send a short message with the req number.
What should you say to a recruiter on LinkedIn?
Say who you are, which role you mean, one proof point that shows fit, and a light next step. Do not make them infer the context.
How long should a LinkedIn message to a recruiter be?
Short enough to read on a phone in one glance. Connection notes should stay under 300 characters. Full messages should usually be a few short paragraphs at most.
Should you attach your resume in the first LinkedIn message?
Optional. It helps most when you already applied and the recruiter can use it immediately. For exploratory outreach, offer to send it instead.
When should you follow up with a recruiter on LinkedIn?
About 5 to 7 days after your first message is a common and reasonable window. One follow-up is standard. A second and final one is okay in some cases.
Is it okay to ask a recruiter for a job on LinkedIn?
Not bluntly. Ask for fit guidance, a pointer to the right person, or confirmation that your application is in the right place. A direct demand usually reads as spam.