# Why a cover letter should quote your resume

> A cover letter is believed when its claims can be checked against the resume beside it, so each claim should come from the resume itself. By default Zorlya writes each letter from the five passages of your resume closest to the job, or from one stored resume you pick, and may not invent a project, a number or an employer. You edit it before anything is sent.

Source: https://zorlya.com/blog/cover-letters-that-quote-your-resume

By Zorlya. Published 2026-09-19, updated 2026-10-25. Resumes and applications. 8 min read.

A hiring manager reads your cover letter and resume together, often with the resume open beside the letter. Every sentence in the letter is a claim, and the resume is where they check it. A letter that says you led a migration, when the resume shows no migration, does more harm than no letter at all. A letter that names the migration, the system and the number, and the resume shows the same thing, does the opposite. It saves the reader a step.

That is the whole idea behind how Zorlya writes cover letters. The letter is built from your resume, not from a description of the kind of person who might get the job.

## Should a cover letter repeat your resume?

No, but it should quote it. Repeating means listing your jobs again in sentences. Quoting means taking one or two lines the posting cares most about and adding what the resume had no room for: why you did it, how, and what it led to. The reader finds the same fact in both places, and the letter adds the part that makes it believable.

| The posting asks for | The resume line | The letter sentence |
|---|---|---|
| "Experience running supplier tenders" | Ran 12 supplier tenders a year for office and IT goods | Running twelve tenders a year taught me to write a specification suppliers cannot misread, and the last two closed without a single query |
| "Training non-specialist staff" | Trained 40 field staff on the new data app | When we moved field data to a phone app, I trained 40 staff in four districts, most of whom had never used one |

Illustrative: both rows are invented. In each, the letter keeps the resume's figure and name, so a reader can match them on the first look.

## What belongs only in the letter

Some things have no place in a resume and every place in a letter:

- Why this employer, in one specific sentence.
- A move to another city or country, and when.
- Your availability or notice period, if the posting asks.
- A change of field, and the link between the old work and the new.

These are not claims about past work, so there is nothing in the resume to check them against. Keep them short and true.

## Where a generic letter goes wrong

Ask a general purpose model for a cover letter and you get fluent text that could be sent to any company. It says you are a strong fit, that you are drawn to the mission, that you bring a wealth of experience. None of it is false, exactly. None of it can be checked either, and a reader can tell.

The model is not lying. It has no way to know what you did. Given a job title and a vague summary, it fills the gap with what letters for that kind of job usually say. Readers have seen that letter many times.

The fix is not a better prompt. It is giving the model the right evidence and forbidding it from going past it.

## How the evidence is chosen

When you add your resume, Zorlya splits it into short passages: your summary, each role and what you did in it, and your skills. Each passage is stored as an embedding, a list of numbers that places text by meaning. Every job in the feed has one too.

When you ask for a letter, Zorlya takes, by default, the five passages of your resume closest in meaning to that job. For a backend role asking for Postgres and queue design, those are the roles where you did that work, even if the words differ. For a developer relations role, a different five come up: the talks, the docs, the community work. The same resume gives a different letter for each job, because a different part of it is relevant.

Those five passages, the job's own description and its title and company are what the model is given. If you pick one of your stored resumes in the letter dialog, the model gets that file's text instead of the five passages. Nothing else about you is in front of it.

## The rules the letter follows

The model is told that every claim must come from those passages, and that it may not invent projects, numbers or employers. If a passage says you cut a build from 14 minutes to 3, the letter can say that. If no passage gives a number, the letter does not make one up to sound concrete.

The letter has three paragraphs and a fixed job for each:

- **The opening** names the role and the company, gives one specific reason for this company drawn from the posting, and follows it with one measured result from your resume that matches the posting's most important requirement. It may not open with "I".
- **The middle** gives two or three examples from your resume that answer the posting's core requirements, with at least one measurable result. It uses two or three of the posting's own terms where they fit naturally, not forced in.
- **The close** says what about this role connects to where you are heading, and asks for a conversation.

Some phrases are banned outright, because they mark a letter as one that was sent everywhere: "I am writing to", "to whom it may concern", "I am a perfect fit", "passionate about", "results-driven", "detail-oriented", "track record of success". So are em dashes and the vocabulary that readers have learned to spot as machine-written. A letter that reads as generated stops being read, however good its content.

You choose the tone, formal, warm or concise, and the sign-off follows it.

## When there is not enough to go on

If your resume has little that relates to the job, the five closest passages are still the five closest, and they may not be close. The letter will be thinner, because it is not allowed to fill the gap with invention. That is the right result. A thin letter tells you something true: this job asks for things your resume does not show yet.

When that happens, Zorlya's skill gap check is the more useful next step. It lists what the posting asks for that your resume lacks. If you have done the work and simply did not write it down, add it to your resume, and the next letter has it to draw on.

## You edit before anything is sent

The letter is a draft. You can edit it, and it goes nowhere until you send it. Zorlya never applies to a job or emails an employer on its own.

Read it the way the hiring manager will, with your resume open:

1. **Check every number.** Each one should be in your resume, in the same form. If a figure has changed since you wrote your resume, change both.
2. **Check every name.** Projects, products, employers and tools should match what your resume calls them. A reader matching a claim to a line should find it on the first look.
3. **Add what only you know.** The model only knows what is in your resume and the posting. Why this company, from you, is worth one sentence the model could not have written.
4. **Cut what you would not say aloud.** If a sentence sounds unlike you, it will read that way.

A letter that quotes your resume is easier to check, and a reader who has checked your first two claims tends to trust the third. The aim is not a letter that sounds impressive. It is one where every sentence holds up.

## Questions people ask

### Can I use an AI tool to draft a cover letter?

Check the employer's instructions first, since some ask you to write it yourself. If you use a draft, edit it until every claim is in your resume and every sentence sounds like you.

### How many examples should a letter give?

Two or three at most. One well told example the reader can check is worth more than five they cannot.

### What if the posting asks for something my resume does not show?

If you did the work, add it to your resume first, then quote it. If you did not, say what you have done that comes closest, or leave it out.

### Should the letter use the same words as the resume?

For names of projects, tools and employers, yes. For everything else, write in plain sentences.

## What we know and what we do not

We know what Zorlya gives the model and what the model is told, from the code and the prompt that run it. We do not know how a given employer reads letters, or whether it reads them at all. The letter's job is to be checkable, and only your edit can make sure it is.