12 min read
You're not confused because cover letters are mystical. You're confused because half the advice still treats them like homework from 2008 while your actual bottleneck is a Workday preview that mangled your phone number.
If you're applying tonight, don't start with a blank letter doc. Check your resume for free first. You're confirming Experience imported in order and that must-have terms still live in recent bullets, not only in a Skills list the parser ignored.
Job searching when you're tired of rewriting the same paragraph for every company is brutal enough. You don't need guilt about optional uploads. You need a straight rule for when a letter changes a human's mind and when it's theater.
Below: the symptom that makes people over-write, three causes that actually justify a file, how to tell which cause is yours, fixes for each, and portal behavior in Greenhouse and Workday. When a letter is warranted, generate a cover letter from your resume and the posting so you edit specifics instead of inventing structure at midnight.
Quick Wins
- Required upload: three short paragraphs, half a page max.
- Optional upload: skip unless referral, pivot, or top-five target.
- Never upload the resume PDF into the letter field.
- Name files FirstLast_Company_CoverLetter.pdf before you submit.
What's the point of a cover letter when the resume already applied?
The point is not tradition. It is selective persuasion when the resume alone leaves a recruiter guessing. Corporate talent queues sort on title, employer, and recent scope. A letter does not override a level mismatch. It explains the weird part a six-second skim cannot decode.
The symptom I see most is guilt writing: optional field checked, three paragraphs of passion, zero new facts. That file often signals spray applying harder than an empty optional slot. The opposite symptom is absolute refusal, even when a hiring manager at a twelve-person company would have opened a tight note.
So think in jobs the letter does, not in moral obligation. Job one: close a narrative gap. Job two: satisfy a required upload without embarrassment. Job three: give a human skimming on a phone one reason to keep reading when titles look off-pattern. Everything else is optional noise.
Parsers still weight the resume. For how files die before humans see them, read why your resume never reaches a human . Fix that path before you debate letter philosophy.
Internal transfers, federal-style narrative statements, and nonprofit culture screens stretch the definition. Those are still letters, but the reader expects structure and mission fit, not a restated bullet list.
Edge case: the posting forbids cover letters. Obey it. Edge case: employee referral with a warm intro email already sent. A two-line letter that names the referrer once may still help the recruiter connect records; a page of fluff does not.
This will not rescue applying to senior roles with coordinator scope in your last five years. It stops a qualified file from getting archived because nobody understood why a teacher is now applying to instructional design.
Three causes and how to tell which is yours
Diagnostic posts fail when they list tips without sorting symptoms. Use three causes. If none match, you probably do not need a letter tonight.
Cause 1: The portal requires a file
Workday and Greenhouse often mark the letter mandatory even when the req text sounds casual. The point here is compliance plus competence: show you can follow instructions and write in plain English. Length beats poetry. Half a page with company-specific nouns from the posting beats a blank upload or resume duplicated into the wrong field.
How to tell: the submit button stays gray until a document attaches, or the form labels the field required with a red asterisk. Fix: write four beats, hook, two proofs mapped to the JD, context only the letter can carry, close with availability. Export a clean PDF with selectable text.
Cause 2: Your resume has a story gap
Career changes, return from caregiving, relocation without a local address line, contract stacks that read like hopping, or a license earned last year all create gaps titles cannot carry alone. The letter is a bridge paragraph, not a second resume.
How to tell: you hesitated on the summary because the truth needs a sentence the bullets cannot hold. Fix: one paragraph on the pivot proof, one on why this employer, zero repetition of every Experience row.
Cause 3: A human with a small pile still reads
Founders, agency principals, hiring managers at sub-fifty-person shops, and mission-driven teams often read letters when volume is low. The point is culture and motivation fit, not keyword density.
How to tell: the posting asks open questions, mentions values, or comes through a personal network. Fix: write like email. Short paragraphs. One project detail that could only belong to this company.
Worked example: operations analyst, career change
Before: Letter opens with "I am excited to apply" and repeats six resume bullets about classroom teaching.
After: Two paragraphs: built district scheduling dashboards in Google Sheets serving forty schools; applying to this ops analyst req because the posting names cross-functional inventory work you already did during COVID supply runs.
Worked example: software engineer, referral
Before: Generic letter with no referrer name; resume already strong for the stack.
After: Three sentences naming the referring engineer, one shared shipped feature, and why you want this team’s platform area; half page total.
Worked example: enterprise req, optional letter
Before: Optional letter uploaded with swapped company names and "synergy" language.
After: Optional field left blank; hour spent tightening two recent bullets to match the JD nouns and re-exporting PDF.
I've screened Greenhouse folders where the cover letter was the only place the candidate explained a contract gap, and the resume timeline looked like job hopping until that paragraph landed.
Copy-paste block: minimum viable cover letter
[Your name] | [email] | [phone] | [city, state]
[Hiring manager name if known, else Hiring team]
Dear [Name or Hiring team],
I am applying for the [exact job title] role at [Company]. [One sentence bridge the resume cannot show: pivot, referral, or relocation.]
In my current role at [Employer], I [outcome verb] [specific deliverable] that [result tied to JD noun]. Previously, I [second proof mapped to posting language, not a bullet dump].
[Optional third paragraph: why this team or product, one company-specific detail from the site or posting.]
Thank you for your time. I am available for a conversation [general window].
Sincerely,
[Your name]
File name: FirstLast_Company_CoverLetter.pdf
Edge case: multiple locations on the posting. Pick the city you can truthfully work from and say so once. Edge case: salary history questions in the portal. Answer in the form fields; do not bury compensation demands in the letter unless the posting asks for it there.
Edge case: academic CV norms versus corporate half-page letters. If you are applying outside academia, shrink the prose to business length even when your CV is five pages.
When Cause 2 applies, mirror one verb from the posting in paragraph two, not in every sentence. You are showing you read the req, not playing mad libs.
For how recruiters read titles before they open attachments, see how recruiters interpret job titles . Align title lines first, then decide if a letter still adds signal.
Beliefs that waste your hour
Treating the letter as an ATS keyword bag. Stuffing the posting into a paragraph does not beat a clean resume match. Humans smell it instantly.
Assuming brilliance rescues a broken resume. If Experience imports empty in preview, the letter never gets opened.
Writing when the posting says not to. Instructions are a screen too.
Uploading the resume twice. Filling the letter slot with the same PDF signals you did not read the form.
Before: "I am a passionate, detail-oriented team player excited for this amazing opportunity at your esteemed organization."
After: "I shipped a Workday reporting pack that cut manual headcount reconciliations from three days to six hours for a 900-person business unit."
Before: Page-long autobiography starting in high school.
After: Three paragraphs, each under four lines on screen, every sentence tied to this req.
Fancy letterhead images and two-column designs break text extraction the same way bad resume layouts do. Plain single column, 11-point Calibri or Arial, saved as PDF with real text.
Apologizing for missing skills in the letter instead of fixing bullets trains the reader to focus on gaps. State what you have done that rhymes with the JD, not what you lack.
Saving as CoverLetterFinal_v7.pdf in a shared recruiter inbox forces extra clicks. Use names humans can search.
Waiting until the letter is perfect while the application deadline passes hurts more than submitting a tight half page with a verified resume. Done beats ornate.
Addressing the letter to "Dear Hiring Manager" is fine when names are hidden. Guessing a VP name wrong looks worse than a neutral greeting.
If you already submitted a weak letter to the same company last month, do not attach a second file on a new req unless the portal forces it. Focus the new apply on a sharper resume and a fresh form.
Typos in the company name or job title line are instant discard signals. Spell-check the posting title character for character before upload.
Fix the resume, then decide on a letter
Upload the same PDF you will submit to HireFlow's free ATS resume checker . Confirm dates, employers, and must-have terms survived export. That scan takes less time than writing a letter for a role your resume already mismatches.
When the diagnostic says you need Cause 1 or 2, generate a cover letter draft from your resume text and the posting, then replace every generic sentence with a company-specific fact you can defend on a call.
Do this now: Run the resume scan, pick cause 1, 2, or 3, write only if required or gap-driven, name the PDF, submit one application you actually want.
What to do on the next apply
What's the point of a cover letter? To answer a question your resume leaves open, or to satisfy a required upload without looking sloppy. It is not a second resume, not an ATS cheat code, and not mandatory for every Greenhouse click.
- Scan the resume PDF before you write a word.
- Label cause 1, 2, or 3 for this specific req.
- Skip optional fields when you'd only paste a template.
- Keep required letters under half a page with JD nouns.
- Name the file so a recruiter can find it later.
Open the posting one more time. Run a free ATS check , fix import issues, then write only if the form or your story demands it.
Read more
Frequently asked questions
The point is a narrow argument for fit when titles and bullets leave a hole: pivot proof, referral context, relocation timing, or a required upload. Recruiters in big queues often never open the file. Hiring managers and small teams still do when the pile is thin or the resume looks odd on paper. If your story is obvious from Experience alone, put the hour into resume bullets instead.
Workday, Greenhouse, Lever, and iCIMS usually attach the letter to your profile and may index the text. Screening still centers on resume fields, knockout questions, and recent role match. Keyword stuffing in the letter reads fake when a human opens it. Write plain sentences for the person who might read, not for parser fantasy.
Optional means skip unless you have one sharp reason: employee referral, career change bridge, gap you will not hide in bullets, or a top-five target role. A generic optional letter can signal spray applying more than an empty field. Required means upload something tight even if prose is not your strength.
No. Broken PDF layout, missing Month Year dates, and vague bullets kill you before anyone debates letter quality. Fix the resume export and recent role language first. A letter explains context; it does not replace Experience rows parsers map to the req.
No. Batch portal applies deserve a strong resume and honest forms, not forty half-page essays. Reserve letters for required fields, weird stories, and roles you would take a phone screen for tomorrow. Three tailored letters beat thirty swapped company names.
