Short Cover Letter That Still Works

11 min read

You're told cover letters must be long to show effort. Then you watch a recruiter scroll past three paragraphs on a phone preview inside Greenhouse. That's the gap this page closes.

Brevity only works when every sentence carries proof. A short cover letter that still works isn't lazy. It's scoped to what the req asks for in paragraph one.

Before you draft, check your resume for free against the posting. Your letter should repeat one bullet recruiters can verify, not introduce new claims you can't defend in Experience.

Below is the bar good letters clear, five before-and-after pairs across US roles, what weak drafts share, and a copy-paste skeleton you can adapt tonight.

Job searching is hard enough without writing a second resume in prose. Keep the letter short and honest.

The standard a short cover letter that still works must meet

Strong letters have four parts: greeting with name when you have it, req identification, one proof paragraph tied to paragraph one of the posting, and a single closing ask. No third-page career essay. No buzzword cloud that repeats Skills without Experience backup.

Recruiters in Workday and Greenhouse often read the letter after they skim Experience. If the letter claims Salesforce admin work your resume never dates, trust drops. If the letter repeats bullet one in plain English, they keep reading.

I've screened stacks where the cover letter was longer than the resume and said less. The files that moved had four tight sentences and a req ID in the subject line when email allowed it.

Optional letters still matter on close-match reqs. Use them to explain a pivot, contract end, or relocation timing your resume can't carry in one line.

For openers that don't sound copied, pair this page with how to start a cover letter . For closings that get replies, see cover letter closing lines that get replies .

Before and after: short cover letter examples by role

Operations coordinator, mid-size SaaS

Before: Three paragraphs on passion for teamwork, no req ID, no metric, generic "I would love to join your dynamic company."
After: "Re: Operations Coordinator (Req 4421). I cut vendor onboarding tickets 18% last year by standardizing intake in Zendesk. Your posting asks for vendor SLAs and cross-team routing; that's the work I run today at Northwind. I'm available for a call Thursday or Friday."

Software engineer, product backend

Before: Letter lists ten languages, none tied to the team's stack in paragraph one.
After: "Applying for Backend Engineer on the Payments team. I shipped checkout APIs in Node and Postgres, reducing failed charges 9% in Q2. Your req highlights idempotent webhooks; I built that pattern at Contoso. Happy to walk through the design in a thirty-minute screen."

Registered nurse, hospital med-surg

Before: Emotional story about childhood dreams, no license line, no unit fit.
After: "RN application for Med-Surg Night Shift, Req 88102. BSN, ACLS, three years on a 32-bed unit with 1:5 ratios on nights. Your posting notes IV certification and rapid response coverage; I precepted two orientees on that schedule last winter. I can start after a two-week notice."

Digital marketing specialist, agency

Before: Letter repeats the resume Skills list and calls the reader "esteemed hiring manager."
After: "Digital Marketing Specialist, Studio Apex. I managed $120k monthly in paid search with ROAS targets set weekly in Looker. Your client brief mentions B2B SaaS lead gen; that's the portfolio I ran for two years. I'd welcome a brief chat on campaign structure for your Q4 launch."

Customer success manager, Series B

Before: Page-long letter about company mission with no churn or expansion metric.
After: "CSM role, Req CS-19. I owned a book of 28 accounts at $2.1M ARR and cut reactive tickets 11% by building a weekly health dashboard in Gainsight. Your posting stresses onboarding playbooks for mid-market; I wrote the playbook our team still uses. Open to speak this week."

Copy-paste skeleton for your next apply block. Swap brackets, keep the four-part shape:

{`Hi [Name or Hiring Team],

I'm applying for [Job Title] ([Req ID if you have it]). [One proof sentence from bullet one with tool and outcome].

Your posting calls for [phrase from paragraph one]; that's the scope I run today at [Employer on resume].

[One-sentence ask: availability for a call or screen this week].

Best,
[Your name]`}
              

Edge case: career pivot. Use the letter for one honest bridge sentence, then point to a project bullet that shows target work. Don't claim years in a title you never held.

Edge case: employed and applying quietly. Send the letter only when the portal requires it. Keep proof lines that match public resume text so nothing contradicts if your manager hears your name.

Edge case: referral from a friend. Name the referrer in sentence two if they agreed, then still cite one metric. Referrals open the door; proof keeps it open.

Numbers inside those sample sentences illustrate strong lines, not market claims. Your resume must already carry the same facts in Experience before you paste them into a letter.

When the posting forbids cover letters, respect the rule. Extra attachments sometimes auto-reject in strict portals.

Mobile previews truncate after a few lines. Put req title and proof in the first two sentences so the skim carries even if the rest collapses.

Don't open with "To whom it may concern" when the posting names a recruiter. Search the req footer or company careers page for a name before you default to generic.

