Most cold emails fail because they ask for help before giving the reader a reason to care.

A recruiter or founder does not need your full life story. They need to understand who you are, what role you fit, and why replying is easy.

Quick answer

The best cold email is short, specific, and easy to reply to.

Bad:

Hi sir/mam, I need a job. Please help me. I am hardworking and passionate.

Better:

Hi Riya, I saw your team is hiring backend interns. I recently built a Node.js job tracker with auth, PostgreSQL schemas, and deployment notes. Would it be useful if I sent the repo and a 2-minute project summary?

The better version gives context, proof, and a small next step.

the structure

Use five parts:

  1. Specific reason for emailing.
  2. One-line proof.
  3. Role or opportunity you are asking about.
  4. Link to proof.
  5. Tiny next step.

That is enough.

template for a fresher

Subject: Backend intern interested in your Node.js opening

Hi [Name],

I saw your team is hiring for a backend intern role. I am a student building Node.js and Redis projects, including a queue-based worker that handles retries and idempotency.

Here is the project: [portfolio link]

If the role is still open, I would be grateful if you could point me to the best way to apply or share whether my profile is relevant.

Thanks,
[Your name]

This works because it is specific. It does not say “I am passionate and hardworking” without proof.

template for a founder

Subject: Student backend developer interested in [Company]

Hi [Name],

I have been following [Company] because of [specific product or problem]. I am building backend systems in Node.js and TypeScript, and I recently wrote about making queue workers safe to retry.

My work is here: [portfolio link]

If you ever consider interns or junior backend help, I would love to be considered.

Best,
[Your name]

Founders get vague messages all the time. Specific product context helps you stand out.

what not to write

Avoid this:

Dear sir/madam,
I am looking for any opportunity. Please help me.

It gives the reader no role, no proof, no context, and no easy reply.

Also avoid long paragraphs about your childhood, motivation, or every technology you have touched. Save detail for the resume or portfolio.

make the reply easy

A good cold email does not demand a meeting immediately.

Low-friction asks work better:

  • “Is this role still open?”
  • “Is my profile relevant for this team?”
  • “Who is the right person to contact?”
  • “Can I send a short project summary?”

The easier the reply, the more likely you get one.

follow up once

Wait four to seven days. Then send:

Hi [Name],

Just following up on this. I know inboxes get busy, so no worries if now is not the right time.

Thanks,
[Your name]

Do not send five follow-ups. One polite follow-up is enough.

final checklist

Before sending, check:

  • Did I name a specific role or company reason?
  • Did I include one proof point?
  • Is my portfolio or resume linked?
  • Is the email under 150 words?
  • Is the ask easy to answer?

Cold email is not magic. It is just a small, clear proof packet.