Job Hunting Playbook — Junior SWE on OPT

The Founder Cold Email Playbook for Getting Hired

A step-by-step system for emailing startup founders directly to land software engineering interviews — without ever touching a job portal.

~3 hours daily
Stack: React, Node.js, Python, Django
Target: Pre-seed → Series B
SECTION 01

The Psychology — Why This Actually Works

Your biggest fear is probably: "Won't they think something is wrong with me for cold emailing?" The short answer is no — but the long answer matters, because understanding founder psychology is what separates emails that get replies from emails that get archived.

How founders think vs. how HR thinks

At a company with 500+ employees, a hiring manager gets a cold email and thinks: "This is unusual. Why isn't this person applying through our careers page like everyone else? Something's off." That suspicion is rational in their world — they have systems, pipelines, recruiters. Going around them signals either ignorance or desperation.

A founder at a 5-person startup who just raised a seed round gets the same email and thinks: "Oh thank god, someone who can actually code and isn't waiting to be spoon-fed. I've been trying to hire for three weeks and all I get is recruiter spam."

This is the fundamental asymmetry you're exploiting. Early-stage founders are drowning. They're writing code, doing sales, managing investors, and trying to hire — all at once. Many of their best hires came through warm intros, Twitter DMs, or cold emails. Your outreach isn't weird in their world; it's normal.

What your cold email actually signals

Positive signals a founder reads
Initiative — you go after what you want
Research skills — you found them specifically
Genuine interest — not a mass application
Startup-ready personality — resourceful, scrappy
Low-friction — they can reply in 30 seconds
Negative signals to avoid
Generic mass email — signals zero effort
Leading with your needs — sounds selfish
Being vague about skills — signals inexperience
Apologetic tone — undermines confidence
Hiding OPT status — creates trust issues later

The "why is this person looking?" objection

This fear is overblown for several reasons. Most people at any given time are passively or actively looking — founders know this. Engineers leave jobs for better opportunities constantly. You're a junior engineer — the entire world expects you to be looking for your next step. And most importantly, you're not framing this as desperation. You're framing it as curiosity and interest in their specific company. That's attractive, not suspicious.

The mindset to internalize

You're not begging for a job. You're a builder who noticed an interesting company and is reaching out to see if there's a fit. That mental frame changes everything — your word choice, your tone, your confidence. If they're not hiring, that's fine. You lose nothing. If they are, you just skipped the line.

The math in your favor

Let's be realistic about numbers. If you send 15 well-researched emails per day, about 20–30% will be opened, and about 5–10% will get a reply. That means in a week of 75 emails, you'll get roughly 4–8 replies. Some will be "not hiring right now" (still valuable — warm contacts for later). Some will be "let's talk." Even one or two conversations per week puts you far ahead of people who only apply through job portals where they're competing with 200+ applicants per listing.

SECTION 02

Where to Find Startups to Email

You want companies that have recently raised money (meaning they have budget to hire), are small enough that the founder reads their email (usually under 50 people), and are building something where your stack — TypeScript, React, Node.js, Python, Django — is relevant. Here's every source worth using, organized by quality.

Tier 1: The best free sources

Best Overall
Y Combinator Directory
ycombinator.com/companies

The single best free source. Over 5,000 companies, filterable by batch, industry, status, region, and team size. Filter by the most recent batches (W25, S25, W26) to find companies that just raised. Use the "Is Hiring" filter. Add ?keywords=react or ?keywords=python to the URL to find relevant stacks. Sort by "Launch Date" to see newest companies first.

Funding Database
Crunchbase
crunchbase.com

The standard for funding data. Free tier lets you search companies by funding stage, location, industry, and founding date. Search for companies that raised Seed or Series A in the last 90 days. Look at "Recent Funding Rounds" section for a live feed. The free tier is limited, but sufficient for building a daily list of 15 targets.

Community Database
YCDB (Y Combinator Database)
ycdb.co

A community-built database of all YC companies with more granular data than YC's official directory. You can create custom ranking scores, see funding amounts, and filter by revenue ranges. Good for identifying which YC companies are growing fastest.

Curated List
TopStartups.io
topstartups.io

A curated gallery of outstanding early-stage companies with recent funding from leading investors like Sequoia, a16z, Accel, and Khosla. Shows investor names, funding amounts, employee counts, and founding year. Good for finding companies backed by top-tier VCs — a signal of quality.

