<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How do I cold email a recruiter or engineer at a tech company for an internship?", "acceptedAnswer": { "@type": "Answer", "text": "For tech internship outreach, focus on demonstrating genuine interest in the company's product or engineering challenges rather than just asking for a referral. Mention a specific project, open-source contribution, or technical blog post from the person you're emailing. Keep the email to 4-6 sentences and include a link to your portfolio or GitHub if relevant. Target engineers 1-3 years into their career — they remember recruiting recently and are more likely to respond." } }, { "@type": "Question", "name": "Is cold emailing effective for getting tech internships at FAANG companies?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, but the mechanism is different than in finance. At FAANG companies, a cold email typically leads to a referral rather than a direct hire. Internal referrals at Google, Meta, and Amazon move your application to the top of the review queue and can bypass the initial resume screen entirely. A single successful cold email that results in a referral can be the difference between getting screened out by an ATS and landing a phone interview." } }, { "@type": "Question", "name": "Should I cold email engineers or recruiters at tech companies?", "acceptedAnswer": { "@type": "Answer", "text": "Email engineers, not recruiters. Recruiters at FAANG companies receive hundreds of inbound messages and have limited bandwidth for cold outreach from students. Engineers, especially those 1-3 years into their careers, are more likely to respond and can provide referrals that carry significant weight in the hiring process. At startups, you can email founders or engineering managers directly since teams are smaller and hiring decisions are less bureaucratic." } }, { "@type": "Question", "name": "How do I find the email address of a hiring manager or engineer at a tech company?", "acceptedAnswer": { "@type": "Answer", "text": "Tech company emails can be found through company email pattern recognition, personal websites or blogs linked from GitHub profiles, LinkedIn contact info sections, or dedicated contact databases. Many engineers have public email addresses on their GitHub profiles or personal websites. For verified professional emails across FAANG and startups, platforms like Offerloop search 2.2 billion contacts by company, role, and seniority so you can find the right person without manual guessing." } }, { "@type": "Question", "name": "What should I say about my projects or GitHub in a cold email for a tech internship?", "acceptedAnswer": { "@type": "Answer", "text": "Reference one specific project that's relevant to the company's tech stack or problem space — not a generic portfolio dump. If you're emailing someone at Stripe, mention a payments-related project. If you're emailing a Meta engineer, mention something related to distributed systems or social platforms. Include a direct link to the project repo or live demo, not just your GitHub profile. One targeted project reference is worth more than a list of ten unrelated ones." } }, { "@type": "Question", "name": "When should I start cold emailing for tech internships?", "acceptedAnswer": { "@type": "Answer", "text": "For FAANG summer internships, start outreach in August-September — applications open in late summer and many positions fill by October-November. For startups, the timeline is more flexible with many hiring January through April for summer roles. Start networking 4-6 weeks before you plan to apply so you have time to build relationships and secure referrals before the application window closes." } } ] } </script> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "HowTo", "name": "How to Cold Email for a Tech Internship", "description": "Step-by-step guide to writing cold emails that get responses from engineers, PMs, and hiring managers at Google, Meta, Amazon, and top startups.", "totalTime": "PT15M", "step": [ { "@type": "HowToStep", "name": "Identify the right person to email", "text": "Target engineers or PMs with 1-3 years of experience at your target company. They're most likely to respond and can provide referrals. At startups, you can email founders or engineering managers directly. Use LinkedIn or a contact database like Offerloop to find the right contacts." }, { "@type": "HowToStep", "name": "Research their work before writing", "text": "Check their GitHub contributions, published blog posts, conference talks, or open-source projects. Reference something specific in your email to prove you did real research beyond reading their LinkedIn headline." }, { "@type": "HowToStep", "name": "Write a subject line that stands out", "text": "Include a specific hook: your university, a shared technical interest, or a reference to their public work. Avoid generic subject lines like 'Internship Question' that signal a mass email." }, { "@type": "HowToStep", "name": "Lead with technical substance", "text": "Your opening should reference a specific project they worked on, a blog post they wrote, or a technical problem their team solved. Show that you understand their work, not just their company's brand." }, { "@type": "HowToStep", "name": "Include a link to your best relevant project", "text": "Share one specific project that's relevant to their company's tech stack or problem space. Include a direct link to the repo or live demo. One targeted project is worth more than a generic GitHub profile link." }, { "@type": "HowToStep", "name": "Ask for a conversation, not a referral", "text": "Request a 15-minute call to learn about their experience. Never ask for a referral in the first email — let that happen naturally after a conversation. Engineers are more likely to refer someone they've actually spoken with." } ] } </script>

