Cold Emails and LinkedIn Messages to Recruiters: 12 Templates That Get Replies

Cold outreach is one of the highest-leverage activities in a software job search, and one of the most poorly executed. Most messages recruiters get are some version of "Hi sir, please find my resume attached, kindly consider me for any suitable role." They get ignored, not because outreach doesn't work, but because that message gives the recipient nothing to act on.

This guide breaks down why messages get ignored, the structure of messages that get replies, who to contact, and then gives twelve templates you can adapt. The templates are written for the Indian job market (LinkedIn-heavy, referral-driven, notice periods), but the principles apply anywhere.

Why Most Cold Messages to Recruiters Are Ignored

Put yourself in the recipient's position. An in-house tech recruiter at a product company may be handling many open roles at once and receives a steady stream of LinkedIn messages and emails. An engineer who gets a referral request is doing you a favour in between their actual work. Each message is triaged in seconds.

Messages fail that triage for predictable reasons:

• No specific role. "Any suitable opening" forces the recipient to do your job search for you.
• Too long. Three paragraphs about your passion for technology won't be read on a phone between meetings.
• No proof. "I am a hard-working fresher" carries no information. "Built X used by Y; 450 LeetCode problems" does.
• Unclear ask. The recipient doesn't know whether you want a referral, a call, advice or a job.
• Obvious mass message. Wrong name, wrong company, "Dear Sir/Madam", or a copy-pasted block with no personal line.
• Just "Hi". A message that says only "Hi" or "Hello sir" and waits for a reply puts the work on the recipient. Many people never respond to these.

The Anatomy of a Message That Gets Replies

Every template below follows the same five-part structure. Once you understand it, you can write messages for situations no template covers.

Subject lines for emails

For email (not LinkedIn), the subject line decides whether it's opened. Put the role and your strongest signal in it:

• SDE-1 Backend (Job 12345) – 2 YOE Java, payments experience
• 2026 CSE grad – built a UPI-style ledger in Go – SDE intern/new grad
• Referred by Ankit Sharma – Frontend Engineer role (only if true)

Avoid "Job Application", "Resume", "Request" or "Hi" as subjects. They look like spam and say nothing.

LinkedIn connection notes have a short limit

Connection request notes on LinkedIn are limited to a short length (a few hundred characters at most, and less on some free accounts at the time of writing), and free accounts may have a cap on personalised invitations per month. So the connection note should be a short hook plus intent; save the full message for after they accept, or use InMail if you have it.

Who to Contact and How to Find Them

Finding email addresses: many companies use a predictable format (firstname.lastname@company.com), but guessing and blasting addresses is spammy and can bounce. LinkedIn messages are the default in India; reserve email for founders, people who list their email publicly, or when you've been told to email. Don't scrape or buy contact lists.

Make sure your own profile is ready before you message anyone. The first thing a recipient does is click your profile. Our LinkedIn profile optimization guide covers what they should see.

Templates for Freshers and Students (1–4)

Template 1: Fresher to an in-house recruiter about a specific opening

Subject: SDE-1 New Grad (Job ID 48213) - 2026 CSE grad, Java + Spring Boot

Hi Neha,

I saw the SDE-1 New Grad opening on [Company]'s careers page and applied
yesterday. I'm a 2026 CSE graduate from [College]. My strongest project is a
peer-to-peer marketplace in Spring Boot + PostgreSQL used by ~300 students,
where I cut search latency from ~900 ms to ~120 ms with a trigram index.
I've also solved 450+ LeetCode problems (contest rating 1780).

Could you check whether my application is in the queue for this role? I've
attached my resume. Happy to share anything else that helps.

Thanks,
Aditya | github.com/aditya | +91-XXXXXXXXXX

Why it works: exact job ID, already applied (so the ask is small: look at it), one project with a number, one DSA signal.

Template 2: Fresher to a startup founder (no opening posted)

Subject: Backend engineer (2026 grad) - built an inventory sync like yours

Hi Karthik,

I've been following [Startup]'s work on inventory software for kirana stores.
For my final-year project I built an offline-first inventory app (React Native +
SQLite, syncing to a FastAPI backend) that handles conflicting edits when two
devices update stock offline. Demo: [link].