Gallery + Jobs
Startups.gallery
startups.gallery/news

Handpicked early-stage companies with recent funding news. Covers AI, fintech, healthcare, and more. Less noisy than Crunchbase — every listing is editorially selected. Check the "news" section for the freshest funding announcements.

Tech News
TechCrunch Funding Section
techcrunch.com/category/startups

Daily articles about funding rounds. When a company announces a raise on TechCrunch, the founder is usually quoted — that's a person to email. Subscribe to the TechCrunch Startups newsletter for a daily digest of newly funded companies.

Tier 2: VC portfolio pages

Every venture capital firm publishes their portfolio. These are gold mines because every company listed has received funding, and the VC's brand signals quality. Browse these and look for companies with 5–50 employees that are building web/software products.

Y Combinator
ycombinator.com/companies

5,000+ companies. Filter by batch recency, industry, and hiring status. The most useful single portfolio page.

Andreessen Horowitz (a16z)
a16z.com/portfolio

One of the most active early-stage investors. Filter by sector — their consumer and enterprise portfolios are heavy on web tech.

Sequoia Capital
sequoiacap.com/our-companies

Top-tier. Look for their seed and Series A investments specifically. These companies are well-funded but still small.

First Round Capital
firstround.com/companies

Focuses on seed stage. Many of their companies are exactly the size (5–20 people) where a cold email to the founder works.

Bessemer Venture Partners
bvp.com/portfolio

Strong in cloud, SaaS, and developer tools. Their early-stage investments are very relevant for your stack.

Accel
accel.com/portfolio

Strong in enterprise SaaS and developer tools. Heavy representation in Europe and US.

Khosla Ventures
khoslaventures.com/portfolio

Invests in both AI and traditional software. Lots of early-stage companies in their portfolio.

General Catalyst
generalcatalyst.com/portfolio

Active across all stages. Filter for their more recent, smaller investments.

Greylock Partners
greylock.com/portfolio

Famous for developer-facing companies. Many LinkedIn, Discord, Figma-type companies started here.

Benchmark
benchmark.com

Very selective, small portfolio. If Benchmark invested, the company is strong. All their portfolio companies are worth emailing.

Other VC portfolios worth browsing: Lightspeed Venture Partners, NEA, Index Ventures, Founders Fund, Union Square Ventures, Kleiner Perkins, Ribbit Capital, Craft Ventures, Lux Capital, Redpoint Ventures, Wing VC, Boldstart Ventures, BoxGroup.

Tier 3: Startup job boards (inverted use)

Instead of applying through these boards, use them as a source of companies to cold email. If a company is posting on these boards, they're actively hiring — which means your cold email to the founder arrives at the perfect moment.

Wellfound (formerly AngelList)
wellfound.com

The biggest startup job board. Filter by role, stage, and tech stack. Don't apply through the portal — find the founder on LinkedIn and email them directly instead.

Work at a Startup (YC)
workatastartup.com

YC's own job board. Every listing here is from a YC company. Shows team size, funding, and stack. Use it as a research tool, then email the founder.

Hacker News "Who's Hiring"
news.ycombinator.com (monthly thread)

Posted on the 1st of every month. Companies post with stack details, location, and sometimes founder email right in the post. These are very technical companies — your stack fits well here.

LinkedIn Startup Jobs
linkedin.com/jobs

Filter by company size (1–10, 11–50), date posted (past week), and keywords like "React" or "Python." Then find the founder's profile and email them.

Tier 4: Twitter/X and newsletters

Many founders announce their raises on Twitter before it hits Crunchbase. Follow these accounts and set up alerts.

Accounts and newsletters to follow

Twitter/X accounts: @techcrunch, @jason (Jason Calacanis — often posts about investments), VC partner accounts who tweet about new portfolio companies, and founders you admire who retweet peers' funding announcements.

Newsletters: StrictlyVC (daily funding rounds), The Hustle, TLDR (tech newsletter), Newcomer (startup-focused), Term Sheet by Fortune (daily deals and fundraising), The Information (paywall but excellent).

Subreddits: r/startups, r/SaaS, r/EntrepreneurRideAlong — founders often post about their companies and hiring needs.

SECTION 03

