Cover Letter Mistakes to Avoid Before You Send It

Cover letter mistakes to avoid are generic wording, claims you cannot prove, wrong names, and instructions you skipped. A useful letter links verified experience to this role and a need the employer stated. Treat the fixes as an editing sequence for U.S. roles and cross-border moves, not as a forecast of who gets called.

Three things to remember

1. Name the exact role and one posting signal before you praise the company.
2. Tie every skill claim to work you can find on a resume, portfolio, or note.
3. Proofread names and files on a pass that ignores style.

Twelve mistakes worth fixing first

Work this list as a revision checklist. The numbering is an edit order. It is not a risk ranking.

No single item decides who gets an interview. A clean letter can still lose to a closer match. A sloppy one can bury a strong match. Fix what you control.

1. Sending the same generic letter for every role.
2. Opening with vague enthusiasm or a stock interest line.
3. Repeating resume bullets instead of adding context.
4. Focusing only on what you want from the job.
5. Claiming soft skills with no example behind them.
6. Using the wrong employer name, role title, or recipient.
7. Leaving spelling, grammar, attachment, or formatting errors.
8. Writing too much, or making the letter hard to scan.
9. Stuffing keywords, or faking a personal detail.
10. Leaving copied, template, or AI language unedited.
11. Overstating a qualification, or apologizing for a gap you can explain.
12. Ignoring file type, prompts, naming, or submission rules.

Keep the list beside the draft. Run it once before you fuss over tone.

Give the substance a pass before style. Open the posting and mark two signals you can meet. Circle the resume lines that prove them. Write those connections in plain sentences. Only then touch greeting, length, and tone. Polish a generic draft first and you will spend the hour making filler sound smooth.

Applying to several roles this week? Clone the checklist, not the polished letter. The examples have to change. Otherwise the name-swap problem returns on application three.

A name swap is not a tailored letter

Thing is, a lot of drafts fail before the second paragraph. They could go to any employer. Tailoring means you name the exact position, pick a real priority from the vacancy, and connect one piece of your history to it. Replacing one company name is not enough.

What to pull from the posting

Read the ad and mark two or three signals you can honestly meet. A duty you have done counts. So does a tool you have actually used. Then choose one or two achievements that match. The rest of your career stays on the resume.

Here is a small edit. Fill the brackets with your details. Do not borrow metrics from another person's letter.

The posting in this example asks for vendor coordination and weekly stakeholder updates, plus use of a named CRM. Your true evidence is narrower. You timed vendors on a launch and sent a Friday note to sales and support. You logged those notes in the CRM. You did not build dashboards.

A fair line reads: "For the [exact role], I coordinated vendor timing on a launch and sent weekly updates to sales and support in [CRM]. That lines up with the posting's focus on vendor coordination and stakeholder updates."

Do not upgrade it. Logging notes is not dashboard work. Say the smaller true thing.

Empty praise sounds like this: "I have always admired your company and would love the opportunity to join your team."

A tighter link: "For the [exact role] position, my experience coordinating [verified project] connects with the posting's focus on [specific need]."

The second line only works if the brackets are true. This tailoring walkthrough shows the same shift in its after version: name the role, use the posting's priorities, and swap broad enthusiasm for proof.

Openings that could be mailed anywhere

"I am writing to express my interest in this exciting opportunity." That line names no role and gives the reader nothing to check.

Try a plainer shape. "In [relevant function], I have [verified responsibility]. I am applying for the [exact role] because the posting emphasizes [specific capability]."

That shape is a pattern, not a rule. You might open on one accomplishment. You might open on why this employer's stated work fits what you have done. There's no required word count for those first lines.

Put the job title in the first sentence. You can sound human after that. Warmth before the title just delays the point.

Don't open with an apology about your current title. The reader has the resume. Use the first lines to show the overlap.

Stop retelling the resume

The resume already lists selected facts. The letter should say why one fact matters for this job. Retype every bullet as a paragraph and you have a slower resume.

Readers notice. They skip.

A resume line might read, "Coordinated [process] with [stakeholders]." A letter line can add the link: "That coordination depended on [relevant capability], which matches this role's focus on [job-ad signal]."

One link is enough. You won't strengthen the page by walking through the other six bullets.

The letter that is only about your plans

Motivation can sit in the letter. It goes flat when the page is a growth plan and nothing else.

"This role would help me grow and develop my career." That tells the reader what you want. It does not show what you bring.

Pair the want with their work. "I am interested in the [role] because it focuses on [stated work]. My experience with [verified responsibility] fits that focus."

Don't promise a sales lift or a culture change. You don't control those outcomes.

