Networking
Cold Messaging on LinkedIn: Templates That Actually Get Recruiter Replies
Cold messaging on LinkedIn has a reputation problem. Most people either do not do it because it feels presumptuous, or they do it badly and conclude that it does not work. The reality is that direct outreach is one of the highest-conversion activities in a job search — when it is done right. A well-crafted message to the right person can bypass the ATS entirely, surface your application to the top of a recruiter's queue, or open a conversation that was never going to happen through the job portal.
This guide explains exactly how to do it in a way that respects the recipient's time and gives your message a real chance of getting a reply.
1. Why Most Cold Messages Fail
The messages that go unanswered share a common structure: they are long, they lead with what the sender wants, and they give the recipient no obvious reason to respond. Recruiters and hiring managers at tech companies receive dozens of unsolicited messages per week. The ones that get ignored look like this:
"Hi [Name], I hope you are doing well. I came across your profile and I am very interested in opportunities at [Company]. I have X years of experience in [broad function] and I believe I would be a great fit. I have attached my resume for your consideration and I would love to connect and learn more about any open positions. Please let me know if you have time for a quick call. Thank you for your time."
This message fails for several reasons simultaneously:
- It opens with a filler greeting that wastes the first sentence — the only one that is almost always read
- It makes no mention of anything specific about the company, role, or the recipient's work
- It leads with what the sender wants rather than what might be interesting or useful to the recipient
- The ask — "let me know if you have time for a quick call" — is vague and puts the work of scheduling entirely on the recipient
- At a glance, it reads as a template sent to 200 people, because it is
The fix is not a different template. It is a different orientation: your message should demonstrate that you have done 10 minutes of real research, make a specific and easy-to-act-on ask, and be short enough to read in 30 seconds.
2. Recruiter vs Hiring Manager — Different Goals
The approach that works for a technical recruiter will not work for a hiring manager, and vice versa. They have fundamentally different motivations for replying to your message.
Technical Recruiters are measured on pipeline volume, time-to-fill, and offer acceptance rates. They want to know quickly whether you are a qualified candidate for an open role on their slate. Your message to a recruiter should be efficient: your current role, the specific role you are interested in, one specific qualification that maps to the role, and a clear ask. They will reply if they have an open role you might fit and your background passes the initial filter. They will not reply to engage in a general conversation about career trajectories.
Hiring Managers are rarely looking for outreach from candidates — that is what the recruiter is for. But they do occasionally reply when a message shows genuine knowledge of their team's work, a specific technical perspective, or a background that is uncommon in the pipeline. Your message to a hiring manager should focus on the work, not the job search. Reference something specific about the team's product, a technical decision they made publicly, or a problem they are working on. The ask should be for insight, not an interview.
3. Connection Request Note vs InMail
LinkedIn gives you two main mechanisms for reaching someone outside your network: a connection request with an optional note (300 characters), and InMail (sent directly, available with premium accounts, up to 2,000 characters).
Connection request notes have a higher open rate than InMail in most contexts. The notification format ("X wants to connect with you") creates a natural open, and the brevity constraint forces you to be specific. The downside is 300 characters — roughly two sentences — which requires discipline. Do not waste characters on "I hope this message finds you well." Get directly to the point in the first line.
InMail allows more context but has a lower baseline open rate than connection notes. The advantage is that you do not need to be connected first, and for certain high-value outreach — a specific message to a VP of Engineering about a role their team is hiring for — the additional length lets you build a more complete case. The same principle applies: lead with specificity, not with what you want.
4. The Anatomy of a Message That Gets a Reply
Every effective cold message has the same structure, regardless of whether it is a connection note or a full InMail:
- A specific hook — One sentence that demonstrates you have done real research. Reference the company, the team, a recent product launch, a public talk, an engineering blog post, or a technical decision. Not "I admire your company." Something specific.
- Who you are in one line — Your current role and one relevant credential. Not your resume summary. One line.
- The ask — small, specific, and easy to say yes to — Not "I would love to work for you." A small, specific request: a 20-minute call, a question about the team, a referral to the right recruiter. The smaller and more specific the ask, the more likely you get a yes.
Total length for a connection note: under 280 characters if possible. For InMail: under 150 words. For a direct message to someone already connected: under 100 words. Every word you cut increases your reply rate.
See how your resume reads to Workday, Greenhouse, and Taleo before you apply.
Analyze your resume free →5. Four Templates for Different Situations
Use these as starting points. Customize the hook with something specific before sending. A message that takes you 3 minutes to personalize will outperform one that takes 3 seconds every time.
I saw that [Company] is expanding the platform engineering team and posted two Staff Engineer roles this month. I have spent the last 4 years building high-throughput data pipelines at [current employer] — most recently architecting a system that processes 40M events per day with sub-100ms p99 latency. That maps closely to what I see in [Company]'s JDs.
I have already applied through the portal but wanted to reach out directly. Would a 15-minute call be useful for you to gauge fit before screening?
Thanks — [Your Name]
I applied for the [Role Title] role at [Company] on [date] through your careers page. I wanted to make sure my application did not get lost in the queue — I have strong overlap with the requirements, particularly [specific skill from JD].
I would be happy to answer any quick questions about my background or send additional materials. If this role is not the right fit right now, I am open to hearing about similar openings on your team.
Thanks for your time — [Your Name]
I read your team's recent post on [engineering blog topic] and had a question about the tradeoffs you described in the consistency model. That approach is close to something we are wrestling with on my current team.
I am also exploring my next move and [Company]'s infrastructure team is on my short list. Would you be open to a 20-minute call sometime in the next few weeks? I would genuinely value your perspective on the team's current technical priorities — and happy to share what we have learned on my end too.
No pressure at all if the timing is off. — [Your Name]
6. Follow-Up Timing and What to Say
Most guides tell you to follow up once after 5-7 days and leave it there. That is reasonable advice, but the follow-up message itself is where most people make a second mistake: they send a reminder that adds no new value.
"Hi [Name], just wanted to follow up on my previous message — I am still very interested in opportunities at [Company]" is a prompt to say no, not a reason to reply.
A follow-up that works adds something. A relevant article about a problem the company is working on. A short update — "I should mention, I shipped the distributed cache migration I mentioned, cutting latency by 30% — happy to walk through the design if that would be useful." A new question that did not appear in the original message.
Follow-up sequence that works for most contexts:
- Day 0: Send the original message, Tuesday through Thursday mornings perform best
- Day 6-8: One follow-up that adds a piece of new information or a slightly different ask
- After that: Move on. A third message crosses from persistent into annoying. If the timing is ever right for them to respond, they have your message in their inbox.
7. What Not to Do
A few behaviors that consistently reduce your reply rate or damage your reputation with a recruiter or hiring manager:
- Sending the same message to 15 people at the same company. Recruiters talk to each other. If they compare notes and realize you sent the identical message to the entire team, you look like you are running a mail merge, not making genuine outreach.
- Attaching your resume in a cold message. An unsolicited resume attachment is presumptuous and often filtered as spam. Mention you have one and offer to share it — do not attach it without being asked.
- Asking about "any openings" at the company. This puts the research burden on the recipient. Do your research first. Know which role you are interested in and name it.
- Leading with your need rather than their perspective. "I am currently unemployed and urgently seeking a role" is not something a recruiter needs to know in a cold first message. Lead with your value, not your situation.
- Sending on Fridays or over the weekend. Messages sent Friday afternoon or over the weekend are buried under everything else when the recipient opens LinkedIn Monday morning. Tuesday through Thursday, morning, consistently outperforms other timing.
- Connecting first and then immediately sending a pitch. Accept the connection, wait at least a few days, and ideally interact with something they posted before sending a direct message. The cold-connect-then-immediate-pitch pattern is widely recognized and widely ignored.
Cold messaging on LinkedIn is a numbers game in one sense — not everyone will reply — but it is a quality game in the more important sense. Ten highly personalized messages sent to the right people at companies you genuinely want to join will produce more conversations than one hundred copy-pasted messages sent to every recruiter at every company with an open req. Start with quality. The volume follows naturally once the process is working.