Work Experience on CV: Examples and Writing Guide

The easiest way to make job history feel relevant is to decide what the next employer needs to believe. Before you edit the section, open the advert, job description, or person specification and mark the responsibilities that keep appearing.

Look for repeated themes such as customer handling, stakeholder management, stock control, analysis, coding, safeguarding, sales targets, shift leadership, project delivery, complaints, reporting, budget ownership, compliance, or patient care. These are your selection filters.

Then ask one question for each past role: what can this job prove for the next one?

A supermarket role might prove customer service, cash handling, stock accuracy, and working under pressure. A university society role might prove planning, communication, budgeting, or event coordination. A short placement might prove that you understand a sector and can apply technical knowledge in a workplace.

Do not describe every role as if every detail has equal value. A CV is a selected argument, not a complete record.

Before writing polished bullets, make a rough evidence list for each role. Include responsibilities, systems, processes, teams, customers, projects, targets, achievements, compliments, improvements, problems solved, volumes handled, and any measurable results.

This rough list can be messy. Its purpose is to stop you writing from memory and falling back on vague lines such as "responsible for admin duties" or "worked as part of a team".

Use prompts like:

• What did I own without being chased?
• What did I improve, fix, deliver, prevent, organise, sell, build, support, analyse, reduce, or speed up?
• Who depended on my work?
• What tools, systems, regulations, or processes did I use?
• What would have gone wrong if I had done this badly?
• What feedback, targets, ratings, reviews, or outcomes can I mention honestly?

Once you have the list, choose the details that match the job you are applying for. Leave the rest out or keep it for a different version of your CV.

Not every entry needs the same depth. A recent job that matches the target role might need five or six bullets. An older job from a different sector might need one or two lines. A temporary job might sit under "Additional experience" if it adds reliability but not much direct evidence.

Use this simple order of importance:

1. Recent and directly relevant roles.
2. Recent roles with transferable evidence.
3. Older roles that explain progression or specialist background.
4. Short-term, early, or unrelated roles that only need brief context.

This stops the section becoming top-heavy with the wrong information. If the job you did five years ago is more relevant than your current role, you can still give it meaningful space, but explain the current role clearly enough that your timeline makes sense.

"Work experience" is the safest heading for most candidates. It is broad enough to include paid work, volunteering, internships, placements, and freelance projects.

"Employment history" can work if all entries are paid jobs. "Professional experience" suits experienced candidates or career changers who want a more polished heading. "Relevant experience" is useful when you have several unrelated jobs but want to foreground the most useful examples.

Role-specific headings can also help. For example, a trainee teacher might use "Teaching and classroom experience", while a software applicant might use "Development projects and work experience". Just make sure the heading is still obvious to a recruiter or applicant tracking system.

Most UK CVs use reverse chronological order. That means your newest role appears first, followed by earlier roles. Recruiters expect this because it makes your current level and recent responsibilities easy to scan.

A standard entry normally includes:

• Job title
• Employer or organisation
• Location if helpful
• Dates of employment
• A short role context line where needed
• Bullet points showing responsibilities, achievements, scope, and outcomes

For example:

Customer Service Adviser | Northside Utilities | Manchester | March 2023 to present

• Resolve 40-60 customer queries per day across billing, account changes, payment plans, and complaints.
• Reduced repeat contact by creating clearer follow-up templates for common meter reading and payment issues.
• Support new starters with call handling guidance, CRM notes, and complaint escalation process reminders.

This format works because the reader can see the role, setting, scope, and impact within seconds.

Use month and year for recent or substantial roles, such as "June 2022 to May 2025". If you have a long career and older roles, year-only dates can be acceptable once the detail is summarised, but be consistent.

Avoid vague date tricks. "2023-2024" might hide a role that lasted two months, and it may raise questions later. If a short contract was short by design, say so:

Events Assistant | City Arts Festival | Fixed-term contract | May 2024 to July 2024

That wording removes suspicion and gives useful context.

If you are still in a role, use "Present" rather than an end date. If your current role has changed internally, you can show progression under one employer:

Operations Coordinator | Greenlane Logistics | September 2021 to present

Operations Coordinator | January 2024 to present Operations Assistant | September 2021 to December 2023

This helps the reader see promotion without splitting one employer into confusing separate entries.

Some job titles are obvious. "Registered Nurse", "Payroll Administrator", or "Frontend Developer" already tell the reader something useful. Other titles need context.

