Cold Outreach Templates for Students in Tech
You send twenty messages. Your inbox stays quiet. That is not a verdict on your worth. Inboxes reward relevance, small batches, and a clear ask someone can answer in one sitting. Measure success by replies, not opens. Baseline reply rates for cold email stay low for almost everyone, so the game is fewer sends with real context, not a longer autobiography.
Batch size and who to email
Cap each wave at roughly fifty to a hundred active targets, or smaller if you are still learning your voice. That cap keeps personalization honest.
At big companies, a university recruiter or university programs contact is often the fastest first door; at startups, a founder or early engineer may actually read mail. If you are not sure who owns hiring for interns, search the company site and LinkedIn for titles that include campus, university, early career, or talent, then pick one person and commit.
Message length and subject lines
Keep the first touch around a hundred to a hundred twenty-five words. Lead with proof you exist: a course, a project link, a club role. Spend the next lines proving you read their work: a launch, a post, a talk, a product detail. End with a low-friction ask, usually a fifteen-minute advice chat, not a demand for a job in sentence one.
Subject line pattern that survives skimming: [Your school + stack signal] + [specific team or product hook] + [Company].
Template A: LinkedIn connection note
300 characters max on many flows.
Hi [Name], [Year] at [School], [stack or project one-liner]. I read [specific thing they published or shipped] and I am trying to learn [narrow skill]. If you accept, I will send a short note with one question. Thanks, [Your name]
Template B: Cold email #1
Subject: [CS @ School | stack] - question on [Team/Product] at [Company]
Hi [Name],
I am [year + major] at [School]. I have been building [one project] ([link]), and I am interested in how [Company] approaches [specific problem their team owns].
Your [post / release / talk on X] made me think about [one concrete takeaway].
Would you be open to a fifteen-minute Zoom or phone chat in the next two weeks? I will send three questions ahead so you can skim.
Thank you for your time, [Your name] [.edu or clean email] | [GitHub or portfolio link]
Template C: Follow-up #1
Add one new detail; do not resend the same block.
Subject: Re: [prior subject]
Hi [Name],
Following up once. I tried [brief experiment tied to their work: benchmark, small prototype, reading], and it surfaced [one sentence insight].
If timing is bad, a two-line pointer to someone else on the team would still help.
[Your name]
Template D: After a career fair or summit
Subject: Great to meet you, [School] / [Company]
Hi [Name],
Thank you for talking with me [where: booth, session name]. I appreciated what you said about [specific detail from the conversation].
I am [year + focus] and I am deciding [one narrow decision: team fit, project direction, how to prep for X].
Would a fifteen-minute call work, or is email easier for you?
[Your name]
Warm lanes (when they are true)
Warm lanes shrink how cold you have to be. If it is true, say it in the first sentence: ColorStack at Northeastern (Khoury lists the chapter as ColorStack @ Northeastern University; the student hub lives at linktr.ee/colorstackneu), Code2040 programs, MLT Career Prep, or a real event where you met them. Those lines increase relevance without inventing affinity.
Send three real messages this week
The failure mode is the same template blasted wide with only the name swapped. It reads like spam, burns time, and pushes your voice toward generic.
Send three messages in the next twenty-four hours. Aim each at a high-fit person with one line you could not have written without opening their profile or product page, and close with the same small ask: fifteen minutes, or one pointed question they can answer in email.