How to Find Founder Emails

You've found 15 companies. Now you need the founder's actual email address. Here's every method, ranked by effectiveness.

Method 1: Guess the pattern (works 60%+ of the time)

At startups, email formats are almost always predictable. If the company is "acmeco.com" and the founder is "Jane Smith," try these patterns in order:

jane@acmeco.com jane.smith@acmeco.com jsmith@acmeco.com j@acmeco.com

The first format (firstname@company.com) is correct roughly 50–60% of the time at early-stage startups. Use an email verification tool (see below) to confirm before sending.

Method 2: Free email finder tools

Best Free Tier
Hunter.io
hunter.io

25 free searches per month. Enter a company domain and it returns all email addresses associated with that domain, plus the email pattern used. The "Email Finder" feature lets you search by name + domain. Also has a Chrome extension for finding emails while browsing LinkedIn or company websites. The free "Email Verifier" tool checks if an address is valid — use this to verify your pattern guesses.

Most Generous Free Tier
Apollo.io
apollo.io

10,000 free credits per month — far more generous than any competitor. Has a database of over 275 million contacts. You can search by company, title, location, and tech stack. The Chrome extension works on LinkedIn — visit a founder's LinkedIn profile and Apollo will show you their email. Also includes basic email sequencing on the free plan.

Budget Option
Snov.io
snov.io

Free tier with 50 credits/month. Includes email finder, verifier, and drip campaign tools. Good Chrome extension. The "Domain Search" feature is useful — enter a company's website and get a list of all email addresses found.

LinkedIn Focused
Lusha
lusha.com

150 free email credits per month. Chrome extension works directly on LinkedIn profiles — visit the founder's profile and Lusha shows contact details. Particularly good for finding personal emails when company emails aren't available.

Method 3: Manual detective work (free, always works)

When tools fail, go manual. These approaches work for virtually any founder.

Company website "About" or "Team" page — Many startups list founder emails directly, especially on their contact page.
LinkedIn profile — Visit their profile. Check the "Contact Info" section (sometimes public). Even if the email isn't there, you can see their name and company, which is enough for pattern guessing.
GitHub profile — Many technical founders have their email in their GitHub profile or in their git commit history. Check their repos.
Twitter/X bio — Founders often have their email or DMs open. A DM works almost as well as an email.
YC Directory — YC company pages often have founder LinkedIn links on the right sidebar. Start there.
Product Hunt launch page — If they launched on Product Hunt, the founders who posted often have linked profiles with contact info.
Press coverage — TechCrunch articles about their funding round sometimes quote the founder with a contact reference.
Google: "founder name" + "email" OR "@company.com" — Sometimes their email appears in conference speaker bios, podcast descriptions, or old blog posts.
Pro tip: Verify before you send

Never send to an unverified email. Bounced emails hurt your sender reputation, and after enough bounces, your emails start going to spam for everyone. Use Hunter.io's free email verifier or NeverBounce (free for low volumes) to check every address before hitting send.

SECTION 04

The 5-Minute Research Protocol

This is where you separate yourself from every other cold emailer. 5 minutes of research per company turns a generic email into one that feels personally written — because it is. Here's exactly what to look for and where.

01

Visit their website (1 minute)

Read the homepage. Understand in one sentence what they do and who they sell to. Look at their pricing page if it exists — it tells you their business model. Check for a "Careers" page — if they're hiring engineers, your email is perfectly timed. Look at the footer for tech blog links.

02

Check their tech stack (1 minute)

Install the Wappalyzer browser extension — visit any website and it tells you what technologies they're using (React, Next.js, Django, etc.). Also check their job postings for stack mentions. If you see React + Node.js or Python + Django in their stack, mention this in your email. It proves you did your homework and shows alignment.

03

Try their product (1 minute)

If they have a live product, sign up or play with the demo. Note one specific thing — a feature you liked, a UX detail that stood out, something that didn't work perfectly. This becomes your opening line and it's devastatingly effective because almost nobody does this.

04

Skim the founder's LinkedIn (1 minute)

Look for shared connections, shared schools, or recent posts they've written. If they posted about a technical challenge their team is facing, that's your in. If they went to the same school as you, mention it. Any shared context makes your email 3× more likely to get a reply.

05

Find one specific hook (1 minute)