A line under the heading can explain the scale or setting:

"Part of a five-person operations team supporting 180 field engineers across scheduling, purchase orders, and service reporting."

That one sentence gives the bullets a frame. It can show team size, customer type, sector, budget, region, product, caseload, technology stack, or workload volume.

Do not write a long paragraph under every job. One line is enough unless the role was unusual.

Bullet points make the section easier to scan. They also force you to separate ideas rather than bury them in prose.

A good bullet usually contains at least two of these elements:

• Action: what you did
• Context: where, for whom, or at what scale
• Skill: the capability shown
• Result: what improved, changed, or was delivered

Weak bullet:

• Responsible for stock and customer service.

Stronger bullet:

• Managed stock checks, replenishment, and customer queries during weekend shifts, helping the store maintain availability during peak trading hours.

The stronger version is not dramatic, but it gives the reader more to evaluate. It shows setting, ownership, and why the work mattered.

A common mistake is turning one bullet into a crowded sentence that tries to prove five things at once. Long bullets are harder to scan and easier to ignore.

Instead of writing one long line about customer service, reporting, stock, training, rotas, and complaints, split the evidence into the two or three points that matter most for the target job.

If the employer wants administration, focus on accuracy, systems, records, and follow-up. If they want supervision, lead with training, shift coordination, handovers, and problem escalation. If they want sales, bring forward targets, pipeline work, renewals, conversion, or customer retention.

The best CV work experience is selective. It does not try to make every past task sound equally important.

Weak:

• Responsible for answering phones and dealing with customers.

Stronger:

• Handled 50+ customer calls per day, logging account updates in Salesforce and escalating billing complaints to the resolutions team.

Why it works: the stronger version gives volume, system use, customer type, and escalation judgement.

Weak:

• Helped improve stock accuracy.

Stronger:

• Improved stock accuracy by introducing a weekly discrepancy log, helping the team reduce repeated picking errors during peak trading periods.

Why it works: it explains the action, the process introduced, and the operational benefit.

Weak:

• Supported senior managers with reports.

Stronger:

• Prepared weekly operations reports for three senior managers, combining rota, absence, service-level, and customer complaint data into one update.

Why it works: there may not be a result number, but the scope and type of responsibility are much clearer.

Weak:

• Organised charity event.

Stronger:

• Coordinated venue booking, volunteer rota, supplier communication, and ticket tracking for a charity fundraiser attended by 120 people.

Why it works: it turns unpaid experience into planning, coordination, communication, and delivery evidence.

Weak:

• Built a website for a course project.

Stronger:

• Built a responsive portfolio website using HTML, CSS, and JavaScript, then tested it across mobile and desktop browsers before submission.

Why it works: it names tools, output, testing, and practical delivery.

Numbers can make a CV more concrete, but weak numbers can feel forced. A good metric explains scale, frequency, improvement, value, risk, time saved, volume, quality, cost, speed, retention, attendance, or customer impact.

Useful examples include:

• Processed 80 invoices per week with no overdue approvals.
• Managed a diary for four directors across two sites.
• Supported a caseload of 35 service users.
• Reduced monthly reporting time from two days to one by rebuilding the tracker.
• Served up to 150 customers per shift during peak weekend trading.

Do not invent percentages because you think CVs need them. A credible scope detail is better than a false improvement claim.

Some jobs do not give you neat metrics. That is normal. You can still show value through context, complexity, trust, accuracy, pace, stakeholders, processes, or risk.

Instead of "completed admin tasks", write:

• Maintained accurate client records across appointment bookings, document uploads, and follow-up notes, reducing missed information during handovers.

Instead of "helped the team", write:

• Covered front-desk queries, stock checks, and appointment changes during staff absence, helping the team maintain service during a busy week.

The aim is not to make every task sound huge. The aim is to make the evidence understandable.

Good verbs make a bullet clearer. They do not need to sound dramatic.

Use verbs such as managed, coordinated, prepared, reviewed, resolved, supported, analysed, maintained, improved, trained, scheduled, delivered, built, tested, monitored, checked, reduced, organised, and reported.

Avoid empty phrases such as "played a key role in", "worked closely with", "was responsible for", or "was involved in" unless the rest of the sentence adds evidence. These openings often waste space.

