← Back to Blog

How to Cold Email for a Software Engineering Internship (With Templates That Actually Work)

Published ยท Finch Team

Updated

Everyone knows about LinkedIn Easy Apply. What most students don't know is that a large share of internships at smaller companies never get posted publicly. They get filled through referrals, career fairs, and (yes) cold email.

Cold email for internships has a bad reputation because most students do it wrong. They send a generic "I'm a CS junior looking for opportunities" message to an HR email address and wonder why nobody responds. Done right, cold email is one of the most effective moves in a student job search.

This post is about doing it right.

Why Cold Email Works for Internships Specifically

Cold email works better for internships than for full-time roles for a few reasons.

Internship headcount is often flexible. A startup or mid-size company that wasn't planning to hire an intern might take one if a strong candidate shows up at the right moment. Full-time hiring is more tied to approved headcount and formal processes.

Engineering managers and tech leads at smaller companies often prefer proactive candidates. If a junior dev shows up in someone's inbox having already looked at their open-source repos or blog posts, that signals the kind of initiative that makes a good intern.

The competition is also lower. Your classmates are all applying to the same 50 posted internships. Very few are sending cold emails. You're not competing in that pool.

Who to Contact (This Part Matters a Lot)

Do NOT email the generic company contact address or HR mailbox. Your email will sit in a queue with hundreds of others and get auto-archived.

Who to email instead:

Engineering managers at mid-size companies are often the best first target. They're the ones who feel the pain of being short-staffed and have the authority to say "yeah, bring in an intern."

Software engineers with 3-7 years of experience. They're senior enough to have pull, but junior enough to still remember what it was like to need a break. They're often more responsive than very senior engineers who get more cold outreach.

Founders at startups. If the company is 5-20 people, the founder probably still writes code or at least cares deeply about who does. A well-targeted cold email to a startup founder sometimes gets a same-day response.

How to find them: LinkedIn. Search the company, filter by "Engineering" department, and look for people with those titles. Or check their GitHub if the company has open-source work: contributors are listed there and you can often find email addresses in commit signatures.

The Anatomy of a Cold Email That Gets Replies

Your cold email should be short. Under 150 words. You're asking for their time, so don't waste it.

Here's the structure:

  1. Who you are (one sentence, specific)
  2. Why you're reaching out to THEM (one sentence, specific to this person or company, not "I love your company's mission")
  3. What you've built that's relevant (one or two lines, include a link)
  4. A clear, low-friction ask

Let's see this in practice.

Template 1 (engineering manager target):

Subject: CS junior at [School], interested in a summer internship

Hi [Name],

I'm a CS junior at [School] focusing on backend systems. I read your post about [specific technical topic from their blog or GitHub], and it reminded me of a similar problem I ran into when building [brief project description].

I've been working on a distributed key-value store in Go that handles [X] operations/second under load testing. The code is at [GitHub link].

I'd love to explore whether there's room for a summer intern. I'm not expecting a formal program. Even an informal arrangement where I could contribute to [specific team or project] would be really valuable.

Thanks for your time. [Your name]

Notice what this does: references something specific to them, shows real work via GitHub link, and the ask is low-pressure.

Template 2 (startup founder target):

Subject: CS sophomore interested in contributing to [Startup Name]

Hi [Name],

I'm a CS sophomore who's been building in [relevant stack]. I found [Startup Name] while working through [specific problem your startup solves] and read through how you handle [specific technical detail from their docs or a post].

I built [brief project] using [tech stack] and it's live at [link]. I'm looking to contribute to a product at an early stage this summer, even in a limited capacity.

Would a short call make sense?

[Name]

With a founder, lead with the problem they're solving, not your credentials. Founders care about people who genuinely understand their problem.

The Subject Line Problem

Most cold email subject lines are terrible. "Software Engineering Internship Inquiry" sounds like a form letter.

Good subject lines are direct and specific:

  • "CS junior at [School], [1-2 word tech specialty] focus"
  • "Interested in interning with [Team Name] this summer"
  • "Saw your [blog post / GitHub repo]: question about [specific topic]"

The third style is best when you can make it genuine. If you actually watched their conference talk or read their technical post, referencing it in the subject line differentiates you immediately.

Following Up

If you don't hear back after 5-7 business days, send one follow-up. Just one.

Hi [Name],

Following up in case this got buried. Happy to send more about my background if helpful.

[Name]

Four sentences is plenty. Do not write a second pitch. Do not apologize for following up. Do not send a third email.

If they don't respond to the follow-up, move on. Some people genuinely don't have bandwidth, and some companies genuinely don't hire interns. No response isn't feedback on your qualifications.

Targeting Your Cold Email List

Don't spray 200 emails at once. It doesn't work and you'll run out of personalization quickly.

A sustainable rhythm: identify 5-10 target companies per week. Find one or two people at each. Write a personalized email for each person. Send. Follow up after a week. Track results.

Do this consistently for 4-6 weeks and you'll have reached 40-80 people. Even a 5% positive response rate gives you 2-4 real conversations per month, far better than staring at job boards waiting for cold applications to convert.

What makes a company a good cold email target:

  • 20-200 employees (large enough to potentially take interns, small enough for your email to matter)
  • Active engineering blog or GitHub presence (you'll have something specific to reference)
  • Not actively posting a lot of formal internship roles already (if they were, you'd just apply normally)

To check that last point, search the company on Finch's board, which lists open internships and new-grad roles. If there's a posting, apply to it first and use your email to follow up on that application.

Connecting Cold Email to Your Application Pipeline

When you land a warm response from cold outreach, you'll often need to quickly send a tailored resume. Have one ready. Your resume should highlight work relevant to their tech stack: if they're a Python shop and your resume leads with Java projects, swap in the relevant work.

Keep two or three base versions of your resume, one per kind of stack, so tailoring is a quick swap. When a cold email actually lands and someone says "can you send your resume?", you want to respond the same day with something targeted, not a generic PDF from three months ago.

For the broader application strategy alongside cold outreach, read our post on how to apply to more jobs faster.

Cold Email Checklist

Preparation (per batch of 5-10 companies):

  • Identify 5-10 target companies: 20-200 employees, tech-forward, active online presence
  • For each, find 1-2 names (engineering manager or mid-level SWE)
  • Find their email: LinkedIn, GitHub commit signatures, personal site, or common format guess (first@company.com)
  • Read something specific about each person before writing to them

Per email:

  • Subject line is specific, not "Internship Inquiry"
  • First sentence: who you are, one sentence
  • Second sentence: why this specific person / company
  • Link to something you built
  • Ask is low-friction and specific ("would a short call make sense?")
  • Total email is under 150 words
  • Proofread for typos before sending

Follow-up system:

  • Log every email sent with the date
  • Set a calendar reminder for 7 business days after each send
  • If no response, send one short follow-up only
  • If no response to follow-up, move on

Cold email is uncomfortable at first. After the tenth one it becomes mechanical. After the first response it becomes clearly worth the effort.