How to Cold Email a Founder for a Job: 4 Startup Templates

A cold email to a founder for a job can put you in front of the person who feels the hiring problem most sharply. It can also disappear if it reads like a mass application or asks them to invent a role for you. This guide gives you a decision rule, a public-contact workflow, four specific templates, and a follow-up plan you can use this week.

Decide whether the founder is the right contact

Cold outreach works best when it matches the way the startup is actually hiring. Your goal is not to bypass the application process. It is to give the right person a quick, credible reason to notice your application or start a conversation.

Use this rule before you write:

At a startup, a role can begin as an urgent problem before anyone has written a polished job description. That is when a concise note can be useful. You are not asking, “Do you have anything for me?” You are showing that you understand one problem and can contribute to it.

This approach is especially useful when you have found a company through the hidden job market but cannot find a relevant opening. It is less useful when the company has a clear process and a named recruiter. Following the stated process signals good judgment.

Find a work email without crossing a line

Start with information the company or founder chose to make public. Read the careers page, team page, product blog, recent press page, and the founder’s own professional profile. If the company has a contact form for candidates, use it.

A focused search can help you find those official pages faster. Google documents that the site: operator narrows results to a specific domain, so try searches such as site:company.com careers, site:company.com team, and site:company.com "contact" to stay on the company’s public web footprint. Google’s search guidance shows the same operator syntax.

If multiple public company pages show a consistent work-email pattern, one carefully researched message to that pattern is reasonable. Check the address before sending. If it bounces, stop trying variations. Use the contact form or a professional social message instead.

Do not hunt for a personal email address, personal phone number, family account, or data-broker record. Do not send the same message to every cofounder. One person, one work channel, one reason for writing is enough.

There is a second reason to begin on the official site: it helps you verify that a role and company are real. The FTC advises job seekers to search the company or hiring person with terms such as “scam,” “review,” or “complaint,” and says never to pay for the promise of a job. Read the FTC’s job-scam checklist before sharing money, identity documents, or financial details.

Give the founder a reason to care in the first 120 words

A founder does not need your full career story in the opening email. They need enough context to answer three questions: Why this company? What have you done that relates to the problem? What are you asking for?

Use this four-part structure:

1. A real trigger. Name a product behavior, customer, launch, job requirement, or founder post you actually read. “I like your mission” is not a trigger.
2. One proof point. Pick one result, project, or artifact that connects to the role. Use a number only if you can explain it in an interview.
3. One useful link. Lead with a portfolio case study, GitHub repository, short product teardown, writing sample, dashboard, or campaign brief. Make it easy to open without requesting access.
4. One small ask. Ask for a short conversation, permission to send a one-page idea, or confirmation that the team expects to hire in a function. Do not ask for an undefined job.

A resume is still useful, especially after you apply. But a work sample is often easier for a busy operator to evaluate in one click. Y Combinator’s job-seeker advice recommends naming a few contributions you would be excited to make and describes candidates who stood out with product ideas, go-to-market outlines, or sample code. Its examples are a good standard for useful proof.

Choose a sample that is small enough to finish and safe to share. An engineer might link a tiny demo or a documented open-source contribution. A product candidate might send a one-page onboarding teardown. A marketer could outline three testable messages for a public landing page. A finance or operations candidate could show a clean, fictionalized analysis rather than employer data. If you want the resume behind that link to make the same case, use this startup resume guide to tighten the evidence.

Example: Suppose you are a data analyst interested in a subscription startup. A strong link is a short public notebook that defines an activation event, sketches a funnel, and lists the data you would request. It is not a ten-page report. Its purpose is to make your thinking visible without pretending you know the company’s private data.

Use subject lines that tell the truth

A subject line should make the email’s purpose obvious. A clever line may earn a glance, but clarity earns the right kind of glance. Do not imply a referral, a meeting, or a connection you do not have.

Try one of these patterns:

• Product analyst application: activation idea
• A retention test for [Company]
• Applied for Growth Engineer: relevant prototype
• Question about [Company]’s next design hire
• Follow-up: onboarding teardown for [Company]

Avoid “Quick question,” “Opportunity,” “Following up,” or “Job inquiry” by themselves. They force the reader to open the email before they know why it matters. Put the role, problem, or artifact in the line instead.

Before you send, read the subject and first two sentences together. They should match. If the subject promises an idea, the email should link to a real idea. If it names a role, state whether you have applied.

Four cold email templates for startup jobs