Soft-skill labels with no scene behind them

"Hardworking," "innovative," and "excellent communicator" are labels. You can't verify a label from the adjective alone.

The stacked version is easy to spot. "I am hardworking, innovative, an excellent communicator, and a team player."

Swap it for one scene you can stand behind. "On [verified project], I worked with [colleagues or stakeholders] to finish [documented responsibility]. I was the person who kept [specific information] moving across that group."

If your past employer did not track work in percentages, use scope instead. Say how often you did the task. Say who relied on it. Name the tool and the constraint. Those details are evidence.

It is easy to bolt a number onto a plain sentence because the draft feels thin, and then the figure is hard to place, it might have been a quarterly note or it might have been an example in another letter you had open, and that is how a small exaggeration becomes the line you get asked about first.

Cut it if you cannot source it.

Keywords, templates, and the draft you still have to edit

Turns out, repeated words in a posting are clues, not a spell you have to cast. If the posting repeats a phrase like stakeholder updates and you actually did that work, put the phrase in the same sentence as the proof. Don't give it a paragraph of its own.

Fake personalization fails the same test. "I love your mission to innovate" is still generic if no detail from the posting supports it. Mention a product, office, or project only after you have checked it. A wrong detail is worse than a quiet letter.

A pass for templates and generated text

A template can break a blank page. A drafting tool can suggest an order. Neither one knows your work history.

Genwriter's notes on tailoring from source material set a plain test. Start from documents you can verify. Describe a partial match as partial.

Before you keep a generated sentence, run four checks:

• Delete placeholders and any company name left from another application.
• Match each tool, title, metric, and outcome to your resume, portfolio, or notes.
• Cut "perfect fit," "proven track record," and "passionate about" unless the next sentence proves the claim.
• Read the draft aloud and rewrite any line that does not sound like you at work.

You'll hear the template voice when you read aloud. It's usually smoother than you, and vaguer.

If a line claims a tool you only saw in a demo, say so or delete the line. The tool can't do that check.

Names, length, gaps, and the form's instructions

Wrong details sink a careful argument. Start with the employer name and the exact role title. If you name a recipient, confirm that person too.

Then look at dates you chose to include, and at the files attached. The letter and the resume should use the same titles and the same dates. A mismatch reads as carelessness even when the prose is fine.

Two passes beat one tired read. First pass is facts only. Names, titles, dates, claims, attachments. Second pass is language. Spelling, grammar, spacing, paragraph breaks.

Ask another person to read the file if you can. You stop seeing a wrong company name. They won't.

If you use a letterhead, the phone number and location should match the resume. Spell the city and country. A foreign postal-code format can confuse a U.S. reader who has never seen it. Use one spelling of your name on the resume, the letter, and the file name. Mixed transliterations can look like two different people.

Length, formatting, and the scan test

Short paragraphs are easier to scan. Spacing that matches the rest of the application helps too. A clean font matters less than a point the reader can find fast.

Length guides are flexible. Relevance beats a target word count. Plenty of U.S. employers want a short note. Sometimes it sits in a text box with no letterhead. Write to the box. Don't attach a full letter the form never asked for. Don't paste letterhead into a field that will strip it.

Some roles outside the U.S. ask for a longer motivation letter. Academic and public-sector posts sometimes do too, because the prompt asks for more. Follow the prompt in front of you. A habit from another country is not a rule here.

Cut resume repetition first. Then cut the generic opening. Adjective strings can go. So can a motive you already stated. Background that never touches this role can go too.

This version wanders: "I am very excited about this wonderful opportunity because I have always wanted to work for an organization like yours. I believe my background, skills, and experience could potentially make me a great addition to your team and would allow me to grow professionally."

This version gets to the point: "I am applying for the [role] because my experience with [verified responsibility] matches the posting's focus on [specific need]."

Keep one motive sentence if it adds a real reason. Delete the echo two lines later.

Overstatement and the apology reflex

Say what you have done, at the real level. You can note a missing qualification without apologizing for existing.

"I know I do not have all the experience you are looking for, but I hope you will consider me." That sentence spends its energy on the gap.

Use a plainer pair. "My experience in [verified transferable area] matches the role's focus on [requirement]. I have not worked with [missing tool]. I have used [adjacent skill] for [verified task]."

The expert claim is the mirror problem. "I am an expert in [requirement]." If that is not accurate, write the exposure you actually have. "My experience includes [actual level]. I can explain how it relates to [role requirement]."

Confidence here is precision. A bigger adjective is not confidence.

Career changers can use the same pattern without borrowing a title. "I have not held the title [target title]. I have [verified adjacent responsibility], including [task the posting names]."

