Cover Letters That Aren't Filler: A Tight Structure That Earns Its Half-Page

Most cover letters are written to be skimmed and then ignored, and the writer can feel it. So they hedge. They open with "I am writing to apply for the position of...," restate the résumé in softer sentences, declare themselves passionate, and sign off. The reader learns nothing the résumé didn't already say.

A cover letter earns its place only when it does something the résumé can't: connect one specific requirement in the posting to one specific thing you've done, in your own voice. That's the whole job. Here is a structure that does it in about half a page, plus an honest account of when writing one is worth your time at all.

Open by naming the match, not yourself

The first sentence is the only one you can count on being read closely. Don't spend it on a throat-clear. Skip "I am writing to apply for..." - the reader knows which job this is; it's stapled to your application.

Instead, read the posting and find the requirement that sits at the top, the one the role clearly turns on. Then open by naming the thing you've done that maps to it. You're answering the unspoken question - "can this person do the main thing?" - before they have to ask it.

Say the posting leads with "own the migration of a legacy billing system to a new provider." A strong first line might be: "I've run two billing-platform migrations end to end, including the one that moved 40,000 active subscriptions off a homegrown system with no billing downtime." Concrete, matched to the lead requirement, and it makes the reader want the next sentence. Compare that to "I am a detail-oriented professional with a passion for fintech." One of these you'd keep reading.

You don't need a clever hook or a story about your childhood. You need the single most relevant fact about you, stated plainly, up top.

Prove it with one concrete story

After the opening claim, back it with one example - not three, not a tour of your career. One story you can tell in three or four sentences, with a real situation, a real action you took, and a result you can describe honestly.

Keep it specific and keep it yours. The pattern that works:

• The situation: what was broken, stuck, or at stake.
• What you did: the action, in active voice, with you as the subject.
• What changed: the outcome, in real terms.

Say you led a support team through a product launch. The filler version: "I have strong leadership and communication skills." The proof version: "When we launched the new checkout, ticket volume tripled overnight. I reorganized the queue by issue type, wrote five canned responses for the most common failures, and we cleared the backlog to a four-hour response time within the week." Same person, but only one of these is believable, because only one shows the work.

If you don't have a clean number, don't fabricate one - a precise-sounding fake is worse than an honest qualitative result. "Cut our response time to under a day, down from several" is fine. Inventing "improved efficiency by 47%" is not, and a sharp reader can usually smell it. If you're struggling to find the real metric buried in your own work, ResumeGet's Evidence Interview walks you through your projects to surface the honest numbers you can actually stand behind.

Give a real reason for this role

This is the paragraph that separates a letter written for the job from a letter blasted to fifty. Generic enthusiasm - "I'm excited by your mission" — reads as filler because it's true of every applicant and provable by none.

A real reason is specific enough that it couldn't be pasted into another application. It usually comes from one of a few places:

• Something the company actually does that intersects with your work: a product you've used, a technical choice they've written about, a market you know firsthand.
• A problem the role exists to solve that you've solved before and want to solve again.
• A genuine fit between where the team is going and what you're trying to build next.

One honest sentence beats a paragraph of praise. "I've been the frustrated customer of three tools in this category, and the way your onboarding handles the first-run problem is the thing I'd most want to work on" tells the reader you looked. "Your company is an industry leader and I'd be thrilled to contribute" tells them you didn't.

If you can't find a specific reason after looking, that's information. Sometimes it means you don't want the job. Sometimes it means a cover letter won't add anything here.

Close short, and cut the rest

End in one or two sentences. Don't summarize the letter you just wrote - the reader was there. A clean close states that you'd welcome the conversation and stops: "I'd be glad to walk through any of this in more detail. Thanks for your time." No "I look forward to hearing from you at your earliest convenience," no restating your phone number that's already in the header.

Then go back and cut. The most common filler to delete:

• Résumé in prose. If a sentence just narrates a line from your résumé, it's dead weight. The letter should add context the bullets can't, not echo them.
• Vague passion. "Passionate," "driven," "team player," "go-getter." These are claims with no evidence. Either show the trait through the story or drop the word.
• Clichés and throat-clears. "I am writing to," "I believe I would be a great fit," "as you can see from my résumé." All deletable with no loss.

Length is a discipline. Aim for half a page - roughly three short paragraphs, three hundred words or fewer. Plain formatting: your contact details, the date, a greeting to a real person if you can find the name, and tight blocks of text. No decorative header, no clever fonts. If you're submitting through a portal, paste it as clean text.

When a cover letter actually helps - and when to skip it

A cover letter is worth writing when it can carry information the résumé structurally can't:

• You're changing fields or roles, and the connection between your past and this job needs one sentence of translation.
• There's a gap, a relocation, or an unusual path that a hiring manager will wonder about - better to answer it briefly than let them guess.
• The posting names something specific you've done that's hard to convey in bullets.
• It's a smaller team or a role where a human clearly reads every application.

It helps less when the application is a high-volume funnel screened mostly by software, when the form makes the field optional and nothing about your case needs explaining, or when you'd be padding to fill space. A weak, generic letter can cost you; no letter where none was needed rarely does.

When you do write one, treat it the way you'd treat a strong résumé bullet: every line earns its place or it goes. If you want a draft to react to, ResumeGet can generate a cover letter from your résumé and a pasted job description - a starting point you then cut down to the half-page that's actually yours. The structure stays the same whether you start from a blank page or an edit: name the match, prove it once, give a real reason, and stop.