10 min read
On competitive reqs, two resumes often parse the same score and read the same on paper. Same years, same stack, same title progression. You're not losing because your PDF is ugly. You're losing because nothing in the packet explains why this req and not the fifty others you could have applied to with the same file.
Check your resume for free first so the letter isn't compensating for a scrambled upload. Once the file parses, the cover letter field is where a recruiter learns what your bullets can't carry: a career pivot, relocation timing, or the one project that maps to a must-have buried in a side role.
You don't need a story about your childhood dream job. You need five steps, two edge cases, and a copy-paste skeleton that fits Greenhouse and Workday text boxes. Job searching's already slow. Don't burn an hour on a letter that repeats your summary line for line.
If you're applying to roles where optional cover letters sit empty on most submissions, that's your opening. A tight letter isn't extra credit. It's the tie-breaker when the resume stack looks identical after the parser runs.
Quick Wins
- Highlight three must-haves from the posting before you write.
- Open with the req title and one gap the resume cannot explain.
- Tie one must-have to a dated bullet with employer and Month Year.
- Paste plain text only. No Canva letter PDFs in Greenhouse fields.
What happens to cover letters on competitive US reqs
Most US corporate stacks still attach a letter field beside the resume upload. Greenhouse shows it in a tab. Workday stores it as plain text next to the parsed profile. Lever often asks for a short note in the application form itself.
Why cover letters still matter for competitive roles: when keyword filters leave a short list of similar files, recruiters open letters to break ties. They're not looking for passion prose. They want one proof line the resume didn't surface and a sign you read this req, not a template you mail to every employer.
A composite data analyst applying to a senior req might have Looker and SQL on the resume twice but never show they owned forecasting for a retail rollout. The letter names that rollout, the quarter, and the stakeholder. Same credentials. Different screen because the gap is visible in four lines.
Edge case: the posting marks the letter optional and you're short on time. Skip it if you'd only repeat the summary. Write it when you carry a pivot, relocation date, or contract-to-hire preference the resume would bury.
Edge case: internal referral. Mention the referrer in line two with permission, then still tie one must-have to a bullet. Referrals get opened. They don't replace proof you match the req.
Edge case: career change where your last title undersells the new lane. The resume might say Project Coordinator while the req wants Product Owner. The letter names the two shipped releases you ran without waiting for a title change. That context rarely fits in bullet one without crowding the parser-friendly layout.
Competitive reqs also mean more optional fields get read when the stack is deep. Hiring managers skim letters after an recruiter shortlist, not before the ATS pass. Your file still has to parse. The letter adds human context once you're in the maybe pile, not instead of fixing upload order.
Read how to pick US job titles that match your skills so the title on your letter matches the parsed resume. Mismatched titles between files is a common silent fail on competitive stacks.
Five steps to write a cover letter that breaks a tie
Work in order. Each step ends with a pass/fail check. Stop and fix before you paste into the portal.
Step 1: Mark three must-haves from the posting
Open the job description. Highlight three required lines: a tool, a scope number, or an ownership phrase. Ignore nice-to-haves until the letter is drafted.
Before: You start writing about being a team player before you know what the req owns.
After: Three highlighted lines sit in the margin: Salesforce admin, 200-seat rollout, QBR ownership.
Pass/fail: you can name three must-haves without scrolling. Fail? Read the posting again before step two.
Step 2: Name one gap the resume cannot carry alone
Pick the must-have your resume mentions weakly: a side project, a contract, a title that undersells scope, or relocation timing.
Before: Dear Hiring Manager, I am excited to apply for your open role. I have many years of experience.
After: Re: Senior Revenue Operations Analyst (Req 4482). My resume lists Salesforce, but your rollout note maps to the 180-seat implementation I led at a mid-market SaaS firm in 2024, not the admin work from 2019.
Line one is the req. Line two is the gap. No childhood story required.
Step 3: Tie one must-have to a dated bullet
Write one paragraph with employer, Month Year, tool, and outcome. Mirror the posting verb when it's honest.
Before: I am skilled in Salesforce and have worked with many stakeholders.
After: From March 2023 to Present at Northline SaaS, I rebuilt the quote-to-cash flow in Salesforce for 220 seats, cut manual QBR prep from six hours to ninety minutes, and owned weekly pipeline reviews with sales directors.
Numbers here are illustrative resume examples, not market claims. Swap in your real scope.
Step 4: Keep the file plain text for portal fields
Draft in Word or Google Docs, then paste into Notepad once to strip hidden formatting before you paste into Greenhouse or Workday.
Before: Two-column Canva export uploaded as a letter PDF when the portal asked for plain text.
After: Single column, 11-point Calibri, no text boxes, no icons. Paste into the letter field and scan for stray characters.
Edge case: the portal accepts only a PDF attachment for the letter. Export PDF from the plain DOCX, not from a design tool. Run the same text-select test you use on resumes.
Edge case: Lever and iCIMS free-text boxes with character caps. Write the opening and proof paragraph first. Cut adjectives before you cut the dated bullet. A 1,500-character cap still fits req title, gap, and one employer line if you drop filler greetings.
Save the letter as Firstname-Lastname-Cover-Letter.docx when upload is allowed. Match the resume filename pattern so recruiters see one candidate, not three random exports from different weeks.
Step 5: Close with scope and timing, not fluff
End with your current title, availability, and relocation or remote preference only if the req mentions location.
Before: Thank you for your consideration. I look forward to hearing from you soon.
After: I'm a Senior RevOps Analyst based in Denver, open to relocation to Chicago for a March 2026 start. Happy to walk through the Northline rollout on a call.
Copy-paste skeleton after you fill the brackets:
Re: [Exact job title from posting] · [Req ID if listed]
[One sentence: must-have from posting + gap your resume undersells.]
[Month Year] to [Month Year or Present] · [Employer] · [Title]
[One paragraph with tool, scope, and outcome tied to the must-have.]
[Current city], [relocation or remote line if relevant], [availability window].
[Your name] · [phone] · [email]
For resume alignment before you paste, see formatting mistakes that kill your resume with AI screening so the letter and file tell the same story.
Where cover letters lose on competitive stacks
Repeating the resume summary. If paragraph two lists the same tools as bullet three on the resume, the recruiter learns nothing new. Cut it.
Wrong company name. Mass-applied templates leave the last employer in the greeting. One typo on a competitive req and you're out before the resume opens.
Design PDFs in a text field. Greenhouse letter boxes want plain text. Fancy layouts paste as garbage characters.
Opening with filler. I am writing to apply wastes the only lines many recruiters read. Start with the req title and gap.
Listing every job you've ever held. One dated paragraph beats a career memoir. Competitive reqs want proof on the must-have, not a timeline.
Salary asks in line one. Unless the posting demands it, save comp for the recruiter call after interest is mutual.
Apologizing for gaps. State the contract dates and what you shipped during the gap. Don't lead with sorry.
Quoting the mission statement back. One line that shows you read the about page is enough. A full paragraph of values language with no proof reads hollow on competitive stacks.
Attachments when the field wanted paste. Uploading a letter PDF to a text box sometimes stores an unreadable file name with no body text. Paste first. Attach only when the req demands it.
This won't fix applying when you lack a posted must-have. It stops a qualified file from losing a tie because the letter repeated the summary while a rival named the rollout you both actually ran.
Draft the letter after the resume matches the req
Paste the posting into the job match score tool with your resume attached. Fix bullet one on the resume before you write the letter so both files cite the same must-have.
Need a plain-text first draft? Generate a cover letter from the posting text, then replace every generic line with your dated bullet from step three. The tool gives you structure. You supply the proof.
Send one letter worth reading
Why cover letters still matter for competitive roles comes down to ties. Resumes get filtered to stacks that look the same on paper. The letter is where you show you read this req and can name one proof line the bullets didn't carry.
Open your next competitive posting tonight. Highlight three must-haves. Draft four plain-text lines: req title, gap, dated bullet, timing. Paste into the portal field after you strip formatting once in Notepad.
Optional doesn't mean ignore. It means send nothing or send something a recruiter can use in ten seconds. One honest gap beats a page of enthusiasm.
Keep one master letter skeleton in a notes file. Swap req title, gap, and dated bullet per posting. Competitive search is volume with precision, not thirty unique essays per week. Ten minutes per letter is enough when steps one through three are already done from resume tailoring.
When the resume still needs a parser fix before you apply, run the free ATS checker on the same export you'll attach. Letters can't rescue a file that scrambled on upload.
Read more
Frequently asked questions
Submit one when you can name a specific gap the resume cannot carry: a career change, relocation timing, or a must-have that sits in a side project instead of a paid title. Skip it when you'd paste a generic three-paragraph template that repeats your summary. On competitive reqs, optional often means the recruiter reads letters only when the resume stack is tied. A tight letter wins ties. A generic one wastes the field.
Some US portals store cover letters as plain text beside the resume file. Greenhouse and Workday often show the letter in a separate tab recruiters open after the resume passes keyword filters. Fancy formatting, text boxes, and columns break the same way they break on resumes. Paste plain text. No tables. No header graphics. Match the filename story your resume already tells.
Aim for one screen on a laptop: opening line with the req title, one paragraph tying a posting must-have to a dated bullet, one paragraph on scope or relocation if relevant, and a closing line with your current title. Long letters bury the gap you needed to explain. Recruiters scanning fifty files read the first four lines. Put the must-have match there.
Yes. A letter that repeats the resume summary, misspells the company name, or opens with filler tells the recruiter you mass-applied. On competitive reqs where many files parse cleanly, that signal can drop you below a candidate who skipped the field entirely. Write one tight letter or leave the box empty when optional. Never submit a rushed template with the wrong employer name.