If a form asks about work authorization, answer with facts you know. Don't sketch a visa plan in the letter. Work permits are a legal question. This page is not legal advice.

When you skip the instructions

Read the instructions before the polish pass. Look for file type, a question on the form, a length cap, a required file name, and whether they want email or an upload. That's a lot of small rules. Missing one is still a miss.

Answer the question they asked. A general letter that dodges the prompt looks unread. If they want a PDF named Lastname_Role_CoverLetter, use that name. Wit in the file name does not help.

If the posting says to email the letter, put the exact role in the subject line. Attach the file they requested. Don't make the email body a second full letter on top of the attachment. One version is enough.

If the form has no letter field and does not ask for one, stop looking for a hidden upload. The resume has to carry that application.

Optional does not mean you must upload a letter to be taken seriously. CreateResume's note on optional letters puts it plainly. The employer will accept the application without one. A generic letter is still a weak letter.

Send one when it adds context the resume cannot carry. A career change, or a move the dates do not explain, is often that missing context. Skip the letter when you would only repeat the resume to fill an upload. If a later step requests a letter or a written answer, write it then.

Whom to address, and how much to say

Customs move. A named recipient is better when the name is reliable. It is not required on every form. Never guess a name. Never guess a title just to force a greeting.

Decision	Use it when	Skip it when	A workable line
Named greeting	The posting or a page you trust names a person	You are guessing from a search	Dear Jordan Chen,
Team greeting	No reliable name exists	A named contact is clearly listed	Dear Hiring Team,
Short letter	One link and one piece of evidence fit briefly	A required prompt is still unanswered	Opening, one proof paragraph, close
Fuller letter	The form asks a question, or a move needs a short explanation	You are retelling the resume	Two proof paragraphs, then stop
Optional letter	It adds context the resume lacks	It duplicates the resume	Why this work fits this team

"To whom it may concern" can still be fine when you cannot find a person. "Dear Hiring Team" is often warmer and just as clear. Don't invent a name because a search returned three similar profiles.

Pick the level of detail from the posting, the evidence you have, and any prompt. A straight match often needs less prose. A career change may need one extra paragraph on why the shift is deliberate. to be honest, that extra paragraph is where a second resume hides. If you cannot name what it adds, cut it.

Applying across a border

This is the part a lot of letter advice skips. It matters if you are moving countries or aiming at a U.S. role from abroad. Match the letter to the market on the posting. Don't copy the last market you applied in.

U.S. corporate applications often want a short, specific note. Sometimes that note lives in a text box. Lead with the role and the evidence. Save the story of the move for one factual sentence. Name the city or region you are targeting, or the work arrangement the posting already describes.

Some employers in other countries expect a motivation letter. They want to know why that organization, and why you are making the move. If the prompt asks for that, answer it. Don't import the longer form into a U.S. box that is only a few lines. Don't import a clipped U.S. note into a process that asked for a statement of interest.

A few mechanics change too. Date formats trip people up. Month-first dates are common on U.S. letters. Day-first dates are common elsewhere. A mismatched date is small. It still looks careless.

Honorifics are not universal either. If your home title would confuse a recruiter outside your country, explain the work in plain words instead of inventing a local title. Leave the foreign title as it is.

Say where you are aiming the application if the posting is ambiguous. Keep that sentence factual. Don't promise a relocation date you have not planned. Don't turn the letter into an immigration essay. Salary talk and contract review do not belong here either. Those are separate conversations.

Here's a workable line. "I am applying for the [exact role] based in [city or region stated in the posting]. In [current or recent role], I [verified responsibility] for [verified scope], which matches the posting's focus on [signal]."

No apology for applying from abroad. No claim that a visa is simple or already sorted, unless that is true and the form asked. If you are unsure what you can say about status, answer only what you know. Get that answer from an official or qualified source, not from a template. This article cannot tell you how a specific employer will read an international application.

The bottom line

Match the letter to the exact role. Back claims with work you can verify. Follow the file rules and the prompt.

Run this check and stop:

• [ ] Job title and employer name match the posting.
• [ ] One or two real examples answer two or three signals from the ad.
• [ ] The letter explains relevance instead of copying resume bullets.
• [ ] Soft-skill lines have a task or project behind them.
• [ ] Placeholders, old employer names, and empty praise are gone.
• [ ] Greeting, dates, and attachment names are correct.
• [ ] File type, file name, length, and submission method match the instructions.
• [ ] Facts and language were read on separate passes.

Save the file in the format they asked for. Send that file. Not the older draft still open in another tab.