Recruiters often skim the first one or two bullets under each role. Do not waste that space on the most obvious duty.

For a sales role, lead with targets, accounts, pipeline, retention, or revenue. For an admin role, lead with systems, accuracy, process ownership, or stakeholder support. For a healthcare role, lead with patient care, safe practice, documentation, caseload, or multidisciplinary working. For a technical role, lead with tools, deliverables, systems improved, or production impact.

If your first bullet could appear under almost anyone's CV, move it down or rewrite it.

You can still build a useful experience section if you have evidence of responsibility. Use volunteering, school or college projects, family business support, clubs, societies, sports leadership, fundraising, caring responsibilities, online projects, or personal work that shows relevant skills.

Label the section honestly. "Projects and volunteering" may be better than "Work experience" if you have not had a paid role yet.

Example:

Community Volunteer | Local Food Bank | June 2025 to present

• Sort donations, check expiry dates, prepare parcels, and support visitors during weekly distribution sessions.
• Coordinate rota updates with three other volunteers when shifts change at short notice.
• Follow confidentiality and safeguarding guidance when handling visitor information.

This is not paid employment, but it proves reliability, organisation, care, and rule-following.

For deeper no-experience guidance, link the section to your first job CV or no experience CV approach.

Career changers need translation. Do not expect the employer to work out why your previous roles matter.

Start by identifying shared responsibilities between the old and new role. These might include project delivery, customer contact, training, reporting, compliance, problem solving, documentation, stakeholder management, budgeting, or analysis.

Then write bullets that foreground the transferable part.

For example, a teacher applying for project coordination might write:

• Planned and delivered weekly lesson sequences against curriculum targets, balancing deadlines, individual needs, resource constraints, and assessment requirements.
• Coordinated communication between parents, support staff, and senior leaders to resolve attendance, behaviour, and safeguarding concerns.
• Maintained accurate progress records and used assessment data to adjust intervention priorities.

The wording does not pretend teaching is the same as project coordination. It shows planning, stakeholder communication, records, data, and deadlines in language a new employer can understand.

For a long career, your challenge is editing. The reader does not need the same level of detail for every role.

Keep recent and relevant roles detailed. Summarise older roles under a short heading such as "Earlier career" if they still matter but no longer need full bullets.

Example:

Earlier career: Retail Supervisor and Sales Assistant roles | 2008 to 2015 Built early experience in team supervision, customer service, stock control, cash handling, and store operations before moving into regional operations roles.

This keeps the timeline clear without giving half the page to old duties.

Do not build the whole section around a gap, but do not make the dates confusing either. If the gap is short, the CV may not need an explanation. If it is longer, a calm line can help.

Examples:

• Career break for family caring responsibilities, now ready to return to full-time administration work.
• Professional development period focused on Excel, bookkeeping, and payroll training.
• Travel and relocation break before returning to UK-based customer service roles.

Keep the wording factual. Then move back to the evidence that proves you can do the job.

For more detail, use the explain employment gaps guide.

Short roles can look jumpy if you do not label them. Add context where helpful:

• Fixed-term contract
• Temporary assignment
• Freelance project
• Seasonal role
• Agency placement
• Internship
• Work placement

You can group similar short roles if each one does not need a full entry.

Example:

Temporary Administration Assignments | Various employers | 2024

• Completed short-term reception, document scanning, CRM update, and inbox support assignments through a local agency.
• Adapted quickly to new processes, handling confidential information and daily handovers across three office settings.

This proves adaptability without making the CV look fragmented.

Show progression clearly under the same employer. You can either list each role separately under the employer or add a short progression line.

Example:

Team Leader | Northbank Retail | April 2024 to present Sales Assistant | Northbank Retail | May 2022 to March 2024

• Promoted after consistently meeting sales, stock accuracy, and customer feedback targets.
• Coordinate daily shift handovers, allocate floor duties, and support new starter training.
• Resolve customer issues at first point of contact where possible, escalating refund and complaint cases when required.

This helps the employer see growth and trust, not just dates.

Applicant tracking systems and recruiters both need clarity. Do not over-design the work experience section. Use normal headings, plain date formats, and readable bullets.

Use employer language where it is accurate. If the advert asks for stakeholder management and you have done stakeholder work, use that phrase naturally in the relevant bullet. If the advert asks for Excel, safeguarding, stock control, React, payroll, CRM, budget monitoring, case management, or complaint handling, connect those terms to real examples.

