How to Write a Cover Letter for a Developer Job

The short answer

A good developer cover letter is a short text written for one specific vacancy, not a retelling of your resume. It answers three questions: why this company, how your experience helps with their tasks, and what you suggest as the next step (a call, a test task, a link to your code).

Length: 5-8 sentences. A recruiter scans it in seconds, so the key point belongs in the first two lines.

When a cover letter really matters

You do not always need one, but in some situations it noticeably improves your chances:

• You are a junior or switching careers — little commercial experience, so the letter explains motivation and points to projects.
• You do not match 100% of the requirements — you can honestly show what you cover and what you can pick up quickly.
• Small company or startup — letters are often read by the team lead or founder.
• The vacancy explicitly asks you to tell about yourself or answer a question. Ignoring that is an almost certain rejection.
• Relocation, remote work, a stack change — the letter answers questions before they are asked.

Even if you are experienced and your resume fits perfectly, 2-3 sentences beat an empty field.

A structure tailored to the vacancy

1. Hook (1 sentence). Which position and what specifically caught your attention: the product, a task from the vacancy, the team's tech blog.
2. Relevant experience (2-3 sentences). One or two facts directly tied to the requirements. Not a list of technologies, but what you built with them.
3. Link to their stack and tasks (1-2 sentences). How your experience is useful to them in particular.
4. Next step (1 sentence). A link to GitHub or a portfolio, availability for a call or a test task.

How to connect your experience to the company's stack

Before writing, pull 3-4 key requirements from the vacancy. For each one, find evidence in your own work:

Put the two strongest matches into the letter. Phrase them as action and outcome: not "I know PostgreSQL", but "designed the schema and sped up slow queries with indexes".

Example for a junior

Hello! I am applying for the Junior Frontend Developer position: your product for small businesses resonates with me, as I helped a friend's shop organize its orders.

Over the past year I built two projects with React and TypeScript: a dashboard with filtering and charts, and an online store with a cart and test-mode payments. In both I worked with REST APIs and wrote tests for key components.

The vacancy mentions a migration to TypeScript, which is exactly where I have the most practice. Code and demos: github.com/username. I would be glad to have a call or do a test task.

Example for an experienced candidate

Good afternoon! I am interested in the Senior Backend Developer role on the payments team.

For the last several years I have owned the backend of a high-load service in Go and PostgreSQL: I extracted a monolithic billing module into a separate service, set up idempotent payment processing and monitoring.

I see you are building bank integrations and scaling the system. I have worked on similar problems and can get up to speed quickly. Happy to discuss details on a call.

Common mistakes

• A generic template. "I am responsible, communicative and a fast learner" gets skipped. If a letter fits any vacancy, it fits none.
• Retelling the resume. The letter should add context, not duplicate your job history.
• Wrong company or position name. A frequent copy-paste error and an instant minus.
• Too long. More than one screen means you have not picked the main point.
• Apologizing for lack of experience. Instead of "I do not have much experience, but…", show what you have already built.
• No links. For a developer, code and demos are the strongest argument.
• Typos. Reread the text or run a spell checker.