How to Describe Work Experience on a Resume: Build Bullets From Proof
Turn real work into clear evidence without copying a job description, inventing metrics, or hiding the employment record a recruiter needs to understand.
A strong work experience section answers four questions quickly: where you worked, what you owned, how you did it, and what changed or stayed reliable because of your work. It is not a transcript of every duty and it is not a collection of dramatic numbers. Build it from facts you could explain in an interview.
Describe Work Experience in Five Passes
- Decide whether each role should be kept, compressed, or omitted.
- Capture the official record before drafting polished language.
- Turn one source fact into one evidence bullet at a time.
- Map only verified experience to the target job posting.
- Audit titles, dates, claims, keywords, and reading order in the final file.
Choose What Each Role Needs to Prove
Start with selection, not wording. The current Indeed work-experience guide treats paid roles, part-time work, temporary roles, internships, and volunteer work as usable history when they help demonstrate the target qualifications. Your task is to decide how much evidence each record deserves.
| Decision | Use it when | What to show |
|---|---|---|
| Keep and expand | The role proves several important requirements or recent progression. | Official record plus three to six distinct evidence bullets. |
| Keep and compress | The role explains continuity or one transferable skill but repeats later work. | Official record plus one or two non-duplicative bullets. |
| List without bullets | The record helps the timeline, but its tasks no longer affect the target decision. | Title, employer, location if useful, and dates. |
| Omit from this resume | The role is older, unrelated, and adds no distinct proof or needed context. | Keep it in your private master record and application history. |
Relevance is not permission to alter history. A tailored resume may select and order evidence, but the employer, title, dates, and work relationship still need to remain truthful.
Build a Source Record Before You Write
Polished bullets are easier to verify when each one points back to a private record. Gather these eight fields for every role:
Work-history source record
- Employer of record: the organization that employed or paid you.
- Official title: the title on your offer, HR record, or contract.
- Dates and location: use one consistent level of precision.
- Relationship: employee, contractor, temporary assignment, internship, or volunteer role.
- Recurring work: the tasks you actually performed, not the whole team's mandate.
- Method and tools: systems, procedures, equipment, or review steps you personally used.
- Scope: people, requests, records, locations, schedules, products, or time periods you can support.
- Result or control: an observed outcome, completed handoff, quality check, deadline, or risk you managed.
Useful sources include schedules, approved performance reviews, project notes, ticket histories, public deliverables, and your own contemporaneous records. Respect confidentiality. If a number, client name, or result cannot be disclosed or defended, use an accurate scope or process signal instead.
Turn One Source Fact Into One Evidence Bullet
A flexible evidence frame
Action + object + method + scope + result or quality signal
Not every bullet needs all five parts. Keep the parts that distinguish your work and remove any slot that would require guessing.
| Source fact | Evidence-based bullet | Proof check |
|---|---|---|
| Answered account questions in a shared queue and sent billing issues to another team. | Resolved routine account questions in the shared CRM queue, documented case notes, and escalated billing exceptions to the finance team. | Can you name the system, issue types, and escalation boundary? |
| Received shipments and checked them against paperwork. | Checked incoming shipments against packing slips, updated stock records, and flagged quantity mismatches before items reached storage. | Can you explain the record and mismatch process? |
| Managed appointment changes for an office. | Coordinated appointment changes across phone and online requests, kept the shared schedule current, and alerted staff to time-sensitive conflicts. | Can you describe the channels, schedule, and handoff? |
These are teaching examples, not claims to copy. Replace every object, tool, scope detail, and outcome with facts from your own record.
What to Write When You Do Not Have Metrics
A number is useful only when it has a source and context. Current job-seeker discussion about percentages without scope shows the failure clearly: a percentage alone does not tell the reader what changed, how large the base was, or whether the applicant measured it. The 2026 U.S. Department of Labor Resume Essentials guide also emphasizes achievement-focused bullets, but achievement does not require a fabricated number.
| Evidence type | Source question | Safe wording pattern |
|---|---|---|
| Frequency | Was this daily, weekly, seasonal, or tied to a recurring deadline? | Prepared the weekly status file and resolved missing inputs before team review. |
| Scope | Which people, systems, locations, products, or records did you support? | Maintained scheduling records for two service locations and routed conflicts to the appropriate lead. |
| Complexity | What exceptions, dependencies, or constraints made the work non-routine? | Reconciled orders across vendor records and internal inventory logs before approval. |
| Quality control | What did you verify, document, or prevent? | Reviewed intake forms for missing fields and returned incomplete records before processing. |
| Handoff | Who used your work next, and what did it enable? | Prepared clean case notes so the next-shift team could continue open requests without restarting the review. |
If you honestly know an approximate range, label it as approximate and keep the source. Never convert a guess into a precise percentage.
Complete Work Experience Example
The entry below is fictional and demonstrates structure only. Every employer, title, date, task, and detail must be replaced with your own verified record.
Patient Services Assistant
Pine Street Community Clinic · Chicago, IL · February 2024–Present · Part-time
- Scheduled and confirmed appointments across phone and online requests, updated status notes in the shared calendar, and escalated conflicts to the scheduling lead.
- Verified contact and insurance information before check-in, corrected mismatched fields through the documented intake process, and handed billing exceptions to authorized staff.
- Prepared the next-day appointment list for front-desk and clinical teams, flagging missing forms before the morning handoff.
- Answered routine questions with approved scripts and routed clinical questions to licensed staff without giving medical advice.
The sample works because it preserves the employment record, separates owned work from licensed decisions, and gives each bullet a different proof signal. It does not claim patient outcomes, perfect accuracy, or a made-up improvement percentage.
Map Your Evidence to One Target Posting
Do not paste a requirement into a bullet and call it tailoring. Use the posting as a question, then answer only with a source-backed example. The broader job-description tailoring method explains how to prioritize requirements across the full resume.
| Posting requirement | Your source record | Decision |
|---|---|---|
| Scheduling and multi-channel communication | Phone and online appointment changes; shared calendar; conflict escalation. | Lead with the scheduling bullet and use the posting's accurate phrase. |
| Confidential records | Verified intake fields and followed an approved exception process. | Show the control and boundary without exposing private data. |
| Advanced spreadsheet reporting | No performed-work example or artifact. | Do not add it to Experience. Treat it as a real qualification gap. |
Test the evidence, not just the wording. Compare your current resume with a target posting in the job-description matcher, then review each suggested term against your source record.
Match My Resume to a JobKeep Skill Claims Inside Performed Work
A skill list is not proof by itself. When a posting asks for CRM, inventory control, scheduling, Excel, or stakeholder communication, show where the skill did real work. Use the exact market phrase only when it accurately names your method or responsibility.
- Claim: CRM. Evidence: documented account cases, updated status fields, and routed exceptions in the named system.
- Claim: inventory control. Evidence: checked receipts, updated stock records, and followed a mismatch procedure.
- Claim: cross-functional communication. Evidence: identify the teams, information exchanged, and handoff your work enabled.
Run a context check. The keyword scanner can surface missing or repeated terms; keep only the words supported by your actual work.
Scan Experience KeywordsRoute Special Work Histories Before Rewriting
| Situation | Record rule | Writing decision |
|---|---|---|
| No paid work yet | Do not create an employer or job title. | Use the project, service, coursework, or activity source routes in the no-experience resume guide. |
| Promotion or multiple roles | Keep the employer and each verified title/date range clear. | Show progression and avoid repeating the same evidence under every title. |
| Agency, contract, or temporary work | Preserve the employer-of-record and client relationship. | Group only when a real agency or contract structure supports it. |
| Confidential work | Protect client names, protected data, and nonpublic results. | Use permitted scope, method, responsibility, and general outcome language. |
| Employment gap | Do not disguise the gap as employment. | Use a truthful neutral label only when context helps the application. |
Diagnose a Weak Bullet
| Signal | Why it is weak | Repair |
|---|---|---|
| Responsible for customer service | It names a duty but not the work performed. | Name the request type, channel, action, and handoff or quality control. |
| Improved performance by 30% | The baseline, measurement, ownership, and source are missing. | Add defensible context or remove the percentage. |
| Collaborated with teams | The teams, object, and outcome are invisible. | Name who exchanged what information and why the handoff mattered. |
| Excel, CRM, communication, leadership | It is a keyword pile rather than experience evidence. | Place each supported term inside a performed-work example. |
| One bullet with three unrelated outcomes | The reader cannot identify the main proof. | Split distinct evidence or keep the most relevant claim. |
For more role-by-role transformations, use the resume bullet point example library as a pattern bank, then trace every borrowed structure back to your own source facts.
Run a 60-Second Hiring Scan
- Employer, official title, location if used, and dates are easy to find.
- Present and past tense follow the actual status of the work.
- The first bullets under the most relevant role answer the posting's priority requirements.
- Every number, tool, client reference, and ownership claim has a defensible source.
- No two bullets repeat the same action with different adjectives.
- Older work is compressed before recent evidence is cut.
- The section still reads in the right order when pasted into plain text.
Check the final file. UseATSCraft can flag formatting, clarity, repetition, and keyword-context risks in the uploaded resume. It cannot verify private facts or guarantee an employer's decision.
Analyze My Work ExperienceHow UseATSCraft Reviewed This Guide
This page was materially refreshed after first-party analytics showed Organic visitors reaching the guide but not engaging deeply. The previous version offered more than 40 generic examples, universal metric advice, and ATS-score claims without a clear fact boundary. We replaced that template pattern with a role decision, source record, no-metric evidence ladder, complete fictional sample, posting map, special-history router, and final-file audit.
We reviewed the method against current Department of Labor and Indeed guidance, current job-seeker language, the surrounding UseATSCraft intent cluster, and the product's actual scope. UseATSCraft can surface parsing, structure, keyword, repetition, and job-match signals. It cannot confirm that a result happened, decide what an employer values privately, or promise an interview.
Frequently Asked Questions
Should work experience bullets list responsibilities or achievements?
Combine them. A useful bullet names the work you owned and the evidence that makes it meaningful, such as scope, method, quality control, handoff, or a verified result. A separate responsibilities list often hides the proof.
What can I write when I do not have metrics?
Use facts you can defend: frequency, workload, people or systems served, complexity, tools, accuracy checks, deadlines, escalation rules, or the handoff your work enabled. Do not invent a percentage just to make a bullet look stronger.
How many bullet points should each job have?
There is no fixed count for every role. Give the most recent and relevant roles enough bullets to prove the target requirements, compress older or repetitive work, and remove any bullet that adds no distinct evidence.
Should I include every job on my resume?
Usually not. Keep a role when it proves relevant work, explains useful progression, or prevents a confusing timeline. Compress or omit older and unrelated work when it does not help the target decision, while keeping application and background-check records accurate.
Can I change my job title to match a posting?
Keep the official title. If an internal title is unclear, you may add a plain-language equivalent in parentheses only when it accurately describes the role. Use the same truthful record across the resume, application, profile, and background check.