Parents and caregivers: draft one template skeleton, then swap proof lines per req during a twenty-minute block instead of rewriting from scratch at midnight.

If you work nights, draft letters when you're alert enough to match paragraph one accurately. Tired copy introduces claims you'll regret in a screen.

Internal applicants should still write like externals. Name the internal req ID and one cross-team outcome hiring managers can verify in your current role.

Contract ends soon? One sentence on availability beats a paragraph on why the contract ended. Save detail for the recruiter call.

Remote reqs: mention time zone alignment only when the posting asks. Otherwise spend words on collaboration proof already on your resume.

Save each letter version next to the req ID in your tracker. Reuse structure, not identical sentences, when you apply to a similar title elsewhere.

So what if you hate writing about yourself? Treat the letter as a caption for bullet one. You're not selling your soul. You're labeling evidence recruiters already hunt in Experience.

Government and university portals sometimes strip formatting from pasted letters. Plain sentences still win. Avoid tables, icons, and colored text in the cover letter field even when the resume upload is separate.

When a posting asks for salary expectations in the letter, answer with a researched range tied to level and city, not a single desperate number. Keep it to one sentence so proof still dominates the skim.

Panel interviews later won't test your letter. They test whether your proof holds. Align the letter metric with the bullet you'll defend aloud under your current employer row.

Batch your letter drafts at the end of each apply block while the posting is still open. You'll notice faster when you're repeating the same weak opener across five companies.

Share this skeleton with a friend who keeps sending page-long letters. Make them trim to four lines before the next apply night you run together.

Confidence on cover letters comes from preparation, not from inventing new achievements. A calm four-line note backed by dated bullets is what US hiring teams expect when the fit is real.

Save sent letters in the same folder as the CV version you uploaded. Next year's you will thank you when a recruiter pings the old req ID again and asks for an update.

You won't fix a mismatched resume with a longer letter. Fix bullet one first, then paste the proof sentence that already survived your own read-aloud test.

If you're employed, shrink letter blocks before you drop resume tailoring. One honest letter on a high-fit req beats five generic paragraphs on roles you'd never take.

When silence might be fit, not letter quality, read your match notes before you rewrite prose. Often the fix is scope on the resume, not adjectives in paragraph three.

Don't schedule letter blocks when you're too tired to spell the company name correctly. Typos in line one kill trust faster than brevity ever will.

Career pivots should use the letter for one bridge clause only, then point to a project bullet that shows target work with Month Year dates recruiters can verify.

Open your calendar and book one twenty-minute letter block after your next resume tailor session. Order matters more than inspiration.

What weak short cover letters share

Repeating the entire resume in prose. Recruiters already have the file. Give them one line they'll remember.

Opening with company history you copied from the website. They work there. They know. Jump to fit.

Claims with no dated bullet behind them. Letters aren't magic zones for skills you never listed under an employer.

Before: 400-word letter, zero req ID, no metric.
After: 140-word letter, req in line one, one proof sentence, one ask.

Multiple CTAs. Pick one next step. "Happy to chat Thursday" beats three optional times scattered across two paragraphs.

This won't get you an interview when the resume misses must-haves. It stops a close match from losing the skim because the letter wasted the recruiter's ten seconds.

Draft tools after bullet one is honest

Write the letter after you tailor bullet one on the resume for that req. Order matters. Proof first, prose second.

Paste the posting into score your job match before you pick the proof sentence. If level is off, skip the letter and the apply. If wording gaps are small, tailor then draft.

Use the cover letter generator to spin a four-line draft from your resume text, then edit until every claim appears in Experience. Delete any sentence the generator invents that your file can't support.

Send one short letter on your best req tonight

You don't need a novel. You need req ID, one verified proof line, and a respectful ask recruiters can answer in one email.

• Highlight three words from paragraph one of the posting.
• Paste the four-line skeleton and fill brackets.
• Trim past 200 words before sign-off.
• Save the letter next to the resume version you uploaded.

Open your tracker on the req you fit best. Run a free ATS check on the resume first, then drop the short cover letter that still works into the portal field.

You'll feel like you're not trying hard enough at 150 words. Recruiters will finally see the point without digging.

Reuse the skeleton tomorrow with a new proof line. Structure stays. Evidence changes. That's how short letters scale without turning into spam.

When a recruiter replies asking for work samples, send the link in a follow-up email, not inside the cover letter field. Keep the initial letter focused on req fit and dated proof.

Acronyms belong in the letter only when the posting uses them first. Spell the term once if your resume already does, so mobile previews stay readable.

You don't need a new letter for every req at the same company if titles differ. Rewrite line one and the proof sentence. Keep the closing ask identical if timing matches.