These are hypothetical examples. Keep the structure, but replace every detail with something true about your own work and the startup. Each message is short on purpose.

1. A posted role

Use this when you found a role and want the person closest to the work to see a concise, relevant introduction. Submit the official application as well.

Subject: Product analyst application: activation-funnel idea

Hi Aisha,

I saw the Product Analyst opening and am applying through the careers page today. The role’s focus on helping new finance teams reach their first completed workflow caught my attention.

At my last SaaS team, I built an activation view that showed where accounts stalled before their first reconciliation. We changed the checklist and improved completed setups by 14%.

I made a one-page sketch of how I would investigate a similar drop-off for your product: [link]. Would a 15-minute conversation next week be useful?

Maya Chen Portfolio | LinkedIn

2. No role posted

Use this when you can point to a specific business need and have a small piece of work that proves you understand it. Do not pretend the company is hiring.

Subject: A lifecycle test for a B2B billing startup

Hi Dev,

I read your launch note about adding multi-entity billing. It made me wonder how new admins learn the setup sequence before their first invoice.

I am a lifecycle marketer who recently mapped a five-email onboarding sequence for a SaaS product with the same handoff problem. I drafted three test messages for your public onboarding flow here: [link].

I do not see a lifecycle role listed. If this is a problem your team expects to own this year, would you be open to a short conversation?

Maya Chen Portfolio | LinkedIn

3. After you applied

Use this when the application is already in the system and you have one extra artifact that makes your fit clearer. Do not resend your whole resume in the email.

Subject: Applied for Growth Engineer: relevant prototype

Hi Aisha,

I applied on Monday for the Growth Engineer role. I wanted to share one piece of work that did not fit neatly in the application.

I built a small prototype that turns a public product event into a shareable invite flow: [link]. It relates to the role’s focus on activation experiments, and the README explains the trade-offs I made.

If the team is reviewing applications now, I would be glad to walk through it in 15 minutes. Thank you for considering my application.

Maya Chen GitHub | LinkedIn

4. One follow-up

Use this only after your first note. Reply in the same thread and add something new, rather than repeating the original request.

Subject: Re: Product analyst application: activation-funnel idea

Hi Aisha,

Bringing this back to the top of your inbox in case it arrived during a busy week. Since my first note, I added a short query outline to the activation sketch that shows the events I would validate first: [link].

If the role is already moving forward, no reply is needed. If the team is still exploring the problem, I would value a brief conversation.

Maya Chen

Use LinkedIn and X DMs as a bridge, not a duplicate

A direct message is useful when you cannot verify a work email or when someone has made that channel their public professional contact point. Keep it shorter than an email. Your job is to earn permission to send the useful link, not to recreate your full application in a chat window.

LinkedIn DM example:

Hi Aisha. I applied for the Product Analyst role and made a one-page activation-funnel sketch based on the public product flow. May I send the link here or by email?

X DM example:

Hi Dev. Your multi-entity billing launch raised a lifecycle question for me. I drafted three onboarding tests from the public flow. Is there a work email or channel where I can send the one-page note?

Do not send an email, connection request, LinkedIn DM, and X DM on the same day. Pick one channel. If you get no response, use one follow-up in that same channel. Repeated copies can make a thoughtful note feel automated.

Follow up once, then close the loop

Set a reminder for five business days after the first email. If you have a real update, send the follow-up template above. If you do not have anything new, send a two-sentence nudge or skip it.

Wait another seven to ten business days before deciding whether a final note adds value. In most cases, it does not. Stop after one follow-up unless the recipient replies or the startup publishes a meaningful change, such as a new matching role or product launch. A later message should refer to that new event, not to the old silence.

Track outreach in a simple sheet so you do not accidentally contact several people at the same company. Use these columns: company, target role or problem, contact, public source for the contact, channel, application date, work-sample link, first-send date, follow-up date, response, and next action. This also gives you a clean record when you ask for a startup referral later.

A reply is not the only useful outcome. Your note may lead to a better target, a request to apply through the right channel, or information about timing. If someone says no, thank them once and move on. Save the company for future roles rather than trying to argue your way into the current one.

Next steps

1. Pick five startups where you can name one real product, customer, or hiring trigger.
2. For each, decide whether the founder, a functional lead, or a recruiter is the right first contact.
3. Build one shareable proof-of-work link that matches the role you want, then tailor only the opening and ask for each company.
4. Apply through the official path when a role is posted, then send one truthful note and schedule one follow-up.
5. Review your tracker after two weeks. Improve the targeting or work sample before sending more volume.