Skip to content

CV writing

How to write a CV that shows what you can do

Turn responsibilities into evidence, explain your contribution, and improve your CV without inventing results.

You’ve done useful work. You’ve handled difficult requests, built reports, helped a team finish a project, or taken responsibility when something went wrong. Then you open your CV, and somehow all of that becomes “excellent communicator,” “team player,” and “responsible for reporting.” The work is there. The reader just can’t see much of it.

Rewriting those phrases with more impressive verbs can make the page sound better without making it more informative. “Spearheaded weekly reporting” still leaves the same questions: what did you produce, how did you do it, and why did anyone need it?

Our CV screener is built around checks such as relevance, evidence, clarity, and readability. This guide explains how to apply those lessons yourself. We’ll start with the job you want, break down a CV sentence, and show how to describe results honestly, including when you don’t have a dramatic number. You should finish with a way to edit your own work, rather than a list of phrases to copy.

Start with the work the employer needs done

Before editing, read the target posting and identify its main tasks. Then look through your own experience for examples that would help someone assess whether you could do them. Relevance gives you a reason to choose one achievement over another.

For a reporting job, a dashboard used in team meetings may deserve more space than organizing an unrelated event. For a coordination job, the event might be useful if it shows how you handled schedules, requests, or competing priorities. The experience hasn’t changed. Its relevance to the target job has.

This doesn’t mean rewriting your history for every application. Keep a factual record of your projects and achievements, then choose and order the most relevant ones. A reader should be able to see the connection between what you’ve done and the work you’re asking to do next.

Collect the facts before writing the bullet

For each example, note the situation, your actions, the tools or methods used, who used the work, and what happened. Rough notes are fine. The point is to recover details that disappear when you start with a polished sentence.

“Weekly reporting” might become: three source spreadsheets, inconsistent request categories, an Excel dashboard, a weekly meeting, and overdue requests reviewed by the support team. Those details give you choices about what to emphasize. They don’t automatically establish that you saved time or improved performance.

Separate what you know from what you think probably happened. If colleagues used the dashboard but you never measured a saving, describe its use. If the team achieved a result, record which part you handled. This is especially useful before asking an AI tool to rewrite anything: give it facts and boundaries, then check that the output stays within them.

What a useful CV sentence contains

Built a weekly reportAction

The work you personally completed.

from three source sheets,Method

The detail that explains how you did it.

used in support meetings.Use

What the work was for, without inventing a saving.

This illustrates sentence structure. Use only the parts that accurately describe your own work. A business outcome can replace the use when you have evidence for it.

Distinguish the size of the work from its result

A budget, team size, or customer count can show the scale of a task. It doesn’t explain what you achieved. “Managed a team of four” tells us about responsibility. “Led four colleagues through a product launch” adds a deliverable. A further result needs its own evidence.

Use numbers when they clarify something real. Combining three input sheets is a verifiable description of the work. A 20% improvement needs a definition of the measure, a comparison period, and a basis for connecting the change to what you did. If you can’t explain those things, don’t add the figure because a CV formula seems to demand one.

There are other useful results: a guide adopted by a team, a report used to make a decision, a test completed, or an error found and corrected. They tell the reader what came out of the work without requiring an invented financial impact.

Scale and achievement tell the reader different things

Scope: how big the task was

Team size, budget, customer count, or number of projects.

Result: what came out of the work

A decision informed, a guide adopted, an error fixed, or a measured change.

ScopeYour contributionResult or use

A large number gives context. It becomes an achievement claim only when the reader can understand what changed or what was delivered.

Show skills through examples

A skill list can help someone locate relevant tools. It becomes more convincing when the experience section shows how you used them. “Excel” beside a specific reporting example gives the reader more information than a self-rating such as “advanced.”

The same applies to communication and teamwork. Interviewing colleagues, resolving conflicting requirements, explaining findings, or coordinating a handover can demonstrate those skills. Describe the action and its purpose, rather than asking the reader to accept the label.

Early in your career, the example may come from a course, society, volunteering, or a personal project. Label the setting accurately. Explain what you personally completed and how it was used or evaluated. A university project doesn’t need to masquerade as commercial experience to be relevant.

Keep each claim easy to understand and defend

Give each bullet one main point. Start with your contribution, add the detail needed to understand it, and finish with the result or use when you have one. Read it aloud. If it needs three explanations before it makes sense, simplify it.

Explain internal abbreviations and replace vague business language with the actual work. “Supported cross-functional alignment” could describe collecting updates, agreeing deadlines, or resolving a disagreement. Name whichever happened. Harvard’s resume guidance similarly recommends specific, active, factual language that’s easy to skim.

Keep achievements beside the job or project where they happened. If several people contributed, make your part clear. Don’t disclose confidential information to strengthen a bullet. Use an accurate description you’re permitted to share, and be ready to explain it within those limits in an interview.

Check the document as well as the wording

Use recognizable section headings and consistent dates. Make the text comfortably readable before trying to fit in every detail. A line that’s relevant and clear is worth more space than several vague claims.

Open the exact file you’ll submit, then copy its text into a plain-text editor. Check whether the headings, dates, and descriptions remain in a sensible order. A page can look tidy while producing scrambled copied text. This is a useful diagnostic, not a guarantee of how every applicant tracking system will process the file.

Follow the employer’s requested file format. Avoid blanket rules that a particular design always passes or fails. Your job here is to produce an accurate, readable document and check the version that actually leaves your computer.

Check the reading order in the file you will send

CV documentExperience
Job title · Dates
Relevant work and results
Education
Qualification · Dates

Copy the text

Plain-text view
  1. Experience
  2. Job title and dates
  3. Work and results
  4. Education
  5. Qualification and dates

The order should remain understandable when the text is copied. This can reveal a problem, but cannot guarantee how every application system will read a file.

Use review feedback to make a specific improvement

A useful review should leave you knowing what to change and why. Choose one finding: an unclear contribution, a weak example, a confusing date, or an unsupported claim. Fix it, then check whether someone outside your workplace could understand the result.

If an AI suggestion adds a figure, tool, responsibility, or outcome that wasn’t in your facts, remove it. A fluent sentence isn’t evidence. You remain responsible for the claim, and you may need to discuss it in an interview.

Finally, use a score as a way to organize feedback, rather than as a prediction of an interview. Once an edit makes your work clearer, continue to the next meaningful issue. The document is ready when it makes a credible case for the job and you can support what it says, even if there are still other ways to phrase a line.

Sources & further reading

Based on our CV screener’s checks for relevant experience, clear examples, writing, layout, and readable files.

Reviewed October 18, 2026. Check the source for current guidance.

Open My CV Browse all stories