# How to write a cover letter that gets read

> When you need a cover letter, how to write one that actually helps your application.

By Aleksandr Kondaurov · Jun 22, 2026 · 2 min read
Tags: career
Series: Job-search guide · Part 4
URL: https://kondaurov.dev/blog/cover-letter/

## Do you even need one?

Short answer: it depends.

- **Required field in the application form** — yes, write one
- **"Optional" but the company is small** — yes, it shows genuine interest
- **Mass application to a large company via ATS** — probably won't be read, but a short one won't hurt
- **Referral or direct email** — absolutely yes, this is your introduction

When in doubt, a short, targeted cover letter is better than none.

## What a cover letter should do

A cover letter has one job: **make the recruiter want to read your resume.**

It should answer three questions:

1. Why this role?
2. Why you?
3. Why this company?

That's it. Not your life story. Not a restatement of your resume. Three clear answers in 200-300 words.

## Structure that works

### Opening (2-3 sentences)

State the role you're applying for and your strongest connection to it. Skip "I'm writing to express my interest in..." — everyone writes that.

**Weak:** "I am writing to apply for the Senior Developer position at Acme Corp. I believe my skills make me a strong candidate."

**Strong:** "Your Senior Developer role caught my attention because of the migration from monolith to microservices — I led exactly that transition at my current company, taking deployment time from 45 minutes to under 5."

### Middle (2-3 short paragraphs)

Connect your experience to what they need. Pick 2-3 specific things from the job description and show how your background matches.

Don't repeat your resume bullet-for-bullet. Instead, **tell the story behind the bullets:**

- What was the problem?
- What did you do?
- What was the result?
- Why does this matter for the role you're applying to?

### Closing (2-3 sentences)

Express genuine interest and make it easy to follow up. No groveling, no "I would be honored." Keep it professional and direct.

**Example:** "I'd enjoy discussing how my experience with distributed systems could help your team scale the platform. I'm available for a conversation anytime this week."

## Common mistakes

**Too long.** If it's more than one page, it won't be read. Aim for 200-300 words. Recruiters are scanning, not reading novels.

**Too generic.** "I'm a passionate developer seeking new challenges" could be sent to any company. Mention the company by name, reference something specific about the role or product.

**Repeating the resume.** The cover letter adds context your resume can't: motivation, cultural fit, the story behind your career moves. Don't waste it on information they can already see.

**Overly formal.** "Dear Sir or Madam, I hereby submit my application..." — this isn't 1995. Write like a professional human being, not a legal document.

**Apologizing.** "Although I don't have experience in X..." — don't highlight gaps. Focus on what you bring, not what you lack.

## A quick template

```
Hi [hiring manager / team],

[1-2 sentences: why this role specifically interests you — reference something
concrete from the job posting or the company]

[1 paragraph: your most relevant experience and how it maps to what they need.
Be specific — name technologies, outcomes, scale]

[1 paragraph: what else you bring — domain knowledge, team skills,
or a unique perspective that adds value beyond the job description]

[1-2 sentences: express interest, suggest next step]

[Your name]
```