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.
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.
The Best Time to Send Cold Emails in India
Timing matters more than most people realize. Data from outreach tools like Mailshake and Lemlist (averaged across thousands of B2B campaigns) shows that emails sent between Tuesday and Thursday, 10 AM to 11:30 AM IST get the highest open and reply rates. Avoid Mondays (inbox overflow from the weekend) and Fridays after 2 PM (everyone's mentally checked out).
For senior folks like CTOs and VPs at Indian startups, early morning emails (7 AM to 8:30 AM IST) often work surprisingly well. Founders at companies like Razorpay, CRED, and Zepto are usually clearing their inbox before standups start. Your email lands at the top instead of buried under 80 other messages by 11 AM.
Avoid sending on Indian festival weeks (Diwali, Holi, end-of-December holidays) — replies drop by 40-50%. Also avoid the last week of every quarter (March, June, September, December) — engineering managers at funded startups are buried in OKR reviews and hiring planning. The first two weeks of a new quarter are gold — budgets refresh, hiring plans open up, and EMs are actively thinking about who to bring in.
One more nuance: if you're targeting product-led startups (Postman, Freshworks, Zoho), Wednesday mid-morning works best. For fintech and B2C startups (PhonePe, Groww, Meesho), Tuesday mornings work better because Monday is firefighting day for them. Track your own data after 30-40 emails and adjust.
Cold Email Mistakes That Kill Your Reply Rate
Some patterns guarantee your email gets deleted in 2 seconds. Here's what to never do:
Mistake 1: The wall of text. If your email is longer than 150 words, most engineering managers won't read past line 3. Cut ruthlessly. One achievement, one reason for interest, one ask. That's it.
Mistake 2: Listing every skill you have. Writing "I know Python, Java, C++, Go, Rust, JavaScript, TypeScript, React, Vue, Angular, AWS, GCP, Azure, Kubernetes, Docker, Terraform..." screams junior. Senior engineers list 2-3 things they're genuinely strong in. Quality beats quantity. Before sending, check ATS score on your attached resume to make sure your skills section is actually relevant to the role.
Mistake 3: Asking for "any opportunity." Vague asks get vague responses (usually silence). "I'm open to any role" tells the reader you haven't thought about what you want. Instead say: "I'm specifically interested in your payments infrastructure team because of the scale challenges you've written about."
Mistake 4: Forgetting the homework. If you can't name one specific thing about the company — a product feature, a blog post, a recent funding round, a tech choice they made — don't send the email. Spend 15 minutes reading their engineering blog or scrolling their Twitter. Generic emails get generic ignores.
Mistake 5: No social proof or link. Always include a GitHub link, portfolio URL, or one impressive deliverable. If your GitHub is empty and you have no portfolio, fix that before sending cold emails. Reading "I built X" without proof feels hollow.
Mistake 6: Salary or relocation demands upfront. Never mention compensation, notice period, or relocation in the first email. That's a third-conversation topic. If you want to benchmark salary before negotiations later, do it privately — don't put numbers in the cold email itself.
What to Do After You Get a Reply
Getting a reply is only step one. Most candidates fumble the next 48 hours. Here's the playbook:
Reply within 4 hours. Engineering managers are busy — if you take 2 days to respond, momentum dies. Even if you can't write a full reply immediately, send a quick "Thanks so much, [Name]! I'll send over times for a call by tonight" within 4 hours.
Suggest 3 specific time slots, not "whenever works." Saying "I'm flexible" puts the scheduling burden back on them. Say: "Would Tuesday 11 AM, Wednesday 4 PM, or Friday 10 AM IST work? Happy to adjust if none of these suit." This shows respect for their time.
Prepare for the call like an interview. Even if they call it "an informal chat," treat it as a screening round. Research the team, the product, recent news, the interviewer's background. Have 3 thoughtful questions ready about their roadmap, team structure, or biggest engineering challenges. And practice interviews for behavioral questions — they almost always sneak one in ("tell me about a project you're proud of").
Send a thank-you within 24 hours of the call. Reference one specific thing they said. Reiterate your interest. Attach anything you promised (code sample, portfolio link, references). This single email moves you from "interesting candidate" to "follow up with HR."
If they refer you internally, send a follow-up thanking them after the recruiter contacts you. Engineers who refer often get ₹50,000 to ₹2 lakh in referral bonuses at Indian startups if you get hired — they're invested in your success. Keep them posted at each round so they can advocate for you internally.
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.
Scaling Your Cold Email Strategy Without Becoming a Spammer
Once you've mastered single emails, you can scale carefully. Aim for 15-25 cold emails per week — enough to generate momentum, not so many that quality drops. Track every email in a simple Google Sheet with columns: company, person, role, date sent, date follow-up sent, response, status, notes.
Build a target list of 50-100 companies at any given time. Tier them: Tier 1 (dream companies — spend 30 minutes per email), Tier 2 (strong fit — spend 15 minutes), Tier 3 (worth exploring — spend 10 minutes). Don't waste premium effort on lower-tier targets, but don't send garbage to anyone either.
Use templates as starting points, not endings. A reusable skeleton (intro, achievement, why-them, ask) is fine — but the specific company details, blog post references, and personalized hooks must be unique per email. Hiring managers can spot a copy-paste from 30 feet away. One Indian startup CTO I spoke with said he receives roughly 400 cold emails a month and replies to maybe 12 — and every single reply went to an email that mentioned something specific about his company.
Also browse jobs on listing platforms in parallel — sometimes the same company you're cold emailing has a posted role you can apply to officially, which combined with your cold outreach doubles your chances. Cold email gets you internal attention; the application gives them the official paperwork to move forward.
Finally, batch your work. Pick one afternoon a week (Sunday evenings work well) to research targets and draft emails. Schedule sends for Tuesday-Thursday mornings. This way, cold outreach doesn't drain your weekday energy and becomes a sustainable habit instead of a desperate scramble.
Frequently Asked Questions
How long should my cold email actually be?
Aim for 120-150 words maximum in the body, plus a short subject line. Engineering managers and senior engineers read cold emails on their phones between meetings — anything longer than what fits on one mobile screen gets skipped. The structure should be: one-line hook showing you did research (1 sentence), what you do and one concrete achievement with a number (2 sentences), why their company specifically (1 sentence), a low-commitment ask like "20-minute chat" (1 sentence), and your signature with links. If you need more space, you're either rambling or trying to close them in one email — which never works. Save the details for the actual call.
What if I have no relevant experience or just graduated?
Lead with what you've built, not what jobs you've held. A strong GitHub portfolio with 3-4 real projects (not tutorial clones), a working side project deployed on a free Vercel/Railway tier, or contributions to open-source repos all count as legitimate proof of skill. Mention hackathons, freelance projects, or college capstones with specific outcomes ("built an attendance system used by 400 students at my college"). Recruiters at Indian startups like Razorpay, Zerodha, and Postman have explicitly said they hire fresh grads who show initiative through projects over those with generic resumes. Skip the "I'm a hardworking learner" cliches — show, don't tell.
Should I send cold emails to FAANG companies or only startups?
Cold emails work much better at Indian startups with under 500 employees than at FAANG. At Google, Amazon, or Microsoft India, hiring is process-driven through recruiters and there's almost no shortcut via cold email — managers can't fast-track candidates outside the formal pipeline. At funded Indian startups (Series A through D), founders and EMs have real hiring authority and can pull you into a process directly. So focus cold outreach on companies like Razorpay, CRED, Zepto, Meesho, Postman, Freshworks, and similar — where one good email to the right EM can lead to an offer in 3 weeks. For FAANG, use referrals and the official application process.
How do I find someone's email address if it's not on LinkedIn?
Three tools dominate this in India: Hunter.io (10 free searches per month, finds email patterns for company domains), RocketReach (5 free credits, very accurate for Indian professionals), and Apollo.io (50 free credits, great for B2B contacts). Pattern-guessing also works — most Indian startups use firstname@company.com or firstname.lastname@company.com. Use a tool like Gmail's "Mailtrack" to confirm if your email was opened (proves you got the right address). If the person has a personal website or GitHub, their email is often listed there directly. For founders and CTOs, Twitter DMs are sometimes more effective than email — many Indian tech founders are responsive on Twitter but ignore their inboxes.
Bottom Line
- Email engineering managers and senior engineers directly, not HR — response rates are 3-5x higher
- Keep emails under 150 words with one specific hook proving you researched the company
- Lead with one concrete achievement and a metric (₹X processed, Y% improvement, Z users served)
- Send Tuesday-Thursday between 10 AM and 11:30 AM IST for best open rates
- Follow up once after 5-7 days with new value — never send a third email
- Aim for 15-25 targeted cold emails per week with a tracked spreadsheet; expect 15-25% reply rate when done right