Cold email to recruiters and managers¶
For students and engineers with 0 to 3 years of experience. You leave with a target list, seven templates, a send schedule, and a pre-send checklist.
Tip: A cold email sends people to your resume and LinkedIn. Finish your resume checklist and LinkedIn profile first, and check visa sponsorship before you spend an email on a company.
Your first week¶
- Pick 20 to 30 companies, each with 1 to 3 live job IDs. Apply to the roles first (application strategy).
- For each company, find one hiring manager or engineer on the exact team (finding people).
- Find and verify each address (see Find and verify the address).
- Write one personal line per person: something they built, wrote, or posted.
- Fill template 1 or template 3. Run the pre-send checklist.
- Send 5 this week, scheduled for 9 AM their time. Log each one in your tracker with a follow-up date 5 business days out.
Where cold email fits¶
I sent around 700 applications for my first US role and got 3 interviews. What fixed it was talking to people at the companies, not a better resume (7 videos on networking your way to offers).
The data agrees on who to email and who to skip:
| Channel | What the data says | Source |
|---|---|---|
| Referral from someone who knows you | 40% of referred candidates reach an interview, vs 3% of inbound applicants | Ashby referral report (May 2025, 38M+ applications) |
| Cold email to a hiring manager | Net positive at FAANG and FAANG-adjacent companies | interviewing.io, part 1 |
| Cold email to a recruiter, before you apply | Net negative at FAANG unless you already fit what they source for | Same survey |
| Cold referral ask to a stranger | Net negative at FAANG and small startups | Same survey |
The interviewing.io sample skews experienced (average about 8 years), and the post says recruiters are not incentivized to help candidates with under 4 years of experience. For students, recruiter email works in one case: after you apply, with the job ID, to a university recruiter.
Who to email, in order¶
| Person | What they control | What you ask for | Notes |
|---|---|---|---|
| Hiring manager (EM, SDM) on the exact team | Headcount and who interviews | A 15-minute chat about the team | interviewing.io: prefer managers in the role under 2 years, and use email, not LinkedIn |
| Engineer or alum on the team | Can submit a referral | Advice first, referral after a real conversation | See referrals |
| University or early-career recruiter | Intern and new grad pipelines | Confirm your application is seen, ask the timeline | Only after you apply. Put the job ID in the subject |
| Professor, lab manager, grad student | Research internships, TA roles, intros | A short meeting or a TA slot | Grad students and lab managers often do the shortlisting (The $0 Masters in the US) |
| Founder or CTO at a seed or Series A startup | The whole hiring decision | A call about the role | Startups read applications if you are early (How I Got My First Startup Offer in 17 Days) |
Find names, titles, and profiles for each row with finding people.
The rules, with numbers¶
| Rule | Number | Source |
|---|---|---|
| Length of the body | 50 to 125 words | Boomerang, 40M emails |
| Subject length | 3 to 4 words did best; stay under 7 | Boomerang; Jugal's Referral Engine prompt caps subjects at 7 words |
| Questions | 1 to 3. Zero questions gets fewer replies | Boomerang |
| Reading level | Plain words. Third-grade level got a 36% lift over college level | Boomerang |
| Personal line | One specific thing they built, wrote, or posted | Jugal, networking post |
| Template reuse | Change at least one line so it is about them | Jugal, same post |
| Links | 1 to 2 (LinkedIn, GitHub or site). No attachment on a first email to a manager | interviewing.io, part 2 |
| The ask | A 15-minute call "this week or next", with two time windows | interviewing.io, part 2 |
| People per company per wave | 1 to 2 (+46% reply rate vs more) | Hunter, 31M emails |
| Touches per person | 3 total (first email + 2 follow-ups) | Hunter; Jugal ("twice max") |
| Daily volume | 10 to 15 personal emails in a 10-minute block | The Job Hunt I Didn't Burn Out Doing |
Watch out: In Hunter's 2026 report, 69% of decision makers said it bothers them if AI was used to write an email. Hand edits lifted replies by 18%. Use AI for a draft, then rewrite the personal line yourself.
Subject lines that work¶
The subject tells the reader why you wrote. Use 3 to 7 words, and make sure the email delivers what the subject says.
| Weak | Strong | Why the strong one works |
|---|---|---|
| Hi | Quick question about Payments at Stripe | Names the team; a small ask |
| Job opportunity | Summer 2027 SWE Intern applicant, Job ID 12345 | Recruiter can search the ATS by ID |
| Looking for a referral!! | Your post on Kafka retries | Common ground first |
| Hello from a student | Question from a UIUC student | Pattern from MIT's cold email guide |
| Following up on my previous email regarding the position | Referred by Priya Shah: Backend role | MIT's guide lists "Referred to you by [name]". Use it only when that person agreed |
Copy-paste subject patterns:
Quick question about [team] at [Company]
Question from a [School] student
[School] [major] student, question about [team]
Referred by [Full Name]: [role] at [Company]
[Season Year] [Role] applicant, Job ID [ID]
Your [talk / post / PR] on [topic]
Question on [team]'s [system or feature]
OA completed, [role] (Job ID [ID])
Never use: ALL CAPS, "URGENT", a fake "Re:" or "Fwd:", emojis, or a subject that promises something the email does not contain. CAN-SPAM bans deceptive subject lines (see email law).
Anatomy of a reply-worthy email¶
Five parts, about 80 to 110 words.
| Part | Job | Words | Example line |
|---|---|---|---|
| 1. Common ground | Prove this is not a mass email | 15 to 25 | "Your post on idempotency keys fixed a bug in my own project." |
| 2. Who you are | One credential | 10 to 15 | "I'm a UIUC CS junior graduating May 2028." |
| 3. Proof | One or two results with numbers | 20 to 35 | "Adding retries with idempotency cut duplicate orders from 14 a week to zero for 2,300 users." |
| 4. The ask | One small, specific request with a time window | 15 to 25 | "Would you be open to a 15-minute call this week or next? I'm free Tue or Thu, 2 to 5 PM PT." |
| 5. Sign-off | Name plus 1 to 2 links | 5 to 10 | "Thanks, Arjun / LinkedIn / GitHub" |
Write part 3 with the XYZ formula from writing bullets. If you have no work experience, a small project is proof. When I hunted for my first internship, one thing that worked was cloning a startup's landing page and sending it with my application (How I Landed My Internship).
Weak vs strong, same student¶
Weak (about 130 words, no common ground, no number, a vague ask):
Subject: Job opportunity
Dear Sir/Madam,
I hope this email finds you well. My name is Arjun and I am a third year
Computer Science student at the University of Illinois. I am very passionate
about software engineering and have always admired your company. I have
experience in Java, Python, React, Node, SQL, AWS and many other technologies.
I am a hard worker and a quick learner who works well in teams.
I am writing to ask if there are any internship opportunities available at
your company. I would be very grateful if you could refer me or forward my
resume to the relevant team. I have attached my resume and transcript.
Please let me know if you need anything else. Looking forward to hearing
from you soon.
Thanks and regards,
Arjun
Strong (about 85 words, names and details invented for the example):
Subject: Your post on idempotency keys
Hi Priya,
Your post on idempotency keys fixed a bug in my own project. My campus
food-ordering app double-charged on retries; adding idempotency keys cut
duplicate orders from 14 a week to zero for 2,300 users.
I'm a UIUC CS junior and applied to the Summer 2027 SWE Intern role
(Job ID 12345) on your team. Would you be open to a 15-minute call this week
or next? I'm free Tue or Thu, 2 to 5 PM PT.
Thanks,
Arjun
linkedin.com/in/[handle] | github.com/[handle]
Templates¶
Full library, including LinkedIn notes and recruiter replies: templates. These seven cover cold email.
1. Hiring manager on the exact team¶
Use when the manager has a talk, post, repo, or launch you can name. Based on interviewing.io's advice: no attachment, 1 to 2 links, ask for a chat this week or next.
Subject: Question on [team]'s [system or feature]
Hi [First name],
I [watched your talk / read your post] on [topic]. The part about [detail]
matched what I hit building [project], where [what you did] cut [metric]
by [number].
I applied to [role] ([Job ID]) on your team. Would you be open to a
15-minute call this week or next? I'm free [two windows, their time zone].
Thanks,
[Name]
[LinkedIn] | [GitHub or site]
2. University or early-career recruiter, after you apply¶
About 90 words. Send the same day you apply.
Subject: [Summer 2027 SWE Intern] applicant, Job ID [ID]
Hi [Name],
I'm [Full Name], a [year] in [major] at [School], graduating [Month Year].
I applied to [role] (Job ID [ID]) on [date].
Two things that match the role:
- [Project or internship]: [result with a number]
- [Skill from the job description]: [where you used it, with a number]
Is there anything else you need from me to be considered this cycle?
Thanks,
[Name]
[LinkedIn] | [Resume link] | [Work authorization line, if relevant]
3. A 15-minute chat with an engineer or alum (Jugal's 2026 template)¶
Verbatim from 7 videos on networking your way to offers.
Subject: Quick question about [team] at [Company]
Hi [Name],
I'm [Name], [one line credential]. I read your [specific post, project, or talk] and [one line on what stuck with you].
I'm applying to [role] at [Company] and would love 15 minutes to hear what the team actually looks for. Happy to work around your calendar.
Thanks either way, [Name]
His shortest version, from How I Got Interviews at Amazon, Meta & Startups. His rule there: "Keep it short. No pitch. No pressure." Put a common-ground line before the second sentence, since this version has none.
Hi [Name],
I admire your work at [Company]. I'm interested in [Role]
and would love to learn more about your team's work.
Would you be open to a quick call?
He sends it with his resume attached. To a hiring manager, link the resume instead.
4. Interest plus a referral ask (Jugal's 2025 template)¶
From The Job Hunt I Didn't Burn Out Doing, with one change: the original opens with "Hope you're doing well." Here that line is replaced by a common-ground line, because Jugal's 2026 post says generic openers are where most cold emails die.
Subject: Interest in [Job Position] at [Company Name]
Hi [Name],
[Common-ground line: one thing they built, wrote, or posted.] I'm a [Your Role], and I'm interested in the [Job Position] at [Company].
I've worked on [One-liner about your best project/impact].
My background in [Relevant Skills] aligns with [Company Initiative or Product].
Would love to connect or be considered for a referral.
Here's the role: [Insert link]
Resume attached.
Thanks,
[Your Name]
Use this one for people you share real common ground with. Cold referral asks to strangers are low-yield; read referrals first. Sending it to a hiring manager? Replace "Resume attached." with a resume link, per interviewing.io's no-attachment rule.
5. Professor or lab (research internship or TA role)¶
Jugal's TA email from The $0 Masters in the US. Follow up after 7 to 10 days, and send the second follow-up too: "One of my professors replied after the second follow-up, and that turned into a full-semester TAship" (How I Paid $0 for a U.S. Degree).
Subject: TA Opportunity for [Course Name]: [Semester]
Dear Professor [Last Name],
I'm [Your Name], a [Year, Major] student, and I wanted to express interest in a TA position for [Course Name] this upcoming [Fall/Spring]. I earned an A in the course and have experience tutoring [Subject/Topic].
I'd be grateful for any opportunity to support your course and contribute meaningfully. Please let me know if there's a formal process I should follow.
Thank you for your time and consideration.
Best,
[Your Name]
[University, Contact Info]
6. Quant or HFT firm (guidance ask)¶
Transcribed from the image in How to break into $300K+ HFT roles. Quant intern applications open early, so send this in summer. See Jane Street, Citadel, Hudson River Trading.
Hi [Name],
I'm a [Year] CS/Math student at [University], and I'm fascinated by the intersection of low-latency systems and quantitative research. I'm preparing for roles in firms like [Company] and would be grateful for any guidance or a quick 15-minute chat on how to best position myself.
Thanks in advance,
[Your Name]
7. Someone who posted "we're hiring"¶
Subject: Your post about [team] hiring
Hi [Name],
Saw your post that [team] is hiring a [role]. I [one result with a number,
tied to the role's stack], and I applied today ([Job ID]).
Happy to send a 3-line summary if it helps. Is there anything the team
weighs that the job post does not say?
Thanks,
[Name]
[LinkedIn] | [GitHub]
Jugal's shorter version for team leads who posted in the last 3 days: "Hey, I saw your recent post. Curious if your team is hiring for XYZ?" (source).
Find and verify the address¶
Full method on finding people. The short version:
- Get the person's full name and the company's email domain (careers page footer or press page).
- Search Hunter Email Finder with "First Last" plus the domain. Free plan: 50 credits a month, and failed searches are free (pricing).
- If nothing comes back, guess three patterns:
first@,first.last@,flast@(from interviewing.io part 2). Large companies often use usernames, so guesses fail more there. - Verify every address in Hunter Email Verifier (free up to 100 a month). Send to Valid, drop Invalid, and run Accept-all results through Truelist (free) first.
- Never send to unverified guesses in bulk. Bounces damage your sender reputation, and Hunter's 2026 average bounce rate was already 3.6%.
When to send¶
| Situation | When | Source |
|---|---|---|
| A new intern or new grad posting | Within 1 to 3 days of it going live. Review is rolling, so the posted deadline is almost never the real one | 494 Summer 2027 Internships |
| You just applied | Same day or next morning, with the job ID | Practice norm |
| You met someone at a fair | Within 24 hours | MIT CAPD |
| Day of week | Barely matters: Wed and Thu 0.48% reply rate, Mon and Tue 0.45%, Fri 0.44% | Belkins, 7.5M B2B emails |
| Time of day | 8 AM to 12 PM in the recipient's time zone had the highest reply rate | Belkins |
Write at night and use Gmail Schedule send to deliver at 9 AM their time. Gmail holds up to 100 scheduled emails.
Decision makers in Hunter's 2025 survey said the send day and time do not matter to them (State of Cold Email 2025). Do not wait for a perfect Tuesday. For the recruiting calendar itself, see internships.
How many to send¶
| Mode | Volume | What it gets you |
|---|---|---|
| Light | 5 new people a week | "Five a week for a month is 20 conversations started" (Jugal) |
| Standard | 10 to 15 a day in a 10-minute daily block | Jugal's pace in The Job Hunt I Didn't Burn Out Doing |
| Ceiling for a personal Gmail | Stay under 50 a day | Keeps you far from limits and spam complaints |
| Hard limit (do not approach) | 500 a day on personal Gmail; 2,000 on Google Workspace (500 on trial accounts) | Gmail limits, Workspace limits |
Hunter's sweet spot of 20 to 49 sends a day per account comes from sales mailboxes. You are one person writing to individuals, so stay lower and personal.
Budget your free email-finder credits: Hunter's 50 credits a month covers about 50 people. Spend them on hiring managers and team engineers, not on whole departments.
Deliverability checklist¶
- Send from your personal Gmail or your university address. Do not buy a new domain for outreach: it has no sending history and you must set up its SPF or DKIM yourself, which Gmail requires of every sender (Gmail sender guidelines).
- Verify every address before sending (see above).
- Plain text, no images.
- Open tracking off. In Hunter's 2026 data, emails without open tracking got 7.4% replies vs 4.4% with it (Hunter 2026).
- At most 2 links. No link shorteners.
- No attachment on a first email to a manager. Link the resume instead (Google Drive, "Anyone with the link: Viewer", tested in a private window).
- One personal line per email, written by you.
- Test your template at mail-tester.com before any mail merge. It gives a spam score for your draft.
- Remove anyone who says no or asks you to stop, everywhere, for good.
- Keep spam complaints near zero. Gmail requires every sender to stay below a 0.3% spam rate.
Mail merge without looking like spam¶
Use this only when you send more than 10 a day and every row has a line you wrote yourself.
| Tool | Free limit (as of Oct 2026) | How to use it |
|---|---|---|
| Mailmeteor | 50 emails a day | Gmail merge from Google Sheets; Jugal's suggested tool at 10 to 15 a day |
| YAMM | 20 recipients a day | Fine for 20 a day |
| Streak | 50 merges a day | Works inside Gmail. Leave its open tracking off (see the deliverability checklist) |
| GMass (paid) | 7-day trial at 50 a day, then paid | Skip unless you already pay |
Sheet columns for the merge:
- Fill
Hookby hand for every row: one sentence about their post, talk, repo, or team. Hunter found two custom fields in the body lifted replies by 56%. - Fill
Proofwith your most relevant result for that role. - Send 10 to 15 rows a day, not the whole sheet.
- Mark
StatusandSentDatethe same day, then follow the cadence in follow-up and tracking.
Want the drafting and sending automated end to end? See n8n automation, with review-before-send turned on.
Email law: CAN-SPAM, UK and EU¶
This is not legal advice. The US law, CAN-SPAM, covers email whose primary purpose is advertising a commercial product or service. A one-to-one job inquiry does not advertise a product, so it is likely outside the law. Follow its rules anyway; they cost nothing.
| CAN-SPAM rule (FTC guide) | What it means for you |
|---|---|
| No false or misleading header information | Send from your real name and real address |
| No deceptive subject lines | The subject describes what is in the email |
| Identify the message as an ad | Not relevant to a job inquiry; never disguise a sales pitch as one |
| Include a valid postal address | Required for commercial email. For a job inquiry, a city in your signature is a fine habit |
| Tell recipients how to opt out, and honor it within 10 business days | Add "If this isn't the right person, no worries, I won't follow up" and stop the same day they ask |
Penalties run up to $53,088 per violating email.
UK readers: the ICO says the PECR rule on direct marketing email does not apply to corporate subscribers, but UK GDPR still applies to a named person's work email. Do not hide your identity, give a way to opt out, and respect an objection (ICO business-to-business guidance). EU country rules vary; the same habits keep you safe.
Watch out: Scammers pose as recruiters too. A real employer never asks you to pay for a job, buy equipment, or deposit a check and send money back (FTC job scams). Check that the sender's domain matches the company and that the role exists on the official careers site.
Common mistakes¶
| Mistake | Fix |
|---|---|
| Opening with "I hope this email finds you well" and a life story | Open with the common-ground line |
| Listing 12 technologies | One result with a number beats a skills list |
| "Any opportunities at your company?" | Name one role and one job ID |
| Asking a stranger for a referral in the first email | Ask for 15 minutes; ask for the referral after you talk (referrals) |
| Emailing 10 people at one company the same day | 1 to 2 per company per wave; add a second person only after 3 business days |
| Attaching resume plus transcript plus cover letter | One link, or one PDF named Firstname_Lastname_Resume.pdf when a recruiter asked for it |
| Following up 5 times | 3 touches total, then stop |
| Spending outreach on a company that does not sponsor your visa | Check sponsorship first (how) |
| Guessing an address and sending without verification | Verify every address |
Pre-send checklist¶
- One job ID picked, and I have applied or will apply today.
- Resume tailored to that job (tailoring).
- Address verified.
- Subject is under 7 words and says what is inside.
- First line is about them, and it is true.
- One or two results with numbers.
- One ask, with a time window.
- 50 to 125 words. I read it out loud once.
- 1 to 2 links, tested in a private window.
- No exclamation marks, no "Dear Sir/Madam", no typos in their name or company.
- Scheduled for 8 AM to 12 PM in their time zone.
- Logged in my tracker with a follow-up date (template).
Resources¶
- interviewing.io: cold outreach to hiring managers: two cold email templates and targeting rules. How to use it: read the targeting section, then compare your draft to their template 1.
- MIT ISO: cold emailing: cold email norms for international students. How to use it: copy the subject patterns and the "mention general timeslots" advice.
- The Muse: the meeting-request email template: a short coffee-chat template. How to use it: base for alumni chat asks.
- Hunter: State of Email Outreach 2026: benchmarks from 31M emails (mostly sales). How to use it: the numbers behind "3 touches" and "1 to 2 people per company".
- Muskan Agarwal: COLD EMAILS Explained: video on emails people answer. How to use it: watch before you write your first one, as Jugal suggests.
- Avinash Singh: cold email, referral and follow-up templates: template walkthrough. How to use it: bookmark; change one line per template.
- Jugal: The Holy Grail of Networking (Notion): Boolean searches, templates, and email finders. How to use it: take the search strings to finding people.
- The One Skill That Can Unlock Every Opportunity: Jugal's relationship-first approach for introverts. How to use it: pick 2 to 3 people, not 20.
- Jugal's AI job application tools post (June 2026): tools for applying, interview prep, and networking, with his longer 15-minute chat email. How to use it: find the address with Apollo or Hunter from its networking list, then send M3 with a first line you wrote. His own rule there: send "fewer, better" messages.