You need exactly one specific, non-generic thing to reference. Examples: "I noticed you're using Next.js with a Django backend — I've built exactly that combination in my last project." Or: "I saw your Product Hunt launch last week — the onboarding flow is really clean." Or: "I read your blog post on migrating to TypeScript." The hook proves you're not mass emailing.

SECTION 05

Writing the Email — Anatomy of What Works

The email needs to be 4–7 sentences. No more. Founders get hundreds of emails. You have about 8 seconds to prove this isn't spam. Every sentence must earn its place.

The structure

Part Purpose Length
Subject line Get them to open it 3–8 words
Line 1: The hook Prove you researched their company 1 sentence
Line 2–3: Your credential Establish you can build things 1–2 sentences
Line 4: The bridge Connect your skills to their needs 1 sentence
Line 5: The ask Low-commitment next step 1 sentence
Line 6: OPT note Address visa proactively 1 sentence

Rules for each part

The Hook (Line 1): Must reference something specific about THEIR company. Not "I love what you're building" — that's generic. Instead: "I've been using [Product] for the past week and the [specific feature] is really well done" or "I noticed your team just open-sourced [repo] — the approach to [specific thing] is clever." The specificity is the proof of effort.

Your Credential (Lines 2–3): One concrete proof of competence. Not a resume dump. Pick your single best signal: a project with a live URL, a metric ("built an app used by 500+ users"), an open-source contribution, or a company name if you've worked somewhere recognizable. Include your stack naturally: "I work primarily in TypeScript/React on the frontend and Python/Django on the backend."

The Bridge (Line 4): Connect your skills to something they need. If you saw they're hiring frontend engineers: "I noticed you're expanding the frontend team — I'd love to contribute." If their stack matches yours: "Since you're building on React and Node, I think there's a good fit." If you're not sure what they need: "I'd be excited to help ship features for [Product] as you scale."

The Ask (Line 5): This is critical — make it low-commitment. Never ask for a job directly. Ask for a 15-minute chat, or offer to do a small technical challenge, or ask if they're open to a conversation. The easier it is to say yes, the more replies you get. "Would you be open to a quick chat this week?" is much better than "I'd love to work at your company."

The OPT Note (Line 6): One sentence, matter-of-fact, no apology. "I'm on OPT with full work authorization through [year] — happy to discuss details." Don't bury it, don't over-explain it, don't lead with it.

Critical: Things to never include

Do not attach your resume in the first email — it makes the email feel like a job application, not a human conversation. Don't include "Dear Hiring Manager." Don't include a paragraph about your life story or your education background. Don't say "I am writing to express my interest in…" — this sounds like a cover letter and gets immediately deleted. Don't use formal sign-offs like "Respectfully" or "Sincerely." Just use "Best," or your name.

SECTION 06

Copy-Paste Templates

Below are three templates for different situations. Replace the green placeholders with your research. Never send any template without customizing the hook — that's the entire point.

Template A: "I used your product"

Best when: The company has a live product you can actually try.

Template B: "Your stack matches mine"

Best when: You found their tech stack through Wappalyzer, job postings, or their GitHub.

Template C: "I saw you're hiring"

Best when: You found an active job posting but want to bypass the application form and go directly to the founder.

SECTION 07

Subject Lines That Get Opened

The subject line determines if your email gets opened. At early-stage startups, founders scan their inbox quickly — you need to look like a person, not a recruiter or salesperson.

Subject lines that work
Quick note on [Product Name]
[Your name] — fullstack eng, React + Python
Re: your frontend engineer opening
Loved the [specific feature] in [Product]
Question about [Company]'s frontend
Fellow [school/city/community] — eng intro
[Mutual connection] suggested I reach out
Subject lines that get deleted
Application for Software Engineer Position
Interested in Opportunities at [Company]
Resume — [Your Name]
Job Inquiry
Passionate developer seeking role
Hello! I'd love to work with you!
[Anything with ALL CAPS or exclamation marks]
The "lowercase test"

A good subject line should sound natural if spoken out loud. "Quick note on Acme's dashboard" sounds like something a person would say. "Application for Full-Stack Software Engineer Position at Acme Technologies Inc." sounds like a robot. Use lowercase, keep it under 8 words, and make it specific.

SECTION 08

The Follow-Up System

