What to actually write in a cold email to a recruiter

The email is short. That is the whole trick, and it is the hardest part, because everything you want to say about yourself feels load-bearing. It is not. A recruiter reading on a phone between meetings decides in about four seconds whether this is worth a reply, and nothing below the fold participates in that decision.

The subject line

Say the role and say something specific. "Application" is invisible. "Interested in opportunities" is worse, because it announces you are sending this to everyone.

Backend Engineer (Pune) — 4 years Go, shipped payments at scale
Re: Senior Data Analyst — built the reporting stack at a 200-person startup
Frontend role — I rebuilt a checkout that cut drop-off by a third

The first sentence

One sentence naming the role and where you saw it, so they can file the email without thinking. Then get out of the way. Do not open with "I hope this email finds you well" — it is four words that tell the reader nothing and signal a template.

The middle: two or three lines, no more

1. What you have done that maps onto this job. Not your whole history — the one or two things that would make this specific hire obvious. A number helps if you have an honest one.
2. Why this company. One sentence proving you read something other than the job title. Their product, a recent launch, the problem their engineering blog says they are wrestling with. This is the line that separates you from the fifty other emails in the inbox, and it is the line most people skip.
3. What you are asking for. A short call. The next step. Something a busy person can say yes to in one word.

Four things to cut

• Your entire career history. It is attached. The email's job is to make them open the attachment.
• Adjectives about yourself. "Passionate", "detail-oriented", "hard-working" — nobody has ever been talked into an interview by an adjective. Replace each one with the thing you did that made you describe yourself that way.
• Apologies for reaching out. You are applying for an advertised job. There is nothing to apologise for, and the apology makes you sound like a nuisance before they have decided whether you are one.
• More than one link. Pick the strongest — the repo, the portfolio, the case study — and give them that. Three links is a research project.

A worked example

Hi Priya,

I saw the Backend Engineer role on your careers page and wanted to write directly.

I have spent four years on Go and Postgres services, most recently owning the
payments path at a fintech doing about 40k transactions a day — including the
retry and reconciliation logic, which is the part that tends to hurt.

Your engineering post about moving settlement off the nightly batch is the
reason I am writing rather than clicking apply; that migration is the exact
problem I spent last year on.

Resume attached. Would a 20-minute call next week be worth your time?

Aryan

Nine lines. Every one of them is doing work. If you are writing several of these a week, the "why this company" sentence is the part worth automating research for rather than the part worth skipping — Replyrate writes both the email and that line from your resume and the job description, and you edit before anything is sent.

Then send it, and plan the follow-up now rather than later — most replies come from the second email, not the first.