6 min read
You've seen templates that demand five bullets under every title, or advice that caps you at three no matter what you owned. Neither matches how files get opened in a queue. You're not choosing a lucky integer. You're deciding how much proof each dated block gets before someone moves on.
On a typical first skim, the reader locks onto your current job header, checks dates, then reads bullet one and bullet two. If those lines don't echo the posting, extra bullets below rarely get airtime. That's why your newest role earns the longest list, and why a 2014 retail job doesn't need six lines when you're targeting a staff engineer req tonight.
Check your resume for free after you set counts. You're confirming must-have tools still sit inside dated bullets, not only in a skills comma list you didn't trim.
Below you'll get the recency taper, a copy-paste count pass, before-and-after trims, and traps that make lean files look empty. Job searching is hard; this is about putting proof where the skim actually lands.
If the portal asks for a note, generate a cover letter after you set bullet counts so the letter doesn't repeat duties you just cut from page one.
Quick Wins
- Current role: four or five bullets; metric or scope in bullet one.
- Prior role: two or three bullets; drop duplicate tools already proved above.
- Older than eight years: one line unless the posting names that era explicitly.
How many bullets per job on a resume: the recency taper
Count follows recency, not symmetry. Your current or most relevant employer gets the most lines because that's where you prove fit for this application. The prior job gets fewer. Everything older is context unless it holds a license, platform, or leadership scope the req still names.
Think of the skim as a narrow window: title, dates, first bullets. Parsers often read the whole experience block in order, but humans weight the top of the current role. Eight bullets under one employer pushes your best metric to line six. Line six is not in the skim window for most first passes.
| Role in your story | Target bullets | What each line must do |
|---|---|---|
| Current / most relevant job | 4-5 | Distinct scope, tool, or outcome; bullet one mirrors posting language |
| Prior full-time role | 2-3 | Proof you can operate at this level; no repeated verbs from current job |
| Older roles (8+ years back) | 0-2 | One proof line or employer/title/years only |
| Short contract under six months | 1-2 | Client type, stack, shipped deliverable; honest agency or LLC label |
I've screened stacks of these in Greenhouse and Workday, and the files that move aren't the ones with identical bullet counts under every logo. They're the ones where bullet one under the current title names the same requirement the posting opened with, attached to scope I can verify on a phone screen.
Exception: you're pivoting and the proof lives in an older role. Give that older block one extra line, then keep the taper everywhere else. Exception: federal or clinical reqs that expect publications or licenses you can't cut. Keep those blocks; still don't pad unrelated 2009 duty paragraphs.
Applying in the US with state-specific norms? See how many bullets per job on a US resume for tighter one-page totals and contract wording. This page keeps the recency rule that works in any market.
What to do now: set counts in one pass
Duplicate your master file. Work on the copy. Run the four steps in order so you don't delete the only line that names a posting must-have.
Step 1: Label each employer by tier
Mark current, prior, and archive tiers in comments you'll delete later. Archive rows are anything that doesn't prove this req unless the posting names that employer or era.
Step 2: Draft high, then cut to tier caps
Before: Six bullets under your current job: three duty lines, two strong outcomes buried at bullets five and six, one duplicate Salesforce mention.
After: Four bullets: bullet one carries the Salesforce pipeline win; bullets two through four show team scope, release ownership, and a different tool from the posting. Duty-only lines deleted, not moved down.
Step 3: Merge overlap across jobs
Before: Current job bullet three and prior job bullet two both say led weekly standups for Agile team.
After: Keep standups in the job where you also shipped the release the req cares about. Replace the duplicate with a line that names budget, ticket volume, or customer count in the other role.
Step 4: Read bullet one aloud per tier
If bullet one under your current role doesn't sound like the posting's first requirement, rewrite before you upload. Parsers read in order; humans decide from the top.
Copy-paste count pass
Bullet count pass (tonight):
[ ] Current job: 4-5 lines; metric or scope in bullet 1
[ ] Prior job: 2-3 lines; no repeated tools from current job
[ ] Archive jobs: 0-2 lines or title-only
[ ] Each bullet: one outcome OR one scope marker (team size, $, volume)
[ ] Read top 3 bullets on page 1: do they match posting highlights?
Save as: FirstName_LastName_RoleFamily.pdf
For how parsers treat trimmed lists, read how resume bullet points are interpreted by ATS . Count changes are layout changes; scan the export after you cut.
When bullet counts backfire
Padding to hit five. Empty bullets with soft skills read like you had nothing to show. Two proof lines beat five assisted-with lines every time.
Shrinking font instead of lines. Below about 10.5 point body text, recruiters notice the squeeze before parsers fail. Cut bullets, not readability.
Identical counts under every logo. A uniform six-by-six layout hides your current win under old internships. Taper so page one leads with today's scope.
Sub-bullets and nested lists. One level of bullets per job. Nested lists break in iCIMS and Taleo more often than they do in Word on your screen.
For length decisions after you trim counts, see resume length guidelines that actually work . Page count follows proof density, not bullets times jobs.
Confirm the trim still parses
You moved lines and dropped dupes. Before you submit, make sure the PDF still exports clean text and that must-haves didn't vanish with the fluff.
Run a free ATS check on the trimmed file. Bullet moves sometimes break columns or nested formatting. You want experience text reading top to bottom, with bullet one still first under your current employer.
Score your job match against the posting you highlighted. If a required tool looks thin after the cut, add it back inside one dated bullet with a verb, not as a seventh synonym line in Skills.
Upload with the taper, not the template
Open the posting you're applying to tonight. Highlight three must-haves. Give your current job four or five bullets that prove them, starting with bullet one. Give the prior role two or three. Collapse everything else to proof or title lines.
How many bullets per job on a resume answers itself once you match count to skim: more lines where you're proving fit now, fewer where the work is old or off-topic. Scan the export, then upload while bullet one still echoes the requirement you marked first.
This won't invent experience you don't hold. It stops qualified work from losing the first pass because six equal blocks buried the metric that matched the req.
Read more
Frequently asked questions
No. Uniform counts treat a decade-old internship like your current director role. Give the job you're in now four or five lines when each proves a different scope or tool. Give the role before that two or three. Older employers often survive on one proof line plus title and dates unless the posting still asks for that era.
Five is fine when every line earns its spot with a distinct outcome, tool, or team size. Five duty lines that repeat assisted with reporting is too many. If bullet four says the same story as bullet two with new verbs, merge them. The cap is signal density, not a hard stop at four.
Ship two. Two lines with scope and a named tool beat four padded tasks. Add a third only when you can show a different proof point from the posting, not to fill white space. Early-career applicants sometimes use three under a relevant internship when each line names stack and outcome.
Repeating the same keyword in six bullets rarely helps. Parsers read experience text in order, but matching still needs proof in dated job lines. One bullet that names Salesforce with pipeline dollars beats three bullets that say CRM without context. Trim dupes before you worry about count.