About 60–70% of replies come from follow-ups, not from the initial email. Founders are busy — they saw your email, thought "interesting," and then got pulled into something else. Following up is not annoying; it's expected.

The follow-up schedule

Timing What to Send Tone
Day 0 Original email Warm, specific, curious
Day 5–7 Follow-up #1: Gentle bump Light, no pressure
Day 14 Follow-up #2 (optional): Add new value Add something new — never just "bumping again"
After #2 Stop. Move on.

Follow-up #1 template

Follow-up #2 template (optional)

Never send a third follow-up

Two follow-ups max. After that, silence is the answer. Adding a third email crosses from persistent to annoying, and will damage any future chance of a relationship with that founder. If they didn't reply to two emails, they're either not interested or not hiring. You can circle back in 2–3 months with a completely new email if you want.

SECTION 09

Handling the OPT Visa Question

Being on OPT is a legitimate concern for founders, but it's far less of a dealbreaker at startups than most people think. Here's how to handle it strategically.

What founders actually worry about

Most early-stage founders don't know the details of OPT, STEM OPT extension, or H-1B sponsorship. Their concerns are vague: "Is this going to be complicated?" and "Will this cost me a lot of money?" Your job is to make it feel simple and low-risk.

Key talking points to have ready

OPT requires zero sponsorship from the employer. You're authorized to work. The company just needs to register with E-Verify (free, takes 10 minutes).
If you have a STEM degree, STEM OPT extends your work authorization to 3 years total — that's a long runway with no sponsorship needed.
H-1B sponsorship is a future conversation, not a present one. Frame it as: "For the first 1–3 years, there's nothing extra you need to do."
Thousands of startups have employees on OPT. It's common and well-understood by immigration attorneys. You can offer to handle the paperwork coordination.
When to bring it up

Mention it briefly in your first email — one sentence at the end. Don't lead with it (makes it seem like a bigger issue than it is) but don't hide it either (creates trust issues). The ideal phrasing is casual and confident: "I'm on OPT with full work authorization through [year] — happy to discuss details." Save the full explanation for the conversation, not the email.

SECTION 10

The Daily Execution System

Consistency beats intensity. 15 emails a day for 2 weeks beats 100 emails in one afternoon. Here's the daily schedule.

9a

Morning: Build your target list (45 min)

Open Crunchbase, YC Directory, and one VC portfolio page. Find 15 companies that raised in the last 90 days, are building with a relevant stack, and have under 50 employees. Add them to your tracking spreadsheet with: company name, founder name, founder email, company URL, what they do, and one research note.

10a

Late morning: Research + write emails (90 min)

Go through your 15 targets. Spend 5 minutes per company on the research protocol. Write each email using the templates, customizing the hook for each one. Verify email addresses. This is the core work — protect this time block.

12p

Midday: Send all 15 emails (15 min)

Send between 10am–12pm in the recipient's time zone — this is when founders check email. Tuesday through Thursday are the best days. Avoid Monday mornings (inbox overload) and Friday afternoons (mentally checked out).

1p

Afternoon: Follow-ups + replies (30 min)

Check your tracking sheet for emails sent 5–7 days ago with no reply — send follow-up #1. Reply to anyone who responded. Update your spreadsheet with statuses. This is also a good time to check for new funding announcements for tomorrow's list.

Weekly targets