Do not hide keywords in a list with no proof. A skills section can help, but the experience section should show where those skills were used. Link this work to your skills on CV section so the CV feels joined up.

Remove internal jargon. Your current employer may use team names, system nicknames, or abbreviations that outsiders will not understand. Translate them into plain language.

Instead of:

• Owned weekly RAG pack for CXT and NRT handover.

Write:

• Prepared weekly status reports for customer experience and network response teams, highlighting risks, overdue actions, and service issues.

The second version can still be understood by someone outside the business.

Before:

• Worked on tills and helped customers.
• Did stock work.
• Answered questions.

After:

• Served customers at till and service desk, handling refunds, product queries, loyalty accounts, and payment issues during peak weekend trading.
• Completed daily stock checks and shelf replenishment, recording discrepancies for supervisors and supporting accurate availability.
• Used store systems to check product locations, process click-and-collect orders, and follow up delayed customer requests.

Why it works: the revised version shows customer service, systems, stock accuracy, follow-up, and busy trading conditions.

Before:

• Helped build web pages.
• Fixed bugs.
• Worked with developers.

After:

• Built responsive page components using React and CSS during a six-week internship, following design specs and accessibility notes from the product team.
• Fixed front-end bugs logged in Jira, testing changes across Chrome, Safari, and mobile breakpoints before code review.
• Paired with a senior developer to refactor repeated component logic, improving readability for future updates.

Why it works: the bullets name tools, workflow, collaboration, testing, and the type of contribution.

Before:

• Planned lessons.
• Communicated with parents.
• Kept records.

After:

• Planned weekly lesson sequences against curriculum targets, individual needs, safeguarding requirements, and assessment deadlines.
• Coordinated communication between parents, teaching assistants, and senior leaders to resolve attendance, behaviour, and support concerns.
• Maintained accurate progress records and used assessment data to adjust lesson plans and intervention priorities.

Why it works: it translates teaching into planning, stakeholder communication, documentation, and prioritisation without pretending the candidate has already been a project coordinator.

Before:

• Managed team and improved performance.
• Responsible for budgets.
• Led change projects.

After:

• Led a 22-person operations team across three sites, improving rota coverage and reducing agency staffing reliance during peak demand.
• Managed a £1.2m departmental budget, reviewing monthly spend, supplier costs, and forecast risks with finance partners.
• Delivered a new escalation process for customer complaints, reducing unresolved cases and giving senior leaders clearer weekly reporting.

Why it works: the bullets show scale, leadership, commercial responsibility, and operational improvement.

Open your CV and scan only the first half-page. What does the reader learn before they make a decision to continue?

If your work experience starts low on the page because the profile, skills list, or education section is too long, check whether that order is still right. Experienced candidates usually need work history visible quickly. Students and early-career candidates may lead with education, but still need the experience evidence to be easy to find.

After each bullet, ask: so what does this prove?

If the answer is not clear, rewrite it. A bullet should prove at least one of these:

• You can handle a responsibility in the target role.
• You have worked at a relevant level or scale.
• You used a tool, process, system, or method the employer cares about.
• You solved a problem or improved something.
• You can work with the people, pace, risk, or expectations of the job.

If a bullet only says you were present, cut it or improve it.

Candidates often repeat the same skill in every job. For example, five roles might all say "communicated with customers". You only need that many customer communication bullets if each one adds a new angle.

Vary the evidence. One bullet might show complaint handling. Another might show written follow-up. Another might show account management. Another might show difficult conversations. If they all say the same thing, keep the strongest and use the space for another skill.

A CV for a junior role should show reliability, learning, accuracy, and core responsibilities. A CV for a manager should show ownership, judgement, team leadership, decision-making, and measurable effect. A CV for a senior specialist should show depth, complexity, influence, and results.

If you are applying above your current level, include examples that show readiness for more responsibility. If you are applying sideways, show relevance and transferable evidence. If you are applying below your previous level, avoid sounding overqualified by focusing on the hands-on work you genuinely want to do.

Work experience sections often contain small errors because they have been edited many times. Check employer names, job titles, date formats, tense, punctuation, and bullet style.

Use past tense for past roles and present tense for current responsibilities. If a current role includes completed projects, past tense can still be correct for those specific achievements.

A clean section suggests care. Errors in dates or names suggest risk.