How to Write a Cover Letter That Is Not a Restated Resume

Most cover letters fail for one reason: they restate the resume in paragraph form. The reader already has the resume. A letter that repeats it is a second copy of a document they have read, written in a worse format, and it gets skimmed in four seconds. A letter that works does something the resume structurally cannot - it makes an argument, connects two facts the bullet points leave unconnected, and shows you understood what this particular job is for. This guide is the structure for that, plus a full worked example.

First: does this job need one?

Writing a real letter takes twenty-five minutes. Sending forty generic ones takes the same time and achieves less, so the first decision is where to spend the effort.

Whether cover letters still matter goes deeper into the read rates. The summary: they are read less often than they used to be, and they matter more than ever in the cases where they are read.

The fifteen minutes before you write anything

You cannot write a specific letter from a job title. Before drafting, collect four things:

1. The actual problem behind the role.Read the posting for what breaks if this seat stays empty. A listing heavy on "documentation" and "handover" is usually a team that lost someone. One about "first hire on the team" is a function being built from nothing. Those need different letters.
2. The two or three requirements that are load-bearing. Most postings list twelve things and mean four. The load-bearing ones are usually named first, repeated, or written in more specific language than the rest.
3. Something real about the company. Not the mission statement. A product decision, a recent launch, a public post by someone on the team, a change in their pricing. One concrete detail is worth three paragraphs of admiration.
4. A name. The hiring manager, the team lead, the recruiter. LinkedIn or the company site usually gives it up in two minutes.

The structure: four paragraphs, 250-350 words

Shorter than people expect. A one-page letter in 11pt is roughly 400 words and almost always contains 150 words of filler. Aim for the top half of a screen.

Paragraph one: why this job, in one specific sentence

Delete "I am writing to apply for the position of...". The reader knows which role you applied for; the application told them. That sentence spends your most valuable line on zero information.

Open instead with the specific thing that made you apply, and put your strongest credential in the same breath:

"Your posting says the analytics function is being rebuilt from scratch after the last two analysts left. I did exactly that at Northwind last year - inherited an undocumented reporting stack and rebuilt it into something the commercial team now runs without me."

Compare with "I am writing to express my strong interest in the Data Analyst position at your esteemed organisation." The first is unmistakably written for this job. The second could be sent anywhere, and reads like it was.

Paragraph two: one story, told properly

Take your single strongest piece of evidence for the load-bearing requirement and tell it in four or five sentences: the situation, what you did, the outcome. Not three examples - one. Three examples in a paragraph become a list, and a list is what your resume already is.

This is the paragraph where the letter beats the resume, because a bullet point cannot hold a decision. "Reduced report turnaround from five days to one" is a good bullet. The letter version can say what you tried first, why it failed, and what you changed - which is the part that shows judgement. If you want a scaffold for structuring it, the STAR method is the same skeleton used for interview answers and works on the page too.

Paragraph three: the second axis, or the objection

This paragraph does one of two jobs. If you are an obvious fit, use it for a second, different dimension - if paragraph two was technical, this one is about working with people, or shipping under a deadline, or the domain.

If you are not an obvious fit, use it to answer the objection directly, before the reader has to raise it themselves. A career changer, a gap, a shorter tenure, a missing credential - name it in one sentence, then spend two on the bridge:

"I have not worked in fintech before. What I have done is five years of reporting inside a regulated environment where every number was audited, so the constraint the role describes - reconcilable, evidenced outputs rather than fast approximations - is the one I already work under."

Addressing the obvious concern yourself is disarming. Leaving it unmentioned does not make it invisible; it just means someone else fills the silence with a guess.

Paragraph four: close on the work, not on yourself

No "thank you for your time and consideration, I look forward to hearing from you at your earliest convenience". Two sentences: something forward-looking about the role, and a plain close.

"If it would help, I can walk through how I would approach the first ninety days on the reporting rebuild. Happy to send the dashboard I mentioned."

A complete example

