Cover Letter Examples for Job Applications

Most advice tells you to sound passionate and stops there, which leaves you staring at a blank page. This section gives you the four blocks a hiring manager reads, in the order they read them. Each block is one short paragraph.

• The hook: the exact job title, where you found the posting, and one sentence on why this employer rather than a similar one.
• The proof: one project from your resume with its outcome attached, expanded past what the bullet had room for.
• The fit: two or three sentences tying that project to the requirements in the posting.
• The close: what you want next, stated plainly, plus your availability.

Four blocks fit on half a page. If yours fills a full page, the proof block has usually turned into a list of everything you have ever done.

The blocks stay the same; what changes is which one carries the weight.

Career changer. A warehouse operations lead applying for a supply chain analyst role names the posting in line one, then spends the proof block on the inventory forecasting spreadsheet she built and the stockouts it removed, not on the forklift certification. Her fit block does the real work: it translates warehouse vocabulary into analyst vocabulary so the reader does not have to.

Entry level. With no job history to mine, the proof block comes from a class project, an internship, or volunteer work, and it still needs an outcome. Rebuilt the club signup form and registrations doubled the following term reads as evidence. Passionate about data does not.

Experienced hire. Here the risk is length. Pick the one project closest to the posting and drop the other eleven, because the resume already lists them. The close can be more direct at this level, naming the scope or team size you are looking for.

If the resume those stories come from still needs work, the free builder at /resume-builder is a reasonable place to start.

Tailoring is not rewriting. Keep the proof block stable across applications in the same function and rewrite only the hook and the fit block. That is twenty minutes per application, not an evening.

Read the posting twice and mark every requirement that appears in both the requirements list and the responsibilities list. Repetition signals what the team is actually short of, and those are the points your fit block should answer by name, using the posting's own words. If the posting says incident response, write incident response rather than handling urgent issues.

One caution: matching vocabulary is not the same as matching experience. Never describe work you have not done to hit a keyword, because the claim comes back as a question in the interview. Rehearsing that conversation out loud is what the practice tool at /mock-interview is for.

A cover letter is a supporting document and it behaves like one. Applicant tracking systems generally keep it as an attachment and rank candidates on parsed resume fields, so in many pipelines nobody opens the letter until a human is already shortlisting. Writing a longer one does not move you up that list.

It also cannot repair a mismatch. If a posting requires a licence, a specific work authorisation, or years in a stack you have never touched, no framing paragraph closes that gap, and a letter that tries usually reads as an apology. Spend the effort on roles where you are missing one requirement, not four.

Formatting, length, and what recruiters scan first are covered across the resume pages at /answers/topic/resume.