Work experience is the heart of a resume, and most people write it as a list of duties. Recruiters already know what a "project manager" does. What they want to know is what happened because you did it.
One pattern for every bullet
What you did, how, and what changed.
- Duty: "Responsible for customer support emails."
- Result: "Answered 60 support emails a day and cut the average reply time from two days to four hours by writing a library of templated answers."
Start each bullet with a verb in the past tense (present tense for your current job): led, built, cut, grew, shipped, trained, negotiated.
Numbers, even rough ones
Numbers make a claim believable: people, money, time, volume, percentages. If you don't know the exact figure, use an honest estimate and say so in the interview: "around 200 customers", "roughly 30% faster". Never invent one.
No numbers at all? Show scope instead: who used it, how often, what it replaced, who asked for it next.
How many bullets
- Recent and relevant jobs: three to six.
- Older or unrelated jobs: one or two, or just the title and dates.
- Ten or more years back: you can group them under "Earlier roles" with one line each.
Order matters
Put the bullet most relevant to the job you're applying for first. Readers skim the first one or two and move on.
Check your work
The ATS check on jsonresume.org flags highlights with no numbers and jobs with too few highlights, and takes you to the field to fix.
Make your resume or open your editor.