60% of software engineering roles at funded Indian startups are filled before they're publicly posted — through referrals, LinkedIn InMails, and yes, cold emails to the right people. The difference between a cold email that gets ignored and one that gets a reply comes down to three things: who you email, what you say, and when you follow up.
Who to Email: The Right Person Changes Everything
Most candidates make the mistake of emailing HR. HR at a 100-person startup receives 200+ cold emails a week and has a low signal-to-noise ratio on technical fit. Instead, email: the engineering manager of the team you'd join (they feel the pain of an open role directly), a senior engineer on the team (they get fewer cold emails and are often happy to refer strong candidates), or the CTO/VP Engineering at companies under 50 employees (small enough that founders care about every hire).
How to find the right person: LinkedIn (search 'engineering manager at [company]'), the company's engineering blog (authors are usually engineers or EMs), GitHub (contributors to the company's open-source repos), and Twitter/X (many Indian tech leads are active). Use Hunter.io or Rocket Reach to find email formats once you have the name.
The Anatomy of a Cold Email That Gets Replies
Subject line: specific and personal. 'Software Engineer with Node.js + AWS background — interested in [Company]' beats 'Job Application' or 'Exploring Opportunities.' Make them curious, not confused.
Opening line: don't start with 'I'. Start with them. 'I've been following [Company]'s engineering blog — the post on how you scaled your notification system to 10M users was excellent.' This proves you did homework and isn't fake flattery — you actually read something specific.
The body (3-4 sentences max): What you do, what you've built (one concrete example with a metric), why you're interested in them specifically (not just 'great company'), and a single clear ask — not 'please give me a job' but 'would you have 20 minutes to chat about your team's roadmap?'
Closing: attach your resume or link your portfolio/GitHub. Make it trivially easy for them to evaluate your skills before they decide whether to reply.
Template: Cold Email to an Engineering Manager
Subject: Node.js + AWS engineer interested in [Company]'s backend team
Hi [Name],
I've been using [Product] for a while and was really impressed by how you handle [specific feature/scale challenge]. I read your engineering blog post on [specific topic] — it changed how I think about [concept].
I'm a backend engineer with 2 years of experience building services in Node.js and TypeScript. Most recently I built a payment reconciliation service that processed ₹2 crore/day with 99.9% uptime — I'd be happy to show you the architecture.
I'm looking for my next role and [Company] is at the top of my list because of [specific reason — team, product, tech stack, problem domain]. Would you have 20 minutes for a quick call in the next few weeks? No pressure at all if the timing isn't right.
[Your name] | [GitHub] | [Portfolio]
---
Why this works: it's specific (not generic), it demonstrates you've done research, it leads with a concrete achievement, the ask is low-commitment (20 minutes, not 'hire me'), and it's short enough to be read in 30 seconds.
Template: Cold Email to a Senior Engineer for a Referral
Subject: Same college + interested in [Company] — quick question
Hi [Name],
I came across your profile while researching engineers at [Company]. I noticed we both went to [College/Institute] — small world!
I'm currently a [role] with [X years] experience in [tech stack]. I'm genuinely excited about [Company] because [specific reason] and I'd love to apply for a [role] position.
I know you're busy — my only ask is: if you think I'd be a reasonable fit, would you be open to referring me? I've attached my resume so you can decide in under 5 minutes whether it's worth it. Completely fine either way.
Thanks for your time, [Name].
---
Common connection emails (same college, same hometown, mutual connection) have significantly higher response rates than cold emails with no shared context. Use LinkedIn's alumni feature to find these connections at your target companies.
Following Up Without Being Annoying
Send one follow-up email 5-7 days after the first email if you get no response. Don't start with 'I'm just following up' — that's weak. Lead with new value: 'I deployed the side project I mentioned — here's the link if you want to see it. I'd still love to connect if there's a good time.'
If still no reply after the second email, move on. Don't send a third email — it crosses into harassment territory and they'll remember you negatively. Instead, try a different person at the same company.
Response rate benchmarks for context: a well-crafted cold email to the right person typically gets a 15-25% response rate. HR cold emails get 3-5%. Warm emails (mutual connection or common context) get 35-50%. Even at 15%, if you send 20 targeted cold emails per week, you're generating 3 new conversations per week — far better than only applying through job portals.