A cover letter has one job: connect what you did to what this employer needs next. Generated letters fail at exactly that, because they are written from your history rather than from the job description. They produce a confident summary of you, which nobody asked for. The fix is not a clever prompt — it is choosing a structure that forces the connection to be made in writing, paragraph by paragraph.
What every letter needs, in this order
Before the templates, the skeleton they all share. Four moves, and skipping one is what makes a letter feel thin:
- Why this role, specifically. One sentence naming something real from the posting or the company. Not praise — a reason.
- The match. The one or two things you have done that answer their requirement. This is the paragraph you write yourself.
- Proof. A number, an outcome, a named system or process. Vague claims read as generated because they are the only thing a tool can produce without your input.
- The ask. A plain closing sentence. Not a summary of the letter, not a restatement of enthusiasm.
The nine structures
Each one below is a shape, not a script. Replace every [bracket] — a bracket left in means you have not decided that field, and a draft will happily decide it for you.
1. The referral letter
Use when: someone inside put you forward.
[Name] suggested I get in touch about the [role]. I have spent [period] doing [thing], most recently [specific project or responsibility]. The part of your posting that fits is [requirement] — I did that at [place], where [one concrete outcome]. I would like to talk about [specific area].
2. The straight application
Use when: no connection, applying through a normal process.
I am applying for [role]. You are looking for [requirement from posting]; at [place] I ran [thing], which is the same problem at [scale or context]. [One sentence of outcome with a number.] The rest of my background is in the CV — this letter is about the match above.
3. The career change
Use when: your history is in a different field.
On paper I am a [old field]; the work I want to do is [new field]. What transfers is [specific skill or process], which I used to [concrete result]. What does not transfer is [honest gap], and here is how I have started closing it: [course, project, certification, portfolio].
4. The internal move
Use when: applying inside your current employer.
I have been in [current team] for [period], where I [specific contribution]. The [role] needs [requirement]; I have already done an adjacent version of it in [project or secondment], and I know [relevant internal context] which shortens the ramp-up. I have flagged this with [manager].
5. The gap explanation
Use when: there is a period you need to account for.
Between [date] and [date] I was [reason, stated plainly]. Since [month] I have [what you did to restart: contract work, course, certification, freelance project]. I am applying for [role] because [one specific reason tied to the posting].
6. The returner
Use when: coming back to work after a long break.
I last held [role] in [year]. The field has moved in [specific way], and I have caught up on [specific thing] through [named course, project or reading]. What I bring that has not dated is [skill or judgement], which I used to [outcome].
7. The relocation
Use when: you are not local yet.
I am moving to [city] in [month], and the move is already arranged rather than conditional. Applying for [role] because [specific fit]. I can start on [date] and I am available for [interview format] before then.
8. The speculative approach
Use when: no posting exists.
I am not applying to a role — I am writing because [specific thing you noticed about their work, product or problem]. I do [thing], and at [place] that produced [outcome]. If [problem area] is on your list this quarter, that is the conversation I would like to have.
9. The short letter
Use when: the application says a letter is optional, or the reader is a founder.
Three sentences: what you want, the one thing you have done that answers it, and when you are free. A short specific letter outperforms a long polished one with a founder, and it is the version a tool is least likely to pad.
The paragraph you must write yourself
The evidence paragraph is the whole letter. A tool cannot know the outcome you produced, the number that makes it credible, or the system you actually worked in — and when it guesses, it produces confident vagueness that a hiring manager reads in two seconds. Everything else on this page can be generated and edited: the opening reason, the closing ask, the phrasing around the match. That one paragraph is yours, and it should contain at least one figure, one named thing, and one verb that is specific to your work rather than to your industry.
Phrases that read as generated
Some wording is a tell, not because it is wrong but because it is what a model reaches for. Cut these on sight:
- "I am writing to express my interest." Nobody writes this. Start with the reason.
- "I am a passionate / dynamic / results-driven professional." Adjectives about yourself are the least credible thing in a letter. Replace with one fact.
- "I believe I would be a great fit." Belief is not evidence. Name the requirement and answer it.
- "In today's fast-paced [industry]." Filler that delays the actual point by a sentence.
- Repeating the posting back. Restating their requirement is not the same as answering it.
Length, and what to cut
Around 250 words for most applications, and under 150 for the short version. If you are over 400, you are probably describing your career rather than making a match. Cut in this order: any sentence about your personal qualities, any restatement of the job description, the closing summary paragraph, then anything that would still be true if you swapped the company name.
Editing time, from our 30-day benchmark
Over thirty days of testing, a structured cover letter took roughly 12 minutes to produce with a general assistant and about 20 minutes with a low-cost dedicated writer — most of it spent on the evidence paragraph, which is the part that was never going to be delegated. The tools earned their time on the opposite problem: producing nine versions so you can see which structure fits, before committing to one.
Draft the shape, write the evidence
Generate the structure, then put the one paragraph only you can write in the middle.
Try Rytr →Frequently Asked Questions
Can I generate a whole cover letter?
You can generate the structure and the phrasing around it, but the evidence paragraph has to be yours. It needs a figure, a named system or a specific outcome, and a tool has no access to any of those.
How long should a cover letter be?
Around 250 words for most applications and under 150 for a short version to a founder. Past 400 words you are usually describing your career instead of making a match.
Should every application get a different letter?
The structure can repeat; the evidence paragraph and the opening reason should not. A letter that survives swapping the company name unchanged has not been written for that employer.
What do I do about a career gap?
State it plainly in one sentence, then say what you did to restart. Explaining less and following with concrete recent activity reads better than a long justification.
Do cover letters still get read?
They get read when they say something the CV does not. A letter that restates your history is skipped; one that answers a specific requirement in the posting is not.