Cold Email for Tech Internships: 10 Templates for FAANG and Startups

Here's what nobody tells you about landing tech internships: the online application portal is a black hole. Google receives over 3 million applications per year. Meta's intern class is roughly 3,000 out of hundreds of thousands of applicants. If you're applying cold through the website with no referral, your resume sits in a pile of 500+ others being scanned by an ATS before a human ever sees it.

But a referral from a current engineer? That moves your application to a different queue entirely. At Google, referred candidates are 3-5x more likely to get a phone screen. At Meta, a referral triggers a manual review regardless of ATS score. At Amazon, a referral from a current SDE can fast-track your application to a specific team.

Cold email is how you get those referrals. Not by begging for them — by having genuine conversations with engineers and PMs who then want to refer you because they're impressed. This guide gives you 10 templates that work, the strategy differences between FAANG and startups, response rate data, timing for recruiting cycles, and the exact approach to talking about your projects that makes engineers want to take your call.

Why Cold Email Works for Tech Internships (And Why LinkedIn DMs Don't)

The Referral Economy in Big Tech

Tech companies run on internal referrals more than almost any other industry:

Google: Referrals account for an estimated 20-30% of hires despite being less than 5% of applicants. Referred candidates skip the initial resume screen and go directly to recruiter review. Engineers get a referral bonus and recognition for successful referrals.

Meta: The internal referral system is deeply embedded in the culture. Engineers can submit referrals through a dedicated portal, and those candidates are flagged for priority review. Meta actively encourages employees to refer strong candidates.

Amazon: Each SDE can submit referrals that go directly to the hiring manager for the specific team. This is especially powerful because Amazon intern hiring is team-matched — a referral to a specific team dramatically improves your odds.

Startups (Series A-C): At startups with fewer than 200 employees, the CEO or CTO often reviews every intern application personally. A cold email to the right person can literally put your resume on the founder's desk.

Why LinkedIn Messages Fall Flat in Tech

Engineers treat LinkedIn differently than finance professionals:

• Recruiter spam. Tech engineers get 10-30 LinkedIn recruiter messages per week. Your message drowns in that noise.
• Engineers don't live on LinkedIn. Many engineers check LinkedIn once a month. They check email multiple times a day.
• LinkedIn messages feel informal. A well-crafted email signals effort and professionalism in a way that a 300-character LinkedIn DM can't match.
• No GitHub link formatting. Email lets you properly link to projects, portfolios, and repos. LinkedIn message formatting is limited.

The exception: LinkedIn is useful for researching targets and for follow-up connection requests after a successful email exchange. Use LinkedIn for research, email for the actual outreach.

FAANG vs. Startup Strategy: Completely Different Playbooks

The biggest mistake students make is treating Google and a Series B startup the same way. The outreach strategy, tone, targets, and even email length should differ significantly.

FAANG (Google, Meta, Amazon, Apple, Microsoft)

Response rate benchmark: 8-15% from engineers, 3-5% from recruiters

Who to email: Software engineers and PMs with 1-3 years of experience (L3-L4 at Google, E3-E4 at Meta, SDE I-II at Amazon). They remember recruiting recently and have bandwidth for networking calls.

Tone: Professional but not stiff. Tech culture is less formal than finance, but a cold email still needs to be polished. Show technical depth.

Key differentiator: At FAANG, your email needs to signal technical competence. Engineers will skim your email for evidence that you can actually code. A link to a strong project, an open-source contribution, or a specific technical question about their team's work — these are what make engineers respond.

What NOT to do:

• Don't email recruiters. They get hundreds of messages and have no incentive to respond to cold outreach.
• Don't mention compensation, perks, or brand prestige. Engineers find this off-putting.
• Don't send the same template to 50 people at the same company. Word gets around on internal Slack channels.

Startups (Series A through Pre-IPO)

Response rate benchmark: 15-30% from engineers, 20-40% from founders/CTOs

Who to email: At startups under 50 people, email the CTO or engineering manager. At 50-200, target senior engineers or team leads. At 200+, treat it more like FAANG outreach.

Tone: More casual and direct. Startup people value hustle and genuine interest in the problem they're solving. Show you understand their product.

Key differentiator: At startups, showing you've used the product is the most powerful hook. Actually try their product, find something interesting (or find a bug), and reference it in your email. This signals product thinking and initiative — two traits startups value above almost everything else.

What NOT to do:

• Don't use corporate language ("I would welcome the opportunity to contribute to your organization's mission").
• Don't compare them to a larger company ("As an alternative to Google, your company..."). This is insulting.
• Don't pitch yourself for a specific role that doesn't exist. Ask if they're considering interns or if there's a way to contribute.

Response Rate Benchmarks by Company Type

Company Type	Cold Email Response Rate	Referral Conversion Rate	Avg. Response Time
FAANG (engineer target)	8-15%	40-60% of conversations lead to referrals	3-7 days
FAANG (recruiter target)	3-5%	N/A — referrals come from engineers	7-14 days
Late-stage startup (200+)	12-20%	50-70%	2-5 days
Mid-stage startup (50-200)	15-25%	60-80%	1-3 days
Early-stage startup (<50)	20-40%	70-90%	1-2 days

The pattern is clear: smaller companies respond faster and at higher rates. If you need an internship quickly, startups are the highest-ROI outreach target. If you're targeting FAANG specifically, plan for a longer outreach cycle and higher volume.

10 Cold Email Templates for Tech Internships

Template 1: FAANG SWE — Shared University

Subject: Fellow [University] Alum — Question About [Company] [Team/Org]

Hi [First Name],

As a fellow [University] alum (Class of [Year]), I was excited to see your work on [Company]'s [specific team, product, or project]. [One specific detail about their work or career path].

I'm a [year] studying CS and I've been building [brief description of a relevant project — 1 sentence with link]. I'm preparing for SWE intern recruiting and would love to hear about your experience on [Team].

Would you have 15 minutes for a quick call?

Thanks, [Your Full Name] [University], Class of [Year] [GitHub/Portfolio link]

Why this works: Alumni connection + specific team reference + a concrete project link. This gives the engineer three reasons to respond: shared identity, evidence of research, and proof you can build things.

Template 2: FAANG SWE — Technical Interest Hook

Subject: [University] CS [Year] — Your Work on [Specific Project/System] at [Company]

Hi [First Name],

I read your [blog post / conference talk / open-source contribution] on [specific topic], and it's directly relevant to a [project/research] I've been working on — [brief description with link].

I'm a [year] at [University] recruiting for SWE internships, and [Company]'s [Team/Org] is my top choice because of [specific technical reason]. Would you be open to a 15-minute call? I'd love to hear about what it's like working on [their specific technical area].

Best, [Your Full Name] [GitHub/Portfolio link]

Why this works: Referencing their public technical work (blog, talk, OSS) is the strongest hook for engineers. It shows you found them through genuine technical interest, not a LinkedIn search.

Template 3: FAANG PM — Product Curiosity

Subject: [University] [Year] — Question About [Product/Feature] at [Company]

Hi [First Name],

I've been using [specific product/feature they work on] and noticed [specific observation — a design choice, a recent update, or a user experience pattern]. I'm curious about the product thinking behind it.

I'm a [year] at [University] interested in PM internships, with experience in [one relevant detail — product management course, user research project, a product you built]. Would you have 15 minutes to chat about the PM role on [their team]?

Thanks, [Your Full Name] [University], Class of [Year] [Portfolio/project link]

Why this works: PMs love when someone notices specific product decisions. The observation in the email signals product sense — the #1 trait PM interviewers look for.

Template 4: FAANG PM — Career Path Interest

Subject: [University] [Year] — Your Path to PM at [Company]

Hi [First Name],

Your transition from [their previous role/company] to PM at [Company] caught my attention — it's a path I'm considering as someone with a [CS/business/design] background.

I'm a [year] at [University] and I've been [one relevant PM experience — leading a product sprint, running user interviews, building a side project with users]. Would you be open to a 15-minute call about how you broke into PM and what the internship experience is like?

Best, [Your Full Name] [University], Class of [Year]

Why this works: Career path questions are low-pressure and flattering. PMs who transitioned from other roles are especially likely to share that story because they're proud of it.

Template 5: Startup SWE — Product User Hook

Subject: [University] CS Student — Actually Use [Product] and Want to Help Build It

Hi [First Name],

I've been a user of [Product] for [timeframe] and [specific observation about the product — a feature you love, a pain point you noticed, or a use case they might not have considered]. [Optional: link to a related project you built].

I'm a [year] CS student at [University] looking for SWE internship opportunities. I'd love to contribute to [Product] — are you considering interns this [season], or would you have 15 minutes to chat about engineering at [Company]?

[Your Full Name] [GitHub link]

Why this works: At startups, showing you actually use the product is the equivalent of a deal reference in banking. It signals genuine interest and product awareness. Engineers at startups are passionate about their product and respond to people who share that passion.

Template 6: Startup SWE — Technical Contribution Angle

Subject: [University] CS [Year] — Open Source Contribution to [Company/Project]

Hi [First Name],

I noticed [Company]'s [open-source project/public repo] and [submitted a PR / found an interesting pattern in the codebase / built something using your API]. [Link to contribution or project].

I'm a [year] at [University] looking for SWE internships, and the technical problems [Company] is solving in [their domain] are exactly what I want to work on. Would you have 15 minutes to chat about the engineering team?

Thanks, [Your Full Name] [GitHub link]

Why this works: An open-source contribution or meaningful engagement with their codebase is the gold standard of startup cold outreach. It proves technical ability and initiative without you having to say either word.

Template 7: Startup PM — Problem Space Interest

Subject: [University] Student — Interested in How [Company] Is Solving [Problem]

Hi [First Name],

I've been researching [problem space/market] and [Company]'s approach to [specific aspect of their solution] stood out — particularly [one specific detail about their product strategy or recent launch].

I'm a [year] at [University] with experience in [relevant PM skill — user research, data analysis, product design]. I'm exploring PM internship opportunities and would love to learn how your team thinks about [specific product challenge]. Got 15 minutes?

[Your Full Name] [University], Class of [Year]

Why this works: Framing around the problem space rather than the job signals intellectual curiosity. Startup PMs want to talk to people who are genuinely interested in the problem, not just the title.

Template 8: Startup PM — Founder Email

Subject: [University] [Year] — Love What [Company] Is Building

Hi [First Name],

I saw [Company]'s [recent launch / funding announcement / product update] and I'm genuinely excited about [specific aspect]. As someone who's been [relevant experience — building products, doing user research, working in the same problem space], I appreciate [something specific about their approach].

I'm a [year] at [University] exploring internship opportunities. Would [Company] consider a PM or product-oriented intern this [season]? Either way, I'd value 15 minutes of your time to hear about your product vision.

[Your Full Name] [Portfolio/project link]

Why this works: Founders respond to genuine enthusiasm about their company. This email is direct, complimentary without being sycophantic, and opens the door even if they don't have a formal intern program.

Template 9: Follow-Up — No Response After 5-7 Days

Subject: Re: [Original Subject Line]

Hi [First Name],

Wanted to bump this — I know things move fast at [Company]. I recently [finished a relevant project / learned something related to their work / saw something about their company], which made me even more eager to connect.

Happy to work around your schedule if you have even 10 minutes.

Best, [Your Full Name]

Why this works: The "I recently did something relevant" addition gives them a new reason to engage rather than just saying "following up." Short and low-pressure.

Template 10: Follow-Up — After a Great Conversation

Subject: Thanks — [Specific Takeaway from Call]

Hi [First Name],

Thanks so much for chatting [today/yesterday]. Your insight on [specific thing they mentioned] was really valuable — it's changed how I'm thinking about [relevant topic].

I'm going to [specific next step: apply to the team, work on a related project, look into something they recommended]. If you'd be open to it, I'd love to stay in touch as recruiting season unfolds.

[Your Full Name]

Why this works: A specific takeaway proves you listened. The next-step statement shows initiative. "Stay in touch" plants the seed for the referral conversation without directly asking.

How to Talk About Your Projects and GitHub (What Engineers Actually Want to See)

This is where most tech cold emails fail. Students either don't mention projects at all, or they dump a generic GitHub link that an engineer will never click. Here's how to do it right.

The One-Project Rule

Reference one specific project that's relevant to the company, not your entire portfolio. If you're emailing someone at Stripe, mention your payments integration project. If you're emailing someone at Figma, mention your design tool side project. Relevance beats quantity every time.

How to Describe a Project in One Sentence

Use this formula: [What you built] + [what technology/approach] + [what result or scale]

Good:

• "I built a real-time collaborative code editor using WebSockets and CRDTs — it handles 50 concurrent users" (relevant for someone at Figma, Notion, or Google Docs)
• "I created an ML pipeline that classifies financial news sentiment using fine-tuned BERT, deployed on AWS Lambda" (relevant for fintech or ML-focused teams)

Bad:

• "Check out my GitHub — I have lots of projects" (no engineer will browse your repos without a hook)
• "I built a to-do app using React" (every CS student has done this — it doesn't differentiate you)

GitHub Profile Optimization for Cold Outreach

Before sending any cold email, make sure your GitHub profile is outreach-ready:

1. Pin your 3-4 best repositories — these should be your most impressive, relevant work
2. Write clear README files — an engineer who clicks your link should understand the project in 30 seconds
3. Include a live demo link when possible — deployed projects are 3x more impressive than repos that require local setup
4. Contribution activity matters — a green contribution graph signals consistent coding habits

What to Do If You Don't Have Strong Projects Yet

Start building now. Even one well-executed project can carry your cold outreach:

• Contribute to open source — even small PRs to popular repos show initiative
• Build something using the company's API — this is the startup equivalent of referencing a specific deal in banking
• Recreate a feature from their product — building a simplified version of something they ship shows both technical skill and product awareness

How to Find Engineer and PM Email Addresses

Personal Websites and Blogs

Many engineers maintain personal websites with contact emails. Check their GitHub profile, Twitter/X bio, or personal blog for links.

GitHub Profile Emails

Some engineers have their email public on GitHub. Check the "Email" field on their profile page, or look at their commit history which sometimes reveals their email.

Company Email Patterns

• Google: firstname.lastname@google.com (though many use firstname@google.com)
• Meta: firstname.lastname@meta.com (formerly @fb.com)
• Amazon: firstname.lastname@amazon.com or flastname@amazon.com
• Apple: firstname_lastname@apple.com
• Microsoft: firstname.lastname@microsoft.com or alias@microsoft.com

Contact Database

For verified emails without the guesswork, Offerloop searches 2.2 billion professional contacts by company, role, and seniority. Search "software engineer at Google" or "PM at Stripe" and get verified emails instantly. It's purpose-built for student networking at student-friendly pricing, not enterprise B2B sales tools that cost $50-500/month.

Timing: When to Send Cold Emails for Tech Internships

FAANG Summer Internship Timeline

Period	What's Happening	Email Strategy
July - August	Applications start opening	Begin outreach — 8-12 emails/week. Get conversations going before apps open.
September - October	Peak application window	Heavy outreach — 10-15 emails/week. This is when referrals have maximum impact.
November - December	Phone screens and onsite interviews	Maintain relationships. Ask contacts for interview prep advice.
January - February	Offers go out, some spots still open	Targeted outreach to teams still hiring.
March - April	Waitlist movements, last-minute openings	Opportunistic outreach only.

Startup Internship Timeline

Startups hire on a rolling basis with a much longer window:

Period	What's Happening	Email Strategy
September - November	Early-stage startups plan headcount	Begin exploratory outreach. Many startups don't have formal intern programs — your email might create one.
January - March	Peak startup intern hiring	Heavy outreach — 10-15 emails/week. Most startups hire interns 2-4 months before the start date.
April - May	Late hiring for summer starts	Second wave of outreach. Startups that got new funding may have opened headcount.

Best Days and Times for Tech

• Best days: Tuesday, Wednesday, Thursday
• Best time: 9:00 - 11:00 AM in the recipient's time zone (engineers check email after standup)
• Avoid: Monday mornings (sprint planning), Friday afternoons, and the week of any major product launch (everyone is heads-down)

LinkedIn Cold DM vs. Email: Which Works Better for Tech

Email Wins For:

• Initial outreach — higher open rates, more professional, better formatting for project links
• FAANG engineers — they check email daily, LinkedIn weekly
• Detailed messages — email supports code snippets, proper links, and attachments
• Tracking — email makes it easier to see if your message was opened and to schedule follow-ups

LinkedIn Wins For:

• Research — finding the right people to email by company, role, and school
• Warm-up — engaging with someone's posts before emailing creates familiarity
• Follow-up connections — connecting after a successful call maintains the relationship
• Startup founders — some founders are highly active on LinkedIn and responsive to DMs

The Optimal Tech Outreach Sequence

1. Research on LinkedIn — identify targets by company, team, university, and experience level
2. Find their email — check GitHub, personal sites, or use Offerloop for verified addresses
3. Send the cold email — use the templates above, include a relevant project link
4. Connect on LinkedIn after the call — send a connection request referencing your conversation
5. Stay visible — occasionally engage with their LinkedIn posts to keep the relationship warm

Common Mistakes That Kill Your Tech Cold Email

1. Being Too Formal

"Dear Mr. Chen, I hope this email finds you well. I am writing to inquire about..." — this reads like a form letter from 1998. Tech culture is informal. "Hi [First Name]" and a conversational tone are standard.

2. No Specific Project Mention

If your email could have been written by someone who doesn't code, it won't resonate with an engineer. Include at least one reference to a project you built or a technical problem you're working on. This is the tech equivalent of a deal reference in banking.

3. Asking for a Job Instead of a Conversation

"Do you know if there are any open intern positions?" — this puts them in an awkward spot. Instead, ask for a 15-minute conversation about their work. If they're impressed, they'll offer to refer you without being asked.

4. Sending Generic GitHub Links

"Here's my GitHub: github.com/username" with no context gives the recipient no reason to click. Instead, link to a specific project with a one-sentence description of what it does and why it's relevant to them.

5. Ignoring the Tech Stack

Emailing a Python engineer about your Java projects, or reaching out to a backend engineer when you're interested in iOS development, shows you didn't do basic research. Match your outreach to people whose technical area aligns with your interests and skills.

6. Mass Emailing at the Same Company

If you send 20 cold emails to 20 engineers on the same team at Google, they'll find out. Engineers talk on internal Slack channels. Send 2-3 targeted emails per team/org at most. Quality over spray-and-pray.

7. Not Following Up

Many engineers intend to respond but forget — they're in the middle of a sprint, a deployment, or a P0 bug. One follow-up after 5-7 days is expected and often effective. Zero follow-ups means you're leaving responses on the table.

Frequently Asked Questions

How do I cold email a recruiter at Google for an internship?

Don't. Email engineers instead. Google recruiters receive hundreds of inbound messages weekly and have limited bandwidth for cold outreach from students. Engineers with 1-3 years of experience are more responsive and can submit referrals that move your application to priority review. If you do want to reach a recruiter, ask an engineer contact to introduce you — a warm intro to a recruiter converts at 10x the rate of a cold email.

What should I say in a cold email to a software engineer at Meta asking about internships?

Reference something specific about their team's work — a product feature, an engineering blog post, an open-source project Meta maintains. Mention one relevant project you've built (with a link), state your school and year, and ask for a 15-minute call. Keep the entire email under 100 words. Meta engineers respond well to product awareness and technical depth, so show you understand what their team actually builds.

How do I cold email someone at a YC startup about an internship?

Be direct and show you've used or studied their product. YC founders value initiative — mentioning that you've tried their product, found a specific pain point, or built something using their API is the strongest hook. Many YC startups don't have formal intern programs, so frame your ask as "would you consider an engineering intern?" rather than "do you have open intern positions?" Keep the tone casual and the email under 80 words.

Should I cold email engineers or recruiters at tech companies?

Email engineers. At every major tech company, engineers who submit referrals have more influence on your application than recruiter inbound. Engineers with 1-3 years of experience are the sweet spot — they remember recruiting recently, have bandwidth for networking calls, and are early enough in their career to empathize with your position. At startups under 200 people, you can email engineering managers or CTOs directly.

Is cold emailing effective for getting tech internships?

Yes, but the mechanism is indirect. Cold emailing in tech leads to conversations, which lead to referrals, which lead to interviews. A referral at Google makes you 3-5x more likely to get a phone screen. At startups, a single conversation with the CTO can lead directly to an offer. The key is that your email needs to demonstrate technical competence — include a relevant project link, show familiarity with their product, and ask questions that signal you understand what they build.

When should I start cold emailing for summer tech internships?

For FAANG, start in August — applications open in late summer and many close by October. Begin networking 4-6 weeks before you plan to apply so you have referrals ready when applications open. For startups, the window is wider — most hire interns January through April for summer starts. Regardless of company type, the worst time to start networking is after you've already applied. Referrals carry the most weight before or simultaneously with your application, not after.

---

The students who land FAANG and top startup internships through cold email aren't doing anything complicated. They're finding the right people, writing specific emails with project links, and following up once. Start with 5 emails this week — target engineers, not recruiters, reference your best project, and ask for a conversation. If finding email addresses is the bottleneck, Offerloop's free tier gives you verified contacts at any tech company so you can focus on building relationships instead of hunting for addresses.