Dear Priya,

Your posting says the analytics function is being rebuilt after the last two analysts left, and that whoever joins will own reporting end to end. I did that at Northwind last year - inherited an undocumented stack of forty-odd spreadsheets and turned it into something the commercial team now runs without me.

The starting point was that nobody trusted the weekly numbers, because three versions of "revenue" existed and none reconciled. My first instinct was to rebuild the dashboards, which was wrong - the problem was upstream. I spent the first month with the sales and finance leads agreeing a single definition of each metric, then built the model on top of that in SQL and Power BI. Weekly reporting went from five days of manual assembly to an automated Monday morning refresh, and the recurring argument about whose number was right stopped happening.

I have not worked in fintech before. What I have done is five years of reporting inside a regulated environment where every figure was auditable, so the constraint in your posting - evidenced, reconcilable outputs over fast approximations - is one I already work under. The domain vocabulary I will have to learn; the discipline I will not.

If it would help, I am happy to walk through how I would approach the first ninety days of the rebuild. Thanks for reading.

Aditi Sharma

Around 290 words. Every paragraph carries information the resume does not: the diagnosis that the problem was upstream, the month spent on definitions, the honest admission about the domain. That is what a reader remembers.

Format and tone rules

• Address a person."Dear Priya" or "Dear Ms Nair". If you genuinely cannot find a name, "Dear Hiring Team". Never "To Whom It May Concern" - it announces that you did not look.
• Write the way you speak, one notch more formal. Words you would not say out loud - herewith, esteemed, endeavour, aforementioned - make the letter sound like a template.
• No adjective stacks."Dynamic, results-driven professional" is four words of nothing. Facts do the work adjectives are pretending to do.
• Send PDF unless told otherwise,named sensibly: aditi-sharma-cover-letter.pdf. If the application is an email, the letter is the email body - do not attach a letter that says "please find attached my letter".
• Match the header to your resume - same name block, same font, same contact details. It reads as one considered application rather than two documents.
• Proofread the company name. The single most common fatal error in cover letters is the name of a different employer left in from the last one.

Doing this at volume without going generic

Twenty-five minutes per letter does not scale to forty applications a week, and it does not need to. Build one base letter where paragraphs two and three hold your two strongest stories, then rewrite only the opening and the objection paragraph per application. That is eight to ten minutes, and it keeps the specificity where it is visible.

If you use AI to draft, use it for the skeleton and the tightening, never for the content. A model that has not read your work history invents plausible achievements, and a letter with an invented figure in it is worse than no letter - you will be asked about that figure. The AI cover letter generator works from your actual resume and the actual posting for this reason, and the cover letter templates give you the frame if you would rather start from a structure than a blank page.

Does the ATS read it?

Sometimes it is stored and searched, sometimes it is attached and never opened. Because you cannot tell which, two practical rules: keep it as real, selectable text rather than an image or a scan, and let the load-bearing terms from the posting appear naturally in it. Do not keyword-stuff a letter - it is written for a human, and it reads badly the moment it is optimised for anything else. The keyword work belongs on the resume, where the ATS scanner can show you what matched and what did not.

The mistakes that sink otherwise good letters

• Summarising the resume in prose. The reader has the resume.
• Leading with what you want - "this role would be a great next step for my growth". The letter is about their problem, not your trajectory.
• Praising the company for three sentences without connecting it to anything you have done.
• Explaining your entire career chronologically. Pick one story.
• Apologising for what you lack. Name it once, bridge it, move on.
• Going past 400 words. Length is read as an inability to prioritise.

The short version

Skip the letter for bulk portal applications and write a real one where a human will read it. Open with the specific reason this job, not a statement that you are applying. Tell one story properly in the middle, answer the obvious objection before it is raised, and close on the work. Two hundred and fifty to three hundred and fifty words, addressed to a named person, with one concrete detail no other applicant could have written. That last part is the whole test: if your letter could be sent to another company by changing the name, it is not finished.