75 new emails per week (15/day × 5 days). ~25 follow-ups per week (from previous weeks' batch). At a 5–10% reply rate, expect 4–8 meaningful replies per week. At a 25% conversion from reply to call, expect 1–2 calls per week. After 3–4 weeks, you should have multiple interviews in progress.

SECTION 11

Tracking & CRM Setup

You need a simple system to track who you've emailed, when, and what happened. A Google Sheet is enough. Here are the columns you need:

Column Example Why
Company Acme Inc Basic tracking
Website acme.com Quick reference
Founder Name Jane Smith Personalization
Email jane@acme.com Contact
Stage Seed / Series A Context
Stack React, Node, Postgres Relevance check
Date Sent 2026-03-25 Follow-up timing
Follow-up 1 2026-04-01 Tracking cadence
Status Sent / Replied / Call Scheduled / Rejected Pipeline management
Notes "Loved our Django exp, wants to chat next week" Context for follow-up
Color coding system

Use conditional formatting in Google Sheets: Gray = sent, waiting. Yellow = follow-up sent. Green = replied positively / call scheduled. Red = rejected or bounced. Blue = "not now, circle back later." This gives you an instant visual pipeline view.

SECTION 12

Handling Every Type of Reply

Every reply is valuable, even the "no." Here's how to handle each scenario to maximize your outcomes.

Best case
"Let's chat" / "Send me your resume"

Reply within 2 hours. Suggest 2–3 specific time slots in the next 48 hours. Include a Calendly link if you have one. Attach your resume now (not before). Prepare by knowing their product cold. Have a clear answer ready for "tell me about something you've built."

Very common
"We're not hiring right now"

This is a warm contact, not a rejection. Reply: "Totally understand — I appreciate you getting back to me. I'll keep an eye on [Company] and would love to reconnect if things change. Mind if I check back in a couple months?" Then set a reminder in your sheet and actually do it in 8 weeks.

Warm lead
"Try applying through our careers page"

Do it — but reply first saying "Will do, thanks for pointing me there. Excited about [specific thing about their product]." You now have a name to reference in your application. Apply immediately and mention in the application that you spoke with the founder.

Redirect
"Talk to my CTO / engineering lead"

Great sign — the founder thought your email was worth forwarding. Reply with "Thanks so much — I'll reach out to them now." Email the CTO/lead and open with "Hi [Name], [Founder] suggested I reach out..." This is now a warm intro, not a cold email.

Delayed opportunity
"We might need someone in Q3/Q4"

Reply: "That's great to hear — I'll plan to follow up around [timeframe]. In the meantime, I'd love to learn more about what you're building if you're ever free for a quick chat." Set a calendar reminder and reach out when the time comes. These often convert.

Tough but fair
"We need more senior engineers"

Reply graciously: "Completely understand. If it helps, I'm happy to start with a paid trial project or part-time contracting to demonstrate what I can do — but no pressure. Wishing you all the best with the search." This reframes the conversation from seniority to proof-of-work, which some founders find compelling.

SECTION 13

Common Mistakes That Kill Replies

Mistake Why It Kills Fix
Sending the same email to 100 founders Founders can smell mass emails instantly. Zero personalization = zero replies. Customize the first 1–2 sentences for every single email. The template is the body; the hook is always unique.
Writing a 500-word email Founders won't read past the first 3 lines. Long emails signal poor communication skills. 4–7 sentences max. Every sentence must earn its place. If you can cut it, cut it.
Attaching resume in the first email Turns a human conversation into a job application. Triggers "delete" instinct. Never attach anything in email #1. Save it for when they ask or for the follow-up.
Leading with "I'm looking for a job" Frames the entire interaction around your needs, not their company. Lead with interest in their product. The job interest emerges naturally.
Using formal corporate language "Dear Sir/Madam, I am writing to express my interest…" gets instantly deleted at startups. Write like a human. "Hi Jane," is perfect. Read your email out loud — if it sounds stiff, rewrite it.
Sending emails on weekends Gets buried under Monday morning inbox avalanche. Send Tuesday–Thursday, 10am–12pm in the recipient's timezone.
Not having a portfolio/GitHub link Founders want to see what you've built. No link = no proof = no reply. Even a simple GitHub profile with 2–3 projects is enough. Include the link in your email signature.
Emailing companies too large for this strategy At 200+ employees, founders don't read unsolicited emails. You're hitting a void. Stick to companies with under 50 employees. Sweet spot is 5–25.
Giving up after one week This is a numbers game that compounds over time. Week 1 will feel slow. Commit to 3 weeks minimum. By week 3, you'll have follow-up replies, warm contacts, and scheduled calls stacking up.
The daily email checklist — review before every send

Before hitting send on each email, verify: (1) Is the founder's name spelled correctly? (2) Is the company name correct? (3) Does my first sentence reference something specific about THIS company? (4) Is my email under 7 sentences? (5) Is my ask low-commitment? (6) Did I include my portfolio/GitHub link? (7) Did I verify the email address? If all seven are yes, send it.

Now go do the work.

This playbook gives you everything you need. The difference between people who land startup jobs through cold email and people who don't isn't talent or templates — it's consistency. Do this every day for three weeks. You'll be surprised how far 15 emails a day can take you.