The work-experience section carries most of the evidence in a resume. Strong entries make it easy to see what you owned, how you worked, and what changed because of your contribution.
Set a consistent structure
For each position, show the employer, role, location when useful, and dates in a consistent format. List roles in reverse chronological order unless a different structure clearly serves your situation.
Give more space to recent and relevant work. Older positions can be shortened when they add context but do not support the target role directly.
Build bullets around actions and context
Begin with a precise action, then explain the object and context. Add an outcome only when it is accurate and meaningful. Not every responsibility produces a numerical result, and an honest operational detail is better than a fabricated percentage.
Replace phrases such as responsible for or helped with when you can describe the actual contribution. Coordinated, analyzed, designed, resolved, prepared, trained, and implemented each give the reader a clearer starting point.
- Action: what you personally did
- Context: team, customer, system, volume, or constraint
- Outcome: improvement, delivery, quality, time, revenue, cost, or risk when known
Edit for relevance and credibility
Choose bullets that answer the target employer's likely questions. A role requiring stakeholder coordination should see examples of communication across groups; a technical role should see systems, decisions, and delivery detail.
Check verb tense, remove repeated openings, define uncommon abbreviations, and keep each bullet focused on one main idea.
Draft an evidence note before writing the bullet
Choose one responsibility from a real role and answer four questions in your own notes: What needed doing? What did you personally do? What did you produce or hand over? What can you verify about the result? For example, an administrator might have checked incomplete delivery records, contacted the relevant store, updated a shared sheet, and prepared a list of unresolved orders for a supervisor. Those details are enough to explain useful work without inventing a dramatic business result.
Keep a private record of where each claim came from, such as your own project notes or an approved performance review. You do not need to attach internal documents to an application. Remove confidential customer names, unreleased product details, and figures you are not allowed to share. If you cannot verify a number, explain the task and output without it.
Worked example: a complete experience entry
The following employer and entry are fictional teaching examples, not details to copy into your own history.
Operations Assistant — Cedar Lane Supplies
May 2024–September 2026
- Checked delivery references against store order records in Excel and followed up on missing entries before the weekly stock review.
- Prepared a shared handover list showing unresolved orders, the person handling each query, and the next action for the store team.
- Updated the new-starter checklist after reviewing recurring setup questions with the office supervisor.
The bullets show record checking, coordination, and documentation as separate contributions. They do not claim that the assistant owned the whole supply chain or caused a company-wide improvement. For a coordinator vacancy, lead with the handover example. For a reporting vacancy, put the Excel work first. Keep the employer, title, dates, and underlying facts consistent across versions.
Rewrite a weak bullet without inflating your role
Before, fictional example: “Helped with a website project.” After: “Tested the new appointment form on mobile browsers, recorded reproduction steps for validation errors, and retested the fixes before release.” This names a contribution, method, and delivery checkpoint. “Led a website launch” would change the meaning if someone else owned the project.
A measured result can strengthen a bullet when the comparison is fair. Record the measurement period, baseline, and your contribution in your notes before including a figure. Distinguish the team's outcome from your own action. If the result is still being evaluated, describe what you delivered and how it is being assessed rather than presenting a target as an achieved improvement.
Handle promotions, short assignments, and limited experience
For a promotion, keep each title with its own dates so the change in responsibility is visible. Group the roles under one employer if the layout keeps those dates clear; otherwise, separate entries are fine. For contract or freelance work, label the arrangement accurately and describe selected assignments you can discuss publicly. Do not present a client as a direct employer if that would misrepresent the relationship.
If paid experience is limited, relevant volunteering, supervised placements, and projects can provide evidence. Label each setting plainly. A course project belongs under a project or education heading, or an appropriately named experience section, rather than being recast as employment. Our student resume guide shows how to build that first document.
Check the entry in the finished document
Read each bullet beside the job title. Is the scope believable? Can you explain your action in an interview? Does a present-tense verb describe ongoing work, and a past-tense verb completed work? Remove repeated sentences that appear under several roles. Open the exported PDF and check that a page break has not separated a job heading from all of its supporting bullets.
Compare the project manager example or software engineer example, then enter your own history in the work experience step of the free builder. Use only activities and outcomes you can support.
Further reading
CareerOneStop's work experience guidance discusses relevant responsibilities and context. Harvard's resume guide recommends specific, fact-based language. The worked examples above are our own illustrations.
Final review
Read the section from the employer's perspective: it should explain your scope and contribution without requiring the reader to infer what you actually did.
Illustrative Examples
Before
Responsible for customer support and solving customer issues.
After
Resolved billing and account questions across email and live chat, documented recurring issues, and shared patterns with the product team.