Cold Outreach That Doesn’t Suck

Every student running an internship search sends roughly the same cold message. It looks like this:

Hi [Name], I hope this email finds you well. My name is [You] and I’m a junior at [School] majoring in Computer Science. I came across [Company] and was very impressed by the innovative work being done. I would love to learn more about opportunities and how I might contribute. I have attached my resume for your reference. Looking forward to hearing from you!

This message is a black hole. Recruiters and engineers get fifteen of these a week. They don’t reply. They might not even open it. Worse — over time, they associate “[School] junior” with this template, which means the next student from your school who reaches out also gets ignored.

Here’s what actually gets a reply.

The four parts that matter

A cold message is short. It does four things and then stops:

1. A subject line that’s not “Quick question” 2. An opener that proves you’re a real person who picked them on purpose 3. A specific, small ask 4. A polite exit

That’s it. No “I hope this finds you well.” No bio paragraph. No attached resume. No “I would love the opportunity to leverage my passion for innovative solutions.”

Subject lines

Bad subjects every recruiter has muted: “Quick question”, “Internship inquiry”, “Reaching out”, “Hello”.

What works: short, specific, and about them or their work. Some that have actually gotten replies:

• Question about your team’s switch to Rust
• CMU junior — your 2024 talk on incident response
• 2-min question about the data infra role

The recruiter or engineer should be able to read the subject and know within a second why you specifically wrote them and what you want.

The opener (this is the whole game)

There are three opener types, ranked by reply rate.

Tier 1: Connection

You share a real connection. Same lab, same advisor, mutual friend, same class. Real connection — not “we both went to Stanford” if Stanford has 17,000 students.

Hey [Name] — I work in Professor Liu’s lab too. She mentioned you graduated last year and now do platform work at Stripe.

This is a 60%+ reply rate opener. Use it whenever you have it. If you don’t have it, don’t fake it.

Tier 2: Context

You read their work and have a specific reaction to a specific thing they did. Their public talk, their PR comment on a popular OSS repo, their blog post, their company’s recent launch.

Watched your talk at Strange Loop on building durable workflows. The bit about idempotency keys at the database layer (vs application layer) made me rethink a side project I’m working on.

Note the specificity — not “I loved your talk”, but the specific moment in the talk that landed. This is hard to fake and recruiters can tell when it’s been faked. Worth the 15 minutes of actual research.

Tier 3: Curiosity

You have a real question about their work that you can’t easily answer with Google. Not “what’s it like working at [Company]” — that’s a Glassdoor question and you’ve insulted them by asking. A real, technical, narrow question.

Curious — when your team migrated to gRPC, did you keep REST endpoints up in parallel during the cutover or do a hard switch? Asking because I’m doing something similar at smaller scale and the dual-stack maintenance is killing me.

This works because it treats them like a peer with expertise, not a gatekeeper with a job to give you. Sometimes they reply with the answer and never get to the “and by the way I’m looking for an internship” part — that’s fine, you’ve now started a relationship.

The ask

Ask for one specific small thing. Not “an opportunity at your company”. Specific small things that work:

• A 15-minute call to ask 3 questions
• An honest read on whether your background fits the [specific team] hiring bar
• A pointer to whoever is closest to the [specific role] hiring decision

What does not work: “Can you refer me?” Asking for a referral as the first ask is a known pattern and recruiters route those messages to /dev/null. Referrals come after a real conversation, not before.

What sounds like a tool-user

Recruiters and engineers can spot AI-shaped writing instantly now. Tells:

• “I hope this email finds you well.”
• “Leverage”, “synergy”, “innovative”, “passionate about”, “actionable insights”.
• Sentences that all have the same rhythm and length.
• Bullet points where there shouldn’t be bullet points.
• Cover-letter voice in a DM.

Write the way you talk. If you wouldn’t say “I am very interested in the opportunity to leverage my background” out loud to a friend, don’t put it in an email. “I want to work on infra and your team is the closest fit I’ve seen” is a sentence a person would say.

Following up

One follow-up after 5 business days. Not “checking in” — restate the ask in fewer words. If they don’t reply to the follow-up, move on. They didn’t reply because they’re busy or not interested, both of which are fine, and a third nudge moves you from “polite student” to “spam”.

A working template

This is the structure, not the words. Don’t copy it verbatim — adapt it.

Subject: [Specific thing about their work]

>

Hey [Name] — [one-line specific opener: connection, context, or curiosity].

>

[One line about why you specifically: school, year, the thing you’re working on right now that’s relevant. No bio paragraph.]

>

[The specific small ask, one sentence.]

>

Thanks either way — I know you’re busy.

>

[You]

Three paragraphs, maybe 80 words. If your draft is over 150 words, cut it in half and send the shorter version.

The frame change

Cold outreach feels like begging when you write the begging template. It stops feeling like begging when you treat it as starting a real conversation with a peer about their work. The reply rate goes up. The conversations are better. Sometimes you get the internship; more often you get a useful relationship that pays off two cycles later.

Send fewer, better messages. Twenty good ones beats two hundred bad ones, and your blacklist stays clean.