How to write a cover letter that proves motivation and skills

Choosing the experience that fits the cover letter question

After reading a cover letter, the reader should be left with the skill the question asks about and the experience where you used it. Connect what you learned about the company and the role to what you did, what changed, and what you learned.

Before you write any sentences, prepare in this order.

Write in one sentence the skill the question is trying to check
Find the related tasks and required skills in the job posting
Pick one or two experiences that show them
Write your role and actions in that experience as individual facts
Connect only the context you need to fit the character limit

If you try to produce finished sentences straight from a blank page, abstract phrases tend to multiply. Choosing the experience and evidence first makes the draft easier to write.

A first sentence that answers the question

Put the conclusion you want this answer to show in the first sentence, not background.

The examples below were written to explain the structure.

Before: I have been a curious child since I was young.
After: Analyzing inventory data myself to reduce repeated ordering errors taught me to verify causes with numbers.

From the second sentence on, describe the situation and actions that support that conclusion. If you can use subheadings, write a phrase that shows your key claim or a change instead of repeating My background.

Four elements of an experience to check with STAR

The STAR structure makes it easy to check the important facts when organizing an experience.

S (Situation): What was the situation?
T (Task): What task and responsibility did you have in it?
A (Action): What did you decide and do?
R (Result): What changed, and what did you confirm?

When the situation runs long, your own actions can get buried. Write only as much S and T as the reader needs to follow, and use A to show why you chose what you did and what you actually did. If you don’t have exact numbers, don’t invent them; write things that can be checked, such as the change before and after, feedback, the work you completed, or a method that was reused elsewhere.

The question each prompt needs you to answer

Motivation

If your motivation is only praise for the company, the reader can’t see how the company connects to your experience. These three things should appear together.

A problem the company or team is working on now
The specific reason you became interested in that problem
Related experience or preparation you already have

Instead of reasons you could attach to any company, like because it's the industry leader or because it has high growth potential, show what you actually observed in its products, customers, technology, or business direction and how it connects to your experience.

Job skills

Choose the experience closest to the main responsibilities and qualifications in the posting. Along with the name of a technology, write what problem you solved with that technology or skill.

Collaboration and conflict

There’s no need to make a conflict more dramatic than it was. Show what the differing views were, how you set criteria for agreement, and how your actions affected the shared result. If you only describe the other person as incompetent or uncooperative, it’s hard to see how you collaborated.

Failure and challenge

What matters more than the size of the failure is how you recognized it, the actions you changed afterward, and the result when you applied them again. If the results aren’t fully in yet, write only as far as you have confirmed.

Background, strengths, and weaknesses

Rather than writing a full chronology, choose experiences that connect to how you work now. For a weakness, write the real risk it creates and how you manage it, which lets you explain it more concretely than dressing it up as a strength.

Goals after joining

Rather than big ambitions far from the actual work, write step by step what you need to understand first and the direction in which you want to contribute. Don’t state schedules or results after joining without grounds; stay within the scope of the role you confirmed in the posting.

Examples connecting claims and actions by role

Even for the same question, like problem-solving skills, persuasive evidence differs by role. These are fictional examples, not real accepted sentences, showing which actions to attach after the claim in your first sentence.

Engineering

Opening claim: Rather than quickly covering up an outage, I first look for a cause I can reproduce.
Evidence to follow: how you narrowed down error logs and request conditions, the fix you chose and the alternatives you dropped, the metrics you checked after deploying

Product planning and PM

Opening claim: When opinions differ, I set scope by putting user problems and business constraints on the same criteria.
Evidence to follow: the data and customer voices you used, the priorities you agreed on with stakeholders, the release scope and the change you confirmed

Marketing and sales

Opening claim: I don't keep low-performing channels on instinct; I redesign them based on customer response.
Evidence to follow: the customer segments you defined, the message or offer you changed, the touchpoints you owned and the response before and after

Operations and customer support

Opening claim: I turn individual fixes into team standards so an inquiry solved once doesn't come back.
Evidence to follow: how you categorized recurring problems, the actions you took to change documents, procedures, and escalation, and the reuse or quality change

A sentence you could reuse by swapping only the job title often still lacks evidence. First find the judgments and actions you actually repeated in your role, then choose the case closest to the skills the posting asks for.

Focus when using one experience for several questions

Reusing the same experience isn’t always a problem. If one project can show different actions and skills, you can use it again.

For example, the same project can have different focuses like this.

Job skills question: how you analyzed the problem and chose a technical solution
Collaboration question: how you agreed on criteria with another team and resolved schedule conflicts

If every answer repeats the same event and conclusion, your range of experience looks narrow and the application tells the reader less that’s new. Before submitting, write one line per question with experience, skill to show, and key action to check for overlap.

What to add from your experience when you’re short on length

Follow the minimum and maximum character counts set in the posting. Rather than mechanically hitting a target ratio, first check whether you’ve answered the question fully.

If you’re short on length, add in this order.

The scope you were responsible for and its constraints
The method you chose and why you dropped the alternatives
The order of the actions you actually took
The criteria you used to confirm the result
What you would change if you did the same work again

Don’t repeat the same resolution in different words, and don’t add company names, numbers, or experience that aren’t on your résumé.

The role of AI: an editing tool rather than the author

AI can help you structure your experience or find alternative phrasing. The final answer should contain what you actually went through, in your own voice.

If you got an AI draft, check the following sentence by sentence.

Did it add facts that aren’t in your résumé or input?
Did it turn something the team did into something you did alone?
Are the numbers, dates, company names, and technology names accurate?
Are there abstract sentences left that would apply to any applicant?
Could you explain it the same way in an interview?

As you read the draft, first check that the evidence from your experience and the way you normally write are still there.

If the experience and numbers the draft is based on aren’t organized yet, start with how to write a résumé that gets read. The dates, role, and results of the same experience should match between your résumé and cover letter.

Frequently asked questions

How do I start the first sentence of a cover letter?

Write the answer to the question first, then follow with the experience that proves it. In a motivation answer you can lead with why you chose the company and role; in a skills question, with what you did. If you’re stuck on your reasons, see the four-sentence structure of a motivation statement.

How do I write a 500-character answer differently from a 1,000-character one?

Rather than adding a second key experience, change how deeply you explain the same one. In a short answer, keep the problem, your actions, and the result; if you have room, add the grounds for your decisions and how you verified them.

Checklist before submitting

Does the first sentence answer the question?
Is every claim backed by real experience and action?
Are the same experience and conclusion not repeated across questions?
Are there no sentences left that would still work if you swapped the company and role?
Do the project names, dates, role, and results match your résumé?
Are there no numbers or exaggerations that can’t be confirmed as fact?
Did you do a final check of everything from the company name and job title to the character count and spelling?
If it’s blind hiring, is there no prohibited personal information left?

Experience and facts to compare across the whole application

If you choose experience that fits the question and write your role and actions factually, it becomes clear what the reader can confirm in your cover letter. Write down what each question asks, use STAR to find what’s missing, then check whether experiences overlap across questions and whether the facts match your résumé.

How this was written and references

The order in this article isn’t a formula that works at every company. If the actual questions, character limits, blind hiring rules, or the company’s own guidance differ from this article, follow those conditions first.

Checking length and facts after drafting

If the question has a character limit, cut background first. Keep what explains your role, actions, and results.

If you made the draft with AI, follow five steps to compare your records with an AI cover letter to review your role, numbers, and job connection. Even if it reads naturally, fix it if it includes work you didn’t actually do.