8 min read
You can have a decent resume and still lose momentum on the letter. The coordinator opens attachments in order. When the letter reads like a mail merge, they'll stop before your best bullet.
That is not because cover letters are magic. It's because the second file either adds proof or adds doubt. If you wouldn't say it out loud to a recruiter, it shouldn't ship as a PDF.
Check your resume for free first if you have not lately. A letter cannot rescue a file that already parsed wrong in Workday.
Below is a diagnostic path: what the symptom looks like, which mistake causes it, and a before-and-after line you can paste tonight. You do not need a new template. You need one paragraph that could not belong to another company.
Quick Wins
- Search the letter for the last company name you applied to. Replace every stale name.
- Cut any paragraph that repeats a resume bullet word for word.
- Name the req title and one metric the resume already proves.
- Stop at one screen. Move extra proof back to the resume.
When the letter confirms a pass
The symptom is silence after a borderline resume. You are not auto-rejected. You are also not moving to a screen. The letter was the tie-breaker, and it broke the wrong way.
Optional letters still get opened when the req is competitive. Required letters get opened every time. In both cases, a generic file tells the reader you batch applied.
Cover letter mistakes that reduce interview chances cluster into four causes: stale company names, resume duplication, vague motivation, and format noise that breaks preview in Greenhouse or Lever.
None of those are fixed by a stronger thesaurus. They are fixed by deleting the paragraph that caused them and replacing it with one line tied to this posting.
Optional does not mean invisible. Competitive reqs still get human eyes on every attachment. Treat optional as a chance to add one fact the resume layout could not carry, not as a dump for your generic intro.
If the portal only accepts plain text, paste from Notepad once. If the greeting or company name disappears, rebuild in Word or Docs as a single column before you tailor again.
If you are unsure whether the letter mattered, read whether cover letters still matter for ATS for when to skip the upload entirely.
Before-and-after fixes by mistake type
Stale company or role name
Before: I am excited to join Acme Corp as a Senior Analyst, copied from yesterday's application while today's req is at Northwind Logistics.
After: I am applying for the Revenue Operations Analyst role at Northwind Logistics. Your posting asks for Looker ownership; I built weekly flash reports for twelve stakeholders in my current role.
Run Find on the company name from your last application. Do it before you change the greeting.
Resume pasted into prose
Before: A long paragraph listing every tool in your skills section with no link to this req.
After: One sentence on scope, one sentence on the posting's top requirement, one close. The resume already carries the tool list.
If a sentence could live as a bullet under your current job, it should live there, not in the letter.
Motivation with no proof
Before: I am passionate about your mission and would love to contribute to your dynamic team.
After: Your req mentions cutover support for a Workday rollout. I supported three payroll cycles during our last HCM migration and documented test cases recruiters could audit.
Passion is cheap. A named system and a scope line is not.
Format that breaks preview
Before: A designed PDF with columns, icons, and colored headers exported from a canvas tool.
After: A single-column DOCX or text PDF with the same contact lines as your resume, standard bullets, and no graphics.
Letters fail parsing the same way resumes do. Plain text wins.
Address blocks also trip uploads. Keep street lines out unless the posting asks for a full header. City and state plus email and phone match what you used on the resume.
Opening line that wastes the screen
Before: I am writing to express my interest in opportunities at your esteemed organization.
After: I am applying for the Staff Accountant role on your careers site. I closed three consecutive monthly books with NetSuite in my current job.
The second version names the req and one outcome. That is enough for paragraph one.
Copy-paste block: tight three-paragraph shell
Copy-paste cover letter shell (edit brackets)
[Your name]
[City, State] | [phone] | [email]
[Month Day, Year]
[Hiring manager name or Hiring Manager]
[Company name]
Dear [Name or Hiring Manager],
I am applying for the [exact job title from posting] role at [Company]. [One sentence on scope you already proved in a resume bullet with a tool name.]
[One sentence tying a posting requirement to a result you can defend in an interview. No new tools you cannot explain.]
Thank you for your time. I would welcome a conversation about [one topic from the posting].
Sincerely,
[Your name]
Pair the shell with cover letter closing lines that get replies so you do not end on a weak thank-you.
Which failure mode is yours
Wrong company in the first line means stale template. Fix names before you tweak adjectives.
Letter longer than your resume means duplication. Cut half, then cut again.
No posting keywords in the body means you did not read the req. Mirror one required skill with a proof line you already own.
I've screened stacks of these in Greenhouse, and the letter that survives is boring, short, and impossible to confuse with another company on the board.
Before: Dear Sir or Madam, I am a hardworking professional seeking new opportunities.
After: Dear Hiring Manager, I am applying for the Client Support Lead role listed on your careers site. I handled forty-plus Zendesk tickets weekly with a documented CSAT target in my last role.
This will not fix a resume that is the wrong level for the req. It stops a good file from looking careless on the second attachment.
Draft without starting from a blank page
Start from the posting, not from last week's letter. Paste the req into score your job match and pull one requirement you can prove in a single sentence.
Then use Generate a cover letter as a draft you still edit for company name, role title, and one metric from your resume.
Do this now: Open yesterday's letter and search for any company name that is not today's employer. If you find one, do not upload until it is gone.
Upload checklist for the next application
Cover letter mistakes that reduce interview chances are visible in five minutes of editing. You are not chasing flair. You are removing duplicate resume text and stale names.
- Company and role names match this posting only.
- One screen, one proof point, one clean close.
- Contact block matches the resume file byte for byte.
- Plain export with no columns or icons.
Run the free ATS checker on the resume, then read the letter aloud once. Job searching is draining enough without giving a coordinator an easy reason to pass.
Read more
Frequently asked questions
Yes, when you upload a sloppy file anyway. A optional field still lands in Greenhouse or Lever as an attachment. A wrong company name or a wall of resume bullets tells the coordinator you did not read the req. Skip the upload if you have nothing new to say. Do not ship a recycled paragraph just to fill the box.
Most pipelines rank the resume profile first. The letter matters when a human opens attachments, when the req marks the letter required, or when you need context the resume cannot carry alone. Parser errors on a letter still look bad in preview. Keep one column, plain text, and the same contact block as your resume.
Treat one screen as the cap. That is roughly 250 to 350 words in 11-point Calibri with normal margins. Recruiters skim for role name, one proof point, and a clean close. Past that, you are asking them to read a second resume. Move bullets back to the resume file.
Only when the posting asks. Salary early reads like you are negotiating before you are invited. Relocation belongs in one sentence if the role is clearly on-site in another city. Otherwise save it for the recruiter screen. The letter should answer why you fit this req tonight, not your entire life plan.