How to Write a Cold Email for an Internship in India (With Templates That Get Replies)
Why cold emails are worth the effort
Most internships in India are filled through college placement cells, referrals, and job portals where a single posting attracts thousands of applicants. Cold emailing bypasses all three.
It works for a structural reason: small and mid-sized companies, startups and individual researchers frequently need help but have no formal internship pipeline. They aren't posting anywhere. When a capable student emails them directly at the right moment, there is no competition at all — you're not one of 2,000 applicants, you're the only one.
Before you write: ten minutes of research
This step is what separates emails that get replies from emails that get deleted. For each target:
- Find a real person, not an address.
careers@andinfo@go to inboxes nobody owns. Find the engineering lead, the founder, the research head, the marketing manager. - Find their actual email. Company sites, LinkedIn, research paper footers, conference pages, GitHub profiles. Many Indian companies use
firstname@company.comorfirstname.lastname@company.com. - Find one specific thing — a product they shipped, a paper they wrote, a talk they gave, a problem they've discussed publicly. This is the sentence that proves you're not mass-mailing.
The structure
1 Subject line — specific, not clever
❌ "Internship Opportunity" · "Seeking Internship" · "Request for Internship — Resume Attached"
✅ "Backend intern — built an order API, available from June"
✅ "Your paper on crop yield prediction — final-year student with related work"
The subject decides whether the email is opened. It should say what you are and what you want in plain words.
2 First line — about them, not you
Almost every student email opens with "I am a final-year student at…". The reader has seen that line hundreds of times and it tells them nothing.
Open with the specific thing you found:
"I read your post about moving your payments service off the monolith — the part about handling partial failures during migration was the clearest explanation of that problem I've found."
This is the hardest sentence to write and the one that does the most work.
3 Who you are — one sentence
"I'm a final-year Computer Science student at [college], working mainly in backend development."
One sentence. No more.
4 Proof — one concrete thing, with a link
Not a list of skills. One specific thing you built, with a link so they can verify in ten seconds.
"I built an order management API handling inventory and payment states — it's running here [link], and the code is here [link]."
A link they can click beats any adjective. "Hardworking", "passionate" and "quick learner" carry no information.
5 The ask — small and easy to say yes to
❌ "Please give me an internship in your esteemed organisation."
✅ "Do you take interns over the summer? Happy to start with a small piece of work so you can see how I do before committing to anything."
The second is far easier to say yes to. You've reduced their risk to nearly nothing, and you've made the decision small.
Full templates
Template 1 — to a startup engineer or founder
Subject: Backend intern — built an order API, available from June
Hi [Name],
I read your write-up on splitting the payments service out of the monolith. The section on handling partial failures mid-migration was genuinely useful — most explanations skip that part.
I'm a final-year CS student at [college], focused on backend work. I built an order management API that handles inventory and payment state transitions — it's live at [link] and the code is at [link]. It's small, but it's the same class of problem.
Do you take interns over the summer? I'd be glad to start with a small, scoped task so you can see the work before committing to anything.
Either way, thanks for writing that post.
[Name] · [phone] · [LinkedIn]
Around 130 words.
Template 2 — to a professor or researcher
Subject: Your paper on [topic] — final-year student with related project
Dear Professor [Name],
I read your paper on [specific topic]. The approach you took to [specific detail] was what I kept coming back to — I'd been trying something similar in a course project and hadn't considered handling it that way.
I'm a final-year [branch] student at [college]. I built [project] using [methods], which is at [link]. My background is in [relevant coursework].
Are you taking project students or research interns this term? I'm available from [date] for [duration], and I'd be happy to work on something small initially.
Thank you for your time.
[Name] · [college] · [phone]
Template 3 — non-technical role
Subject: Content intern — wrote 15 articles, 2 ranking on page 1
Hi [Name],
I've been following [company]'s blog — the piece on [specific article] was unusually practical compared to most writing in that space.
I'm a final-year student at [college] and I write regularly at [link]. Two of my articles rank on the first page for their target keywords, and I handle my own keyword research and on-page SEO.
Are you looking for content interns? I'd be happy to write one sample piece on a topic of your choosing, unpaid, so you can judge the fit directly.
[Name] · [portfolio] · [phone]
What guarantees silence
| Mistake | Why it kills the email |
|---|---|
| "Respected Sir/Madam" | Signals a mass email immediately |
| "Esteemed organisation" | Same. Write like a person. |
| 400+ words | Won't be read on a phone between meetings |
| Listing twelve skills | No evidence. One link beats twelve adjectives. |
| Attaching a resume with no context | Attachments from strangers often go unopened. Link instead. |
| No specific detail about them | Proves you sent the same email to 200 people |
| Asking for a large commitment upfront | Too much risk for a stranger to accept |
Sending to info@ | Nobody owns that inbox |
Following up
Most replies come after a follow-up, not the first email. Silence usually means the email arrived on a busy day, not that the answer is no.
- Wait 5–7 working days before the first follow-up.
- Reply in the same thread so they have the original context.
- Keep it to two lines. "Hi [Name], just moving this up your inbox in case it got buried. Happy to hear either way."
- Follow up once. Maybe twice. Then stop. Persistence past that point damages your reputation rather than your odds.
The honest summary
Cold emailing works because almost nobody does it properly. The students who do it badly send 300-word templates to info@ addresses and conclude it doesn't work. The students who do it well send twenty researched, short, specific emails and get two or three real conversations. The whole method reduces to four things: find a real person, mention one real detail, show one real piece of proof, and ask for something small. Then send enough of them that the reply rate has a chance to work in your favour.
Frequently Asked Questions
Do cold emails actually work for internships in India?
Yes, particularly with startups, small companies and individual researchers who need help but have no formal internship process. Reply rates of 10–20% are normal for well-researched emails. The main reason students conclude it doesn't work is sending too few — three emails is not a test, twenty is.
How long should a cold email for an internship be?
Under 150 words. It should be readable on a phone in under thirty seconds. Long emails from strangers are postponed and then forgotten. Everything beyond the specific opening line, one sentence about you, one piece of proof and one small ask can be cut.
Should I attach my resume to a cold email?
Generally no, not on the first email. Attachments from unknown senders are frequently left unopened and can affect deliverability. Link to a portfolio, GitHub repository or LinkedIn profile instead, and offer to send the resume if they're interested.
How many times should I follow up?
Once after five to seven working days, and optionally a second time a week after that. Reply in the same thread and keep it to two lines. Beyond two follow-ups you're no longer improving your odds and are damaging the impression you leave.
What should I do if nobody replies at all?
Check the volume first — if you've sent fewer than fifteen, you haven't tested the method. If you've sent thirty with no replies, the problem is usually the opening line being generic, the email being too long, or sending to role-based addresses rather than named individuals. Rewrite the first two sentences before sending more.
📚 BrainBuzz explains India — careers, money and the things nobody teaches you.
Comments
Post a Comment