Ask ten recruiters whether they read cover letters and you will get a roughly even split, which tells you the answer depends entirely on context. Rather than writing one for every application or abandoning them entirely, it is worth knowing which applications actually turn on them.

The three cases where it matters

1. You are changing fields

Your resume says logistics; the role is operations analytics. Nothing on the page explains the connection, and a recruiter with 200 applications will not construct the argument for you. The letter's only job is to make the transition legible in two paragraphs: what transfers, and what evidence you have that it transfers.

2. There is something on the resume that needs explaining

A two-year gap, three short tenures, a relocation, a return after caregiving, a layoff. A single honest sentence removes the question mark. Without it, the reader invents an explanation, and the invented one is usually worse than the truth.

3. Small organizations, and roles where writing is the job

Under roughly fifty people, the person reading is frequently the person hiring, and they read everything. In communications, policy, law, fundraising and journalism, the letter is a work sample regardless of what the posting says. The reader is assessing how you build an argument, so a letter that wanders is disqualifying evidence even when the resume is strong.

The structure that works

Four short paragraphs, under 300 words, on one page.

  • Opening: the role, and the single strongest reason you are credible for it. No "I am writing to apply for."
  • Evidence: one specific thing you did, with a number or an outcome, chosen to match the hardest requirement in the posting.
  • The bridge: the sentence only you could write, what connects your background to this particular organization's problem. This is where the letter earns its existence.
  • Close: what you want next, plainly. "I would welcome a conversation about the reporting side of the role."

The bridge paragraph, worked

Here is one career changer writing it twice: eight years managing a retail store, applying for an operations analyst role.

The version most people write:

Although my background is in retail rather than analytics, I am a fast learner with a genuine passion for data, and I am confident my analytical skills would transfer well to this position.

The version that works:

I ran a forty-person store for eight years, and the part I was best at was never in the job description: figuring out why the inventory forecast was wrong. After we missed peak season two years running I rebuilt the weekly replenishment model myself and cut end-of-season markdowns across my categories. Your posting describes the same problem from the other side: a forecasting process nobody on the floor trusts.

The first names a trait; the second names the work, shows the transfer already happening, and attaches to something in the posting rather than to the company's reputation.

The test is mechanical: delete the employer's name from your bridge paragraph. If it still reads perfectly well, it is not a bridge, it is a personal statement.

When the form has no letter field

Increasingly there is no upload at all, just an optional free-text box: "Anything else you would like us to know?" Treat it as the letter, compressed, and apply the same test: if none of the three cases applies, leave it blank. Blank is neutral; filler is not. When one of them does apply:

  • Eighty to 120 words, three or four sentences. No salutation, no sign-off. It is a note, not a letter, and the formal furniture makes it look pasted.
  • Lead with what the resume cannot show: the transition, the gap, the reason for this particular organization.
  • Use the shape rather than the structure: one sentence of context, one of evidence with a number in it, one that connects to their problem.
  • Write it elsewhere and paste it in. These boxes strip formatting and often have a character limit that is not shown until you exceed it.

Never paste a full letter in. A 300-word block in a 500-character box signals that you did not read the form.

When to skip it

Large-employer portals with an optional upload, high-volume roles, recruiter-led processes where you have already spoken to a person, and any application where you would be pasting a template with the company name swapped. A generic letter is worse than none: it costs you thirty minutes and signals volume applying.

Things that quietly damage you

  • Restating the resume in prose. The reader has the resume.
  • Enthusiasm as the main argument. Everyone is excited; it is not differentiating.
  • The wrong company name. Still the most common fatal error.
  • Obvious AI phrasing: "I am thrilled to express my keen interest," "in today's fast-paced landscape." Recruiters now pattern-match on this within a sentence.
  • Apologizing for what you lack. Address a gap once, factually, and move on.

On using AI to draft one

Fine for structure, dangerous for voice. The tell is not vocabulary, it is the absence of specifics: a generated letter can praise the company and describe the role, but it cannot know that you spent eight months rebuilding a returns process for a retailer with the same problem this employer is advertising. Write the specifics yourself and let the tool tidy the connective tissue, not the other way around.

When a letter is required

All of the above reflects typical US corporate hiring, where the letter is genuinely optional in most processes. The exception is any posting that lists a cover letter as a required document. Then it is part of a complete application, and leaving it out reads as an unfinished submission. Federal jobs spell this out: each USAJOBS announcement lists what you must provide in its Required Documents section, and a cover letter is usually optional. Resumes there are capped at two pages, so if you do send a letter, use it for what the resume cannot hold. Check the posting, not the convention.

A letter that could have been sent to four other employers is doing less than no work. The only paragraph that matters is the one that could not.