Cover letters: are they needed and what to write

Does anyone read them

Sometimes yes, sometimes no — it depends who's processing the applications.

But something else matters more: where they are read, the letter decides a lot. Beginners' CVs resemble one another, and the letter is almost the only place you can differ.

The conclusion is simple: write one, but keep it short. Three minutes per application is an acceptable price.

When it's definitely needed

• You don't match on paper but want to explain why it's still worth talking.
• You're changing profession. Without explanation your path looks odd.
• This particular company interests you and you have something substantive to say.
• The vacancy is a one-off, not a pipeline.

When you can skip it: mass applications to standard postings where only the CV will be read.

A five-sentence template

1. What you're applying for and who you are. "Hello. I'm applying for the junior developer role. I've spent the past year learning Python, I build projects, and I'm looking for my first job."

2. Why this company. Specifics are mandatory. "I see you build software for freight — I worked five years in logistics and understand the field from the inside."

3. What you have that's relevant. One or two facts, the strongest. "I built an expense tracker with one other person; I was responsible for the data layer and we took it to a working state."

4. Honesty about the gap, if there is one. "I have no commercial experience, but I've used these technologies on a project — the code is linked below."

5. A short close. "I'd be glad to talk. CV attached."

That's it. Six to eight lines.

What a bad letter looks like

Hello. I was very interested in your vacancy. I'm responsible, a fast learner, stress-resistant, and able to work both in a team and independently. I want to grow at your dynamic company and be of use. I'm ready for any task. Please consider my application.

There isn't a single fact here. This letter fits every vacancy in the country, and the reader can see that.

What a working one looks like

Hello. I'm applying for the junior Python developer role.

I've been learning Python for the past eighteen months and I'm now looking for my first job. I see you build warehouse systems — before moving into development I spent four years in warehouse logistics and know the field from that side.

Most recently: I built an inventory tracker with one other person, with reports and file export; I was responsible for the database work. Code and a running version are linked from my CV.

I have no commercial experience. I'm happy to start with small tasks.

I'd be glad to talk.

There are specifics here, an explained fit with the field, a real project named, and honesty about the gap.

On being honest about experience

Many people fear admitting they have none and skirt around it. Don't: it's visible from the CV anyway.

A plain "I have no commercial experience, here's what I have instead" makes a better impression than an attempt to disguise it. Being able to describe your situation honestly is itself a professional quality.

What not to do

Don't restate the CV. It's attached.

Don't write an essay. Nobody reads past ten lines.

Don't send one letter to everyone. The absence of specifics is instantly visible, and that's worse than no letter.

Don't flatter the company. "I've long admired your product" without detail rings false.

Don't apologise. "Sorry to trouble you" sets the wrong tone: you're offering your work, not asking a favour.