Cover letters, referrals and recruiter outreach

The previous lesson covered the places people find you. This one covers the short pieces of writing that travel with your resume: a cover letter, a request for a referral, and messages to and from recruiters.

Each is only a few paragraphs long, and each follows the same rule as a good bullet. Be specific about this company and this role, give one piece of hard evidence, and make the next step easy for the person reading.

Cover letters

Mostly unread, occasionally decisive. The trick is knowing which situation you are in.

When they are not read

For most applications through a careers portal at a large company, the cover letter is not read at the screening stage. A recruiter working through a stack goes to the resume.

So do not spend an hour on a cover letter for a routine application. A short, competent one takes fifteen minutes and is enough.

When they matter

Four situations where a cover letter genuinely changes the outcome:

1. Small companies and startups. The founder or hiring manager reads everything.
2. A career change. The letter carries the argument your resume cannot make on its own.
3. An unusual circumstance — relocating, a gap, applying below or above your apparent level. One paragraph pre-empts the objection.
4. Explicitly requested, especially with a specific prompt. Not answering it is a filter you have failed.

The structure

Three short paragraphs. Under 250 words total.

Paragraph 1 — Why this role, specifically. Something that could not be copy-pasted to another company. Reference the actual product, a specific engineering problem they have described, or something they published.

I've been running a self-hosted instance of your ingest agent for eighteen months on a 40-node cluster, and the backpressure model in your 0.9 release is the cleanest solution to the problem I've seen.

Paragraph 2 — Why you. Your two or three most relevant pieces of evidence, expanded slightly beyond the resume bullet.

Paragraph 3 — The close. One line. What you would like to happen next.

What to avoid

• Restating your resume in prose. The reader has the resume.
• Opening with "I am writing to apply for the position of…". They know.
• Flattery with no specifics. "I have always admired your commitment to innovation" is worse than nothing.
• Anything over one page. Three paragraphs is the ceiling.

Asking for a referral

A referral is the highest-leverage thing in your job search (see Referral, cold application, and inbound), and most people ask badly.

Why most requests fail

Hi! I saw you work at Northwind. I'm looking for new opportunities — would you be able to refer me?

Three problems: it names no role, it asks the referrer to do the work of finding one, and it gives them nothing to submit. The kind response requires ten minutes of their effort, so it gets postponed and then forgotten.

The request that works

Make it a two-minute task with everything supplied.

Hi Anjali — hope things are going well at Northwind.

I'm applying for the Senior Backend Engineer role on the payments team (req 4471). It looks like a good match: I've spent the last three years owning a payments service at Kestrel, including the settlement and reconciliation side, which the posting calls out.

Would you be willing to refer me? I've attached my resume, and here's a paragraph you can paste into the referral form if it's useful:

"Priya owns the settlement service at Kestrel Systems, processing around ₹40 crore a day. She rebuilt their reconciliation pipeline last year, cutting unmatched transactions from about 300 a day to under 10. Strong fit for the payments team."

No problem at all if you'd rather not — I know referrals carry your name.

Why this works: it names the exact requisition, it explains the fit in one sentence, it supplies the words, and it gives an explicit way to decline.

Who to ask

In order of likelihood:

1. Former colleagues who worked with you directly.
2. University or bootcamp classmates now at the company.
3. People you know through open source or a community.
4. Second-degree connections, where a mutual contact can introduce you.
5. Cold outreach to strangers — low success rate, but non-zero when the message is specific.

If you have no connection

Some companies have public referral communities, and many engineers on professional networks will refer a stranger with a genuinely relevant background. Keep it short, name the requisition, and give them the paragraph.

Recruiter outreach and responses

Recruiters are the other door in. There are two short pieces of writing worth getting right: the reply to an inbound message, and the cold note to a recruiter.

Replying to inbound

A recruiter has contacted you. Three ways this goes wrong: you ignore it, you reply with a single word, or you give away your position immediately.

A good reply does three things:

Hi Sam — thanks for reaching out.

I'm happy to hear more. For context: I'm a backend engineer with six years' experience, currently owning the settlement service at Kestrel (around ₹40 crore a day). I'm most interested in infrastructure and platform roles.

Could you send the job description and the level this is scoped at? Happy to find time for a call this week or next.

It establishes your level, states what you want, and asks for the two facts that determine whether the conversation is worth having.

Cold outreach to a recruiter

Lower success rate, but cheap. Keep it under 120 words:

Hi Sam — I saw Northwind is hiring for backend roles on the payments team.

I'm a backend engineer, six years, currently owning the settlement service at Kestrel Systems (~₹40 crore/day). I rebuilt our reconciliation pipeline last year, cutting unmatched transactions from ~300/day to under 10.

Resume attached. Is the Senior Backend Engineer role (req 4471) still open, and would it be worth a conversation?

Specific role, specific evidence, specific question.

Managing the pipeline

Once several conversations are running, keep a simple table: company, role, stage, last contact, next step, and the compensation band if you know it.

Two reasons. You will lose track otherwise. And when an offer arrives, you want to know exactly which other conversations can be accelerated.