Most cover letters are never really read. Not because hiring managers are rude, but because most letters give them nothing to read: the same generic opener, the same list of adjectives, the same paragraph that could have been sent to any company for any role. A letter like that takes thirty seconds to skim and zero seconds to remember.
The fix is smaller than people think. A cover letter that gets read is short, specific, and obviously written for this posting. Four short paragraphs, each doing one job. This guide walks through the structure, shows you a full annotated example, and covers the judgment calls: when to skip the letter entirely, how to open without sounding like everyone else, and how to stay honest while tailoring hard.
What a cover letter is actually for
A cover letter is a short, one-page note that connects your experience to one specific job posting. It is not a second resume. The resume lists what you have done; the letter explains why any of it matters for this role, at this company, right now. If your letter could be attached to a different application without changing a word, it isn't doing its job.
That definition also tells you what to optimize for. Recruiters skim letters in seconds, so every paragraph has to earn the next one. Specificity is the whole game: a named result, a real detail about the company, language lifted from the posting itself.
Do you even need one?
Sometimes the best cover letter is no cover letter. Write one when the posting asks for it, when you're making a career change that needs explaining, when a referral or a direct contact is involved, or when the role itself rewards writing. Skip it when the application has no field for one and says nothing about it: forcing a letter into a process that didn't ask reads as not reading the instructions. When you skip it, put the energy into the resume instead. Tailoring your résumé to the posting in minutes beats a generic letter every time.
The four moves
Every cover letter that works follows the same skeleton. Four short paragraphs, four jobs, in this order:
1. Name the fit
Say which role you're applying for and give one sharp reason you fit, ideally a result. This is the paragraph that decides whether the rest gets read, so lead with something only you could say.
2. Prove it once
One concrete story with a number in it, mapped to the posting's top requirement. Two or three sentences. This paragraph does the actual persuading, so give it the most room.
3. Mirror their priorities
Show you understand what this company cares about right now: a product launch, a shift in strategy, a problem the role exists to solve. One genuine detail beats a paragraph of flattery.
4. Close clean
Restate the fit in one line and invite the next step. Warm, confident, short. Then stop.
Keep the whole thing to one page, roughly 150 to 250 words. If you're deciding what to cut, cut from paragraphs one and four first. The proof paragraph is the last thing to shrink.
An annotated example
Here is what the four moves look like in a real letter, about 170 words. The applicant is fictional; the technique isn't.
Dear Ms. Chen,
Your posting for Customer Success Manager says the first 90 days are about cutting onboarding time for mid-market accounts. At Brightline, I owned onboarding for 40 accounts and cut average time-to-value from 21 days to 9, mostly by replacing a five-call sequence with two working sessions and a shared checklist.
What draws me to Loopwork specifically is the usage-based pricing launch. Onboarding gets harder exactly when pricing gets more flexible, because every customer's “value moment” looks different. I spent last year building segment-specific onboarding tracks for three plan tiers, and renewal rates on the new tracks ran 12 points higher.
I would welcome the chance to talk through what a 90-day onboarding plan could look like for your mid-market segment.
Best regards,
Amara O.
Why it works, paragraph by paragraph:
- The opener names the posting's priority. “Cutting onboarding time for mid-market accounts” is presumably straight from the listing. The reader sees their own words reflected back in the first line.
- The proof is one story with two numbers. 21 days to 9, across 40 accounts. No adjectives about being “results-driven.” The result does that work.
- The company detail is specific and current. The usage-based pricing launch is something you could only know from research. It connects the applicant's past to the company's future, which is the entire point of paragraph three.
- The close proposes a next step. Not “thank you for your time and consideration,” which closes on an apology. A short conversation about a 90-day plan.
Notice what the letter doesn't do: it never says “I am writing to apply,” it doesn't restate the resume line by line, and every claim in it is the kind you could defend out loud in an interview. That last part matters more than people think. There is a real craft to writing bullets that are strong without inflating anything, and the same discipline applies here.
Opening lines that aren't generic
Your first line has one job: proving this letter was written for this job. Compare:
- Instead of “I am writing to apply for the Customer Success Manager position,” try “Your posting says the first 90 days are about cutting onboarding time. That is the work I do.”
- Instead of “As a results-driven professional with five years of experience,” try “I cut onboarding time from 21 days to 9 at my current company. I want to do it here.”
- Instead of “I have always admired your company,” try “Your shift to usage-based pricing changes what onboarding has to do. I have managed exactly that transition.”
The pattern: quote or paraphrase the posting, then attach yourself to it with a fact. Anything you could paste into a letter for a different company is a placeholder, not an opener.
Mirror the posting's language, honestly
Hiring managers, and their software, notice when your letter speaks the posting's language. If the listing says “onboarding,” “time-to-value,” and “mid-market,” those exact terms belong in your letter, attached to things you actually did.
The honest version of this has a hard boundary: mirror only what is true. Borrowing a keyword for a skill you don't have might survive a parser, but it collapses the moment someone asks about it. The discipline is the same one behind keyword matching without stuffing: echo the vocabulary, never invent the experience.
A practical way to do it: pull three to five concrete terms from the posting's requirements section, and check each one against your history before it goes in the letter. Terms you can't honestly claim stay out, and the letter gets stronger for their absence, because everything left in it is defensible.
Match the company's tone
Read the posting's voice and meet it. A bank's posting and a startup's posting are not asking for the same letter, and sending the same tone to both signals you didn't read either.
- Formal (finance, law, enterprise): complete sentences, no slang, “Dear Ms. Chen” over “Hi there.”
- Plain (tech, startups): short sentences, direct language, first names are fine.
- Warm (nonprofits, education, healthcare): let genuine motivation show, but keep the proof just as concrete.
Matching tone is not faking personality. It is the written version of dressing appropriately for the interview.
What to cut
Most first drafts are twice as long as they should be. Cut ruthlessly:
- The sentence “I am writing to apply for...” (the subject line or salutation already says this)
- Anything your resume already says, restated in sentences
- Adjectives about yourself with no evidence attached
- Praise for the company that would be true of any company
- Apologies and hedging (“Sorry to bother you,” “I know you're busy”)
- A second page. If it doesn't fit on one, it isn't tight enough yet.
The honesty test
Before you send anything, read the letter once more and interrogate every claim: could I defend this out loud, in an interview, with a follow-up question? If a sentence makes you nervous, it doesn't belong in the letter, no matter how good it sounds on the page.
This is the same standard worth applying to the resume behind the letter. A match score that collapses under one interview question was never worth chasing, and a cover letter claim you can't back up is worse than no claim at all. If you're missing a requirement the posting cares about, handle the gap honestly: leave it out of the letter and let your real strengths carry it.
Confirm before you claim. A line you can't defend out loud isn't worth sending.
Format it like it matters
Keep the mechanics boring so the content can be interesting: your name and contact details at the top, the date, the hiring manager's name if you can find it (“Dear Hiring Manager” if you can't), then the four paragraphs, then a simple sign-off. One column, standard fonts, no graphics. Export as PDF so it opens the same everywhere; use DOCX only if the application form specifically asks for an editable file. If you need a clean starting layout, Tailr's ATS-ready templates are single-column and parser-safe.
Cover letter questions, answered
How long should a cover letter be?
One page. Our recommendation: 150 to 250 words. Four short paragraphs beat a full page of filler. Recruiters skim, and a tight letter reads as more confident than a long one.
Should I write a different cover letter for every job?
Yes, at least the opening and proof paragraphs. The four-move structure stays the same every time; the specifics change with the posting. A letter you don't customize is a letter you didn't need to write.
Can I use AI to write my cover letter?
You can use it to draft, but never to invent. Every claim in the letter has to be true and interview-ready, so review each line before you send it. Tailr's cover letter generator is built around this rule: it writes only from experience you genuinely have, and never manufactures a match.
Do cover letters matter if the company uses an ATS?
In most pipelines, the resume is what gets parsed for keywords; the letter is what a human reads when they open your file. A short, specific letter written in the posting's language survives both, which is one more reason to keep it honest and tailored.
What if I don't have much experience?
Lead with adjacent proof: projects, coursework, freelance work, volunteering. Pick the one story that maps most closely to what the posting asks for, and be straightforward about where you are. A short, honest letter from a junior candidate beats a padded one every time.
The bottom line
A cover letter that gets read isn't a writing achievement. It's a research achievement with four paragraphs attached: read the posting for what it actually wants, answer with one true story, show you know the company, and close like you mean it. Do that honestly and the letter stops being a formality. It becomes the reason they open your resume.