Most work experience sections fail in the same quiet way: they describe what the job involved, not what the person achieved in it. A reader learns that someone "was responsible for customer onboarding" and learns nothing about whether onboarding got faster, smoother, or larger under them. That distinction is the whole section. A hiring manager is not buying a list of duties. They are trying to predict what you will do for them, and past results are the only evidence you have.
The same section also has to survive a machine read before a human ever sees it. Many postings run resumes through an applicant tracking system that scores overlap with the posting before a person looks. A consistent format with plain job titles, dated entries, and the posting's own words used only where they are honestly true of your work gives both readers the same clean story. This is the same honesty rule that runs through how to list skills on a resume: mirror the posting, never invent the match.
Give every job the same anatomy
Use one format for every entry, in this order, so a reader can scan your history without relearning the layout each time:
- Job title, written the way an employer would recognise it. If your internal title was unusual, use the closest standard title and keep the internal one out of the headline.
- Company name, plus city or "Remote" for a fully remote role. Add one short line about the company only when it is not obvious what it does, for example "a 40-person logistics software firm".
- Dates as month and year, with "Present" for your current role. Month and year is the standard; years alone hide gaps and invite questions.
- Three to five bullets for recent and relevant roles, fewer for older or less relevant ones. One or two lines per bullet is enough.
List jobs in reverse chronological order, most recent first. That is the order readers expect, and it puts your strongest, most current evidence at the top. The one exception is a functional or skills-led format, which suits career changers and people with long gaps, but it still needs a dated work history section somewhere, or the reader will assume the dates are being hidden. The fuller case for each format is in chronological vs functional resume.
Customer Support Analyst, Northwind Software, Leeds, Mar 2023 - Present
Owns onboarding for new accounts on the support team, covering setup, training calls, and the first 30 days of use.
Cut average onboarding time from 11 days to 6 by rebuilding the welcome sequence and writing the setup guide the team still uses.
Handles around 40 accounts a month, with the highest first-response rating on the team in the last two quarters.
Notice the shape: one line that sets the context, then bullets that each carry a result. The context line is doing real work here. Without it, the reader cannot tell whether "cut onboarding time" happened at a five-person startup or a thousand-person firm, and that context changes what the result means.
Write bullets about results, not duties
The test for a bullet is simple: could it appear, unchanged, on the resume of anyone who held the same job? If yes, it is a duty, and it tells the reader nothing about you. "Responsible for managing the team inbox" could be true of every person who ever held the role. A result is specific to your time in it: what changed, by how much, and for whom.
A useful shape for most bullets is action, what you did, and result, in that order:
- Weak: Responsible for social media posting and reporting.
- Strong: Rebuilt the weekly reporting pack so the team stopped re-checking the same figures, cutting reporting time from a full day to two hours.
- Weak: Worked on improving the checkout flow.
- Strong: Ran usability sessions with 12 customers and rewrote the checkout error messages, after which support tickets about failed payments fell by a third over the following quarter.
Numbers help, but only numbers you can stand behind. If you do not know the exact figure, use an honest range or a scope instead: "a team of six", "around 40 accounts a month", "across three sites". Never estimate upward to sound impressive; an interviewer will ask how you measured it, and a guessed number collapses under one follow-up question. The same discipline applies to quantifying achievements on a resume, which covers what to do when the honest answer is that you never saw the numbers at all.
Order the bullets inside each entry by relevance to the job you want, not by how much time each task took. The first bullet under your most recent role is the most-read line on the whole resume. Spend it on the achievement closest to the posting, not on the duty you spent the most hours doing.
How far back should you go?
For most applicants, the last 10 to 15 years is the right window. Older roles rarely add evidence a reader can use, and they push the resume past two pages for no benefit. That does not mean deleting older work entirely. Summarise it in a short "Earlier experience" block with one line per role: title, company, and dates, no bullets. That keeps the timeline complete without spending space on jobs from a different stage of your career.
Inside the window, include every role that adds something, and be deliberate about the ones that do not. An unrelated job that fills a gap in the timeline earns one or two bullets about transferable skills, not a full entry. A short role that ended badly is still part of the timeline; leaving it out creates a gap that needs explaining, while including it honestly costs one line. The guidance on explaining employment gaps covers how to handle the spaces between roles without stretching dates.
Early-career applicants face the opposite problem: a short history that looks thin. In that case, paid work of any kind counts, and so do internships, placement years, and substantial freelance or project work, each as its own dated entry. The rule is the same as for senior applicants: the entry must show what you did and what changed, not simply that you were there. If your history is mostly education and projects, how to list projects on a resume and a resume with no experience cover how to build evidence from those instead.
Tailor the section to each posting
Tailoring work experience does not mean rewriting your history for every application. It means choosing, for each posting, which achievements to lead with and which to trim. The history stays the same; the emphasis changes.
Read the posting and mark the three or four requirements that matter most. Then, for each role on your resume, ask which of your bullets proves one of those requirements. Lead with those bullets, and cut the ones that prove nothing the posting asks for. A support role that asks for onboarding experience should see your onboarding result first, even if it was not the biggest part of that job. A role that asks for data work should see the reporting rebuild first. The method, including how to build an evidence map before you rewrite anything, is set out in how to tailor your resume to a job description.
Two limits matter here. First, never rename a title or inflate a scope to match a posting. A reader who checks references will find the difference, and the rest of the resume loses credibility with it. Second, keep one master resume with every bullet you have ever written, and save the version you send to each employer. When an interviewer asks about a line, you want to know exactly which version they are reading.
Tricky cases: promotions, overlaps, and short stints
A promotion inside one company should read as one entry with two titles, not two separate jobs. Stack the titles under the company name with their date ranges, and put the bullets under the role they belong to. That shows progression without making the reader wonder whether you changed employers.
Overlapping roles, such as a part-time job held alongside a full-time one, or freelance work run next to employment, get their own entries with their own dates. Do not merge them into a single timeline, and do not hide the overlap. Readers understand parallel work; they distrust timelines that do not add up. Freelance work in particular deserves its own entry, with clients described by type rather than named, as covered in how to list freelance work on a resume.
Short stints need no apology, but they do need a reason the reader can see. A contract role is a contract role: say so in the entry ("6-month contract"). A role that ended in redundancy or a company closure can carry one plain line. What damages a short stint is not its length but the silence around it. If you changed direction deliberately, say so, and a resume for a career change shows how to frame the pivot as a choice rather than a gap.
What to leave off
- Reasons for leaving. No entry needs to explain why you left. That conversation belongs in an interview, not on the page.
- Salary, references, and personal pronouns. Salary history is never asked for on a resume, references go on request, and "I" adds nothing to a bullet that already starts with a verb.
- Duties with no result and no context. If a bullet says nothing that only you could say, cut it or rewrite it with the outcome attached.
- Jobs that add nothing and break nothing. A two-week role from ten years ago is clutter. The earlier-experience block exists for exactly this: one line, no bullets, timeline intact.
- Skills disguised as experience. A line like "experienced in Python, SQL, and Tableau" belongs in the skills section, with evidence in the bullets, not as a bullet itself. The skills guidance is in how to list skills on a resume.
The 60-second work experience audit
Before you send any application, run this check:
- Is every entry the same shape? Title, company, location, dates, then bullets, in the same order every time.
- Does each bullet carry a result? If a bullet could belong to anyone who held the job, rewrite it or cut it.
- Is the first bullet of each role the most relevant one? Order by relevance to this posting, not by habit.
- Do the dates add up? No unexplained gaps, no overlaps hidden by merging, no years-only entries.
- Can you defend every number? If an interviewer asked how you measured it, would the answer hold?
Work experience earns its place at the top of the resume by being evidence, not biography. Write each entry as if the reader will ask one question about it, "so what changed?", and make sure the answer is already on the page. One practical check before you send: run the draft through Tailr's ATS checker and see whether the experience the posting asks for is the experience your resume actually shows, in words a parser can read. Then tailor it to the posting and keep the version you sent.