12 min read
The best US LinkedIn message to a recruiter names one skill from the posting and one proof line from your resume. It does not open with "I'm passionate about opportunities" or "Are you hiring?" Recruiters reply when they can forward your note to a hiring manager without rewriting it.
You've applied on Greenhouse. You've waited a week. You're tempted to send a long paragraph about your career arc. Don't. Corporate recruiters skim messages on mobile between req reviews. They need a role anchor, a match, and a clear ask in under six sentences. Job searching is already slow. A vague message adds another dead end.
Check your resume for free before you message anyone. Your proof line should come from bullet one on your current role, not a summary you invented for chat. If the resume does not parse cleanly, fix that first. The recruiter will open the application file after they reply.
Below you'll see what weak templates share, six before/after pairs across marketing, finance, and engineering roles, and a copy-paste block you can adapt per posting. Composite examples only. Swap in your req title and proof line.
I've screened stacks of these in Workday and Greenhouse, and the message that gets a reply is boring and specific. Role name, one skill, one number or scope line, one ask. That's the bar the pairs below are judged against.
When the posting asks for a cover letter, align your message with the same proof line you'll use in the letter. Generate a cover letter from your resume text so employer names and metrics match what you typed to the recruiter.
Quick Wins
- Lead with the req title or role family from the posting.
- Name one must-have skill and one proof line from bullet one on your resume.
- Keep it under six sentences. Recruiters read on mobile.
- End with one ask: confirm receipt, preferred next step, or scheduling window.
The bar a recruiter-forwardable message must clear
A recruiter can forward your note when it answers three questions in order: which role, why you match, what you want them to do. Passion paragraphs, availability asks without a posting, and resume dumps fail that test. The hiring manager should read your proof line and know which bullet to ctrl-f in the application.
The structure that wins: greeting, req title, one skill from the posting, one proof line from your resume, application status, one ask. Four to six sentences total.
US corporate recruiters often own twenty open reqs. They will not open your attachment from chat if the message does not name which req you mean. Link the Greenhouse or Workday application in one sentence when you have already applied. Mention the req ID if the board listed one.
Your proof line should mirror bullet one on your current role. Not a new metric you did not put on the resume. Not a skill you only listed under Skills. The recruiter will compare chat to the parsed profile. Mismatches kill trust faster than silence.
Read how to follow up after applying without being annoying when you need the second touch after a recruiter goes quiet.
Read what recruiters look for in resumes so your proof line matches what they ctrl-f after your message lands.
Before/after message pairs across roles
Each pair shows a weak version recruiters mute and a forwardable rewrite. Replace bracketed lines with your req and proof. Illustrative titles only.
Pair 1: Marketing manager, demand gen req
Posting lists HubSpot, paid social, and pipeline ownership for a SaaS brand team.
Before: Hi! I'm very passionate about marketing and would love to connect about any open roles on your team. I have extensive experience with digital campaigns and am immediately available. Would love to chat!
After: Hi [Name], I applied to the Demand Gen Manager req (#[ID]) on Greenhouse. Your posting calls for HubSpot and paid social. At Northwind SaaS I ran lifecycle and paid in HubSpot and delivered 412 MQLs in Q2 at $38 CPL. Resume is in the portal. Are you the right contact for a brief screen this week?
Pair 2: Brand marketing coordinator
Posting wants integrated campaigns and agency management for a consumer brand.
Before: Hello, I came across your profile and I'm excited about brand marketing opportunities. I think I'd be a great fit for your company culture. Let me know if you have time for a coffee chat!
After: Hi [Name], applying to Brand Coordinator req #[ID] today. You need integrated launch campaigns and agency partners. I led a Q4 product launch across email, paid, and events with $1.2M media budget and two agency vendors. Workday application will be in by EOD. OK to note you as my contact?
Pair 3: Financial analyst, FP&A
Posting lists Excel modeling, NetSuite, and monthly close support for a public tech company.
Before: Dear Recruiter, I am writing to express my interest in finance roles at your organization. I am a hard worker with strong analytical skills and am open to any suitable position. Please find my resume attached.
After: Hi [Name], I submitted FP&A Analyst req #[ID] on Workday this morning. Posting mentions NetSuite and monthly close. I built three-statement models in Excel for a $180M ARR unit and supported NetSuite close for 14 entities last year. One question: do you prefer a 30-minute screen or async review first?
Pair 4: Senior accountant, technical accounting
Posting wants ASC 606 experience and audit coordination.
Before: Hi there! I'm an experienced accountant looking for new challenges. I'd appreciate any referrals you might have. Thanks in advance!
After: Hi [Name], targeting Senior Accountant req #[ID] you posted. Must-have ASC 606 caught my eye. I owned revenue recognition memos for SaaS contracts and coordinated two Big Four audits with zero material adjustments in FY2024. Application uploaded to Greenhouse. Worth a five-minute skim before you forward to the controller?
Pair 5: Backend software engineer
Posting lists Python, FastAPI, and AWS for a payments platform team.
Before: Hey! I'm a software engineer with 5+ years of experience in various technologies. I'm very interested in your company and would love to learn more about engineering opportunities. Thanks!
After: Hi [Name], applied to Backend Engineer req #[ID] on Greenhouse. You need Python and FastAPI on AWS. I built payment APIs in Python/FastAPI on AWS at FinLayer and cut p99 latency 18% in Q1 2025. Resume is in the portal. Are you screening this req or should I note a different contact?
Pair 6: Platform engineer, Kubernetes focus
Posting wants Terraform, GKE, and on-call for infrastructure team.
Before: Hello, I specialize in DevOps and cloud infrastructure and am actively seeking new roles. I'd welcome the chance to discuss how I can contribute to your team. Looking forward to hearing from you!
After: Hi [Name], Workday app in for Platform Engineer req #[ID]. Posting calls for Terraform on GKE. I ran Terraform modules for twelve production clusters and held incident MTTR under 45 minutes on Q3 on-call. Happy to share employer names if the parsed profile scrambled dates. Open Thursday 2 to 4 PM ET for a screen?
Copy-paste message templates
Copy-paste and replace bracketed lines. Keep one skill and one proof line per send.
Template A (already applied):
Hi [Recruiter name], I applied to [Job title] req #[ID] on [Greenhouse/Workday]. Your posting calls for [skill from posting]. At [Employer] I [proof line from resume bullet one]. Resume is in the portal. [One ask: screen this week / correct contact / OK to note you]?
Template B (applying today):
Hi [Recruiter name], submitting [Job title] req #[ID] by EOD. Must-have [skill] matches my current role: [proof line]. [Greenhouse/Workday] application will show [Employer] as most recent. Worth a quick skim before you forward?
Template C (follow-up, one touch only):
Hi [Recruiter name], following up on [Job title] req #[ID] from [date]. I updated bullet one to include [posting skill] and re-uploaded on [portal]. Still interested in a 20-minute screen if the team is moving this week.
What weak recruiter messages share
No role anchor. "Any open roles" forces the recruiter to guess which req you mean. They won't. Name the title or req ID from the board.
Passion instead of proof. Excited about your mission does not tell the hiring manager what you shipped. Swap passion for one metric or scope line from bullet one.
Skill lists without context. Ten technologies in chat without a job block on the resume reads like keyword spray. One skill from the posting, one proof line from Experience.
Resume paste in the chat box. Walls of text get archived on mobile. Point to the portal upload. Mention you applied. Let them open the file in Workday where they already work.
Multiple asks in one note. Coffee chat plus referral plus salary question plus portfolio review is four conversations. Pick one: confirm contact, request a screen, or ask preferred next step.
Mismatch with the resume. If chat says 412 MQLs but the parsed profile shows no demand gen bullet, the recruiter assumes sloppiness or exaggeration. Pull proof from bullet one you already uploaded.
Third messages without a reply. Two touches max per req unless the recruiter responds. A third note without new information trains recruiters to mute you on future reqs.
Edge case: recruiter posted the role but does not own the req. Ask politely if they are the right contact. Offer to apply through the portal link they shared. Do not argue about ownership in message one.
Edge case: internal referral plus recruiter message the same day. Send the recruiter one line noting your employee referral and the req ID. Do not send duplicate proof paragraphs to both. Same facts, shorter note to the recruiter.
Timing the send. Tuesday through Thursday mid-morning US time beats Sunday night or Friday afternoon when recruiters clear req backlogs before the weekend. That is pattern, not a guarantee. A sharp message on Monday still beats a vague one on Wednesday.
Subject line on InMail. When the platform gives you a subject field, use the req title, not your name. Backend Engineer #[ID] beats Experienced professional seeking opportunities. The recruiter's inbox is sorted by role, not by how polished your headline sounds.
Connection request vs message. If you must send a connection request with a note, keep the note to three sentences. Role, skill, proof. Save the longer Template A for after they accept or when InMail allows a full message without a connection.
Align resume and outreach before you send
Run the free ATS checker with the job description pasted in. Your proof line should match a bullet the parser kept on an Experience line, not a Skills footer that imported cleanly while employers scrambled.
Then score your job match on the same file. If you are weak on a must-have, fix bullet one before you message the recruiter claiming that skill. Chat does not rescue a resume gap the hiring manager will spot in five seconds.
Send one message tonight
The best US LinkedIn message to a recruiter is short, role-anchored, and built from bullet one on your resume. Pick the next req on your list. Pull one skill from the posting. Pull one proof line you already uploaded. Paste Template A or B. Send once.
This won't turn a cold req warm when you are not qualified. It does stop qualified candidates from getting archived because the recruiter could not tell which job they meant or what to forward to the hiring manager.
Save three template variants in your notes app labeled by role family: marketing, finance, engineering. Swap req ID and proof line per send. Boring structure beats a new creative opener every time.
Before you hit send, read the message aloud once. If you cannot name the req title and the proof line without looking back at the screen, the recruiter will not be able to either. Fix the anchor, then send.
Read more
Frequently asked questions
Aim for four to six sentences, under 400 characters when you can. Lead with the req title or role family, name one must-have skill from the posting, and attach one proof line from your resume. Skip your full career story. Recruiters reply when they can forward your note to a hiring manager without rewriting it.
Mention that your resume is attached to the Greenhouse or Workday application when you already applied. Do not paste your resume into the chat box. If you have not applied yet, ask whether they prefer an in-portal upload or a direct file. One link beats three attachments on mobile.
Yes when you reference a live posting they own or a req number from the job board. Cold messages without a role link get ignored. Name the posting, one skill match, and one proof line. That is not spam. A generic availability ask without a role is.
Wait five business days, then send one follow-up with a new detail: you completed the Workday application, you added a bullet that matches their must-have, or you have a scheduling constraint next week. Do not send a third message without a reply. Move to the next req on your list.
Structure stays the same: role, one skill, one proof line, one ask. Engineers lead with stack and production scope. Marketers lead with channel and metric. Finance leads with system and close scope. Weak versions across all three open with passion or availability instead of a posting anchor.