What you will learn
An experience section should help a reviewer understand your contribution, not only the tasks a team was responsible for. Clear bullet points can connect paid work, projects, study, or volunteering to the work an employer needs done.
- Write action, task or method, and result-or-evidence bullet points.
- Use honest numbers when available and useful qualitative results otherwise.
- Rewrite three existing bullets without exaggerating context or ownership.
Move beyond a list of responsibilities
“Responsible for testing” names a duty but leaves the reader guessing what you actually checked. Explain an action you took, the work or method involved, and the deliverable, outcome, or evidence.
Start with your own contribution. If others did part of the work, distinguish that contribution rather than implying that you delivered the entire project alone. Keep the context visible: personal, academic, freelance, volunteer, open-source, or employed.
Build a bullet with action, method, and evidence
A useful structure is: action verb + task or method + result, deliverable, or evidence. It is a writing aid, not a rule that every sentence must contain a metric.
| Type of work | Possible verbs | What to clarify |
|---|---|---|
| Building or improving | Built, implemented, configured, revised | What changed and what you personally did. |
| Analysis or investigation | Analysed, compared, validated, investigated | The question, method, data, and conclusion or limitation. |
| Testing or reliability | Tested, reproduced, checked, documented | Which behaviour or failure case you checked. |
| Collaboration or coordination | Coordinated, explained, reviewed, organised | Your contribution, audience, and agreed output. |
Evidence-based bullet formula
[Action verb] [specific work] using [method or tools], producing [truthful deliverable, observed result, or evidence].
Compare weak and stronger examples
All examples below are illustrative. They describe possible work, not achievements you should copy without having done it.
| Area | Weak | More specific |
|---|---|---|
| Software development | Worked on a website. | Built a responsive event registration page with React, added form validation, and documented keyboard testing. |
| Data analysis | Used Excel and SQL. | Cleaned a practice dataset with SQL, checked duplicate records, and documented assumptions in a reporting summary. |
| Software testing | Responsible for testing. | Created test cases for a study application’s registration flow, reproduced invalid-input issues, and documented the observed behaviour. |
Worked example: improve one bullet in stages
Suppose your draft says “helped with an app.” Before polishing the wording, identify the work that actually happened.
- Name the context: a personal study application, not paid employment.
- Identify your action: implemented a task-entry form.
- Describe the method: JavaScript input checks and error messages.
- Name evidence: a working feature, documented test cases, or a demonstrated behaviour.
- Write the bullet and compare every claim with your code or notes.
Use measurable achievements responsibly
A numerical claim can be useful when you have a trustworthy baseline, a clear measurement method, and a relevant comparison. Record how you calculated it and whether the context was a small test, a simulation, or real operations.
Do not invent percentages because a template says every bullet needs one. A clear deliverable, a resolved issue, a documented process, or a capability demonstrated in a work sample can also be meaningful.
Keep confidential employer information out of public CVs. Use an appropriate non-sensitive description rather than exposing private records to make a point.
Represent different experience contexts honestly
Personal and academic projects show practice; freelance work has its own client and scope context; volunteering can demonstrate organisation or delivery; open-source work can show a specific contribution. Use the accurate label and dates for each.
- Describe a completed contribution rather than claiming authorship of an entire open-source repository.
- For a group assignment, state your feature or responsibility and how you worked with the team.
- For coursework, distinguish a guided exercise from an independently designed project.
- For freelance work, describe the agreed deliverable without revealing client-confidential details.
Practical activity: rewrite three bullet points
Choose three existing lines from your CV, or draft three from a genuine activity. A good revision makes a claim clearer, not larger.
- Record what happened, your role, the tools or method, and the output.
- Replace vague openings with an action that matches your contribution.
- Add evidence or a verifiable result, using numbers only if you can explain them.
- Check that dates, context, ownership, and learning stage remain accurate.
- Ask someone whether they can understand what you did and choose one final revision.
Further reading and local conventions
These resources provide additional guidance, not endorsements of these examples. Harvard and Yale address U.S. audiences; the National Careers Service addresses UK conventions. Use the employer’s instructions and relevant local guidance when applying elsewhere. No format or wording guarantees an interview.