I'm graduating in June and would love to join a small team where I'd ship to
real users quickly. If you're hiring engineers this year, I'd be grateful for a
15-minute chat. Resume attached.

Thanks for building this,
Sneha

Why it works: founders care about relevance to their problem. The project mirrors their product's core difficulty (offline sync conflicts), which is far more compelling than a generic portfolio.

Template 3: Student to an alumnus for an internship referral

Hi Rahul, I'm a 3rd-year CSE student at [College] (your alma mater!) applying for
[Company]'s SDE Intern 2027 role. Would love to ask you one quick question about it.

Thanks for connecting, Rahul! I'm applying for the SDE Intern 2027 role
(Job ID 51022, link below). I've done 400+ DSA problems and built a real-time
quiz app (Node.js + WebSockets) used by our coding club for weekly contests.

Would you be open to referring me? Resume and job link are below, so it should
take under two minutes. No worries at all if you'd rather not.

Resume: [link]   Job: [link]

Template 4: Fresher after a hackathon or event

Hi Meera, thanks for judging at [Hackathon] last weekend. Your feedback on our
team's caching approach was really useful; we've since added Redis and cut
response time by half. I'm graduating in 2026 and very interested in the
platform team at [Company]. Are there new-grad openings there this cycle, or
someone you'd suggest I speak with?

Why it works: a genuine prior interaction, evidence you acted on their feedback, and a question that's easy to answer even if the answer is "not right now".

Templates for Experienced Engineers (5–7)

Template 5: Experienced engineer to a recruiter

Hi Pooja, I noticed [Company] is hiring a Senior Backend Engineer for the
lending platform (Job ID 77310). I have 4 years in Java/Spring and Kafka at
[Company], where I lead our loan disbursement service (handles peak loads of a
few hundred TPS with exactly-once processing via idempotency keys).

My notice period is 60 days, negotiable. Would you be open to a quick call this
week to see if there's a fit? Resume attached.

Why it works: in India, notice period is one of the first things recruiters filter on, so stating it upfront saves a round-trip. Domain match (lending) is explicit.

Template 6: Experienced engineer to a hiring manager

Subject: Search relevance engineer - 5 YOE, Elasticsearch at scale

Hi Arjun,

I read your team's engineering blog post on rebuilding [Company]'s product
search ranking. I've spent the last 3 years on search at [Company], where I
built our query understanding layer (spelling correction + synonym expansion)
on Elasticsearch, which improved search-to-cart conversion in an A/B test.

I saw the Senior SDE - Search opening and applied through the careers page.
If you think there's a fit, I'd value 20 minutes to learn what the team is
focused on next. Either way, thanks for the write-up.

Vikram

Why it works: references the manager's own work, demonstrates domain depth, and has already applied through the proper channel, so the manager isn't being asked to bypass process.

Template 7: Service-to-product switcher

Hi Sameer, I'm a Java backend developer (2.5 YOE) at [IT services company],
working on a claims processing system for an insurance client. I recently
reduced our document generation time from ~8 min to ~90 s by batching DB calls
and parallelising rendering.

I'm preparing to move into product engineering and saw [Company]'s SDE-1
backend opening (Job ID 66104). Would you be open to referring me, or would
you suggest I apply directly? Resume and link below. Thanks!

For the full picture on making this switch, see how to switch from service to product companies.

Referral Request Templates (8–10)

Referral requests deserve special care because you're asking someone to put their name next to yours. The more you reduce their effort and risk, the more likely a yes. The deeper strategy is in our referral guide for product companies.

Template 8: Cold referral request to an engineer you don't know

Hi Divya, I'm a backend engineer with 3 years in Go and PostgreSQL at
[Company]. I'm applying for the SDE-2 Payments role at [Your Company]
(Job ID 90215) and noticed you're on that team.

Quick fit summary: I built our reconciliation service that matches ~1M ledger
entries nightly, and I've worked on idempotent payment APIs.

Would you be comfortable referring me? Job link and resume below. If you'd
prefer to chat first, happy to do a 10-minute call. And no problem at all if
you can't.

Template 9: Referral request to a former colleague or classmate

Hey Nikhil! Hope things are good at [Company]. I'm looking to move and saw an
SDE-2 Data Platform opening on your org's careers page (Job ID 33871). It's very
close to what I've been doing with Spark and Airflow for the last two years.

Would you be okay referring me? I've attached my resume. Also, if you have
10 minutes this week, I'd love your honest take on the team.

Template 10: Asking for a referral after an informational chat

Hi Sanjana,

Thanks again for the chat yesterday. Your explanation of how the team handles
on-call rotations and design reviews made me even more interested.

As we discussed, I'd love to be referred for the Backend Engineer II role
(Job ID 44120). I've updated my resume to highlight the event-driven work you
mentioned would be relevant; it's attached along with the job link.

Thanks for your time,
Harsh

Follow-Up Templates (11–12)

Template 11: Follow-up after no reply (about 7 days)

Hi Neha, just bumping this in case it got buried. Since my last message I've
completed [Company]'s online assessment for the SDE-1 role. Would you be able
to check where my application stands? Thanks!

Note that it adds new information (completed OA). A follow-up that just says "any update?" is weaker than one that gives the recipient a reason to look again.

Template 12: Follow-up after an interview

Subject: Thank you - SDE-2 interviews on 14 Oct

Hi Pooja,

Thanks for coordinating my interviews on Tuesday. I enjoyed the system design
discussion on the notification service, especially the trade-offs around
fan-out on write vs read.

Could you share the expected timeline for next steps? Happy to provide
anything else the team needs.

Best,
Vikram

Send this within a day of the interview. If there's still no update after the timeline they gave, one more polite check-in is fine.

Timing and Cadence: When and How Often to Send

• When: weekday mornings, in the recipient's time zone, are a sensible default so your message is near the top of the inbox at the start of the day. Avoid late-night messages to people you don't know.
• How soon after a job posts: early is better. Many roles get most applications in the first week or two, and recruiters often start screening immediately.
• Volume: 5–10 thoughtful messages a day is sustainable and effective. Fifty copy-paste messages a day tends to produce fewer replies and can trigger platform limits.
• Follow-ups: first after roughly 7 days, second after another 7. Then stop. Mark as "no reply" in your tracker and move on.
• One person per role per company at a time. Messaging five engineers on the same team for the same referral on the same day can look desperate if they compare notes, which in small teams they sometimes do.

Tracking Your Outreach Like a Pipeline

Once you're sending 30–50 messages a week, memory fails. Use a sheet with these columns:

After two or three weeks, calculate reply rate by template and by channel. If alumni referral asks are getting replies and cold recruiter messages aren't, shift your time. You'll also spot which of your proof lines resonate. This feedback loop is the main reason to track, and it's the same discipline described in the off-campus placement strategy for applications.

What to Do When They Reply

A reply is where many people fumble. Respond within a few hours if you can, and keep making things easy.

• If they agree to refer: thank them, confirm the exact job ID, and send anything their referral form needs (resume, email, sometimes a short note on why you fit). Let them know when you hear from the recruiter; referrers like knowing the outcome.
• If they ask for a call: offer two or three specific time slots. Prepare a 60-second introduction and two or three good questions about the team. Our guide on answering "tell me about yourself" helps here.
• If they say there's no role right now: thank them and ask if you can reach out again in a few months, or whether there's another team you should look at. Keep the relationship warm.
• If a recruiter asks for expected CTC early: it's common in India. Give a researched range or ask about the band for the role; see our guide on answering salary expectation questions.

Messages to never send

• "Hi" (and nothing else).
• "Sir please give me job, I am in need."
• Your entire resume pasted into a LinkedIn message.
• Repeated messages every day, or messages to someone's personal number you weren't given.
• Guilt-tripping or pressure ("I've messaged you three times").
• Anything you'd be uncomfortable seeing forwarded to the hiring manager. Assume it might be.

Good outreach is a skill, and like any skill it improves with feedback. Use the structure, personalise the hook and proof every time, track your results, and within a few weeks you'll know exactly which messages work for your profile.

Frequently Asked Questions

Pranjal Jain

Ex-Microsoft SDE · IIT Kanpur · Founder of Prepflix. Helps engineers crack startup and product company interviews across India.