By Peter Miller · Published August 31, 2026 · Last updated: October 5, 2026
9 min read
You've seen both extremes: three-word bullets that could describe anyone, and mini-essays that bury the result on line three. Neither one survives a six-second skim in Greenhouse.
If you're trimming tonight, don't chop outcomes to hit a mythic character limit. You're aiming for clarity, not a word-count trophy. Recruiters aren't counting characters; they're checking whether you did real work.
Check your resume for free after you trim two bullets. Long blocks sometimes mean the parser will mash lines together in plain text.
This teardown shows what too short and too long look like on real skims, and gives you paste-ready fixes without a word-count gimmick. If a posting wants a letter, keep bullets short there too via the cover letter generator .
Quick Wins
- Put scope in the first eight words before any comma.
- Split any bullet that needs three lines into two ideas.
- Read bullets aloud; if you run out of breath, cut adjectives.
What we mean by resume bullet length
Length here is visual lines on a one-page US resume, usually Calibri or Arial at 10.5–11 point with standard margins. It is not character counts from SEO tools.
Recruiters skim in an F-pattern. They catch the first five words of each bullet. If those words are Managed projects, the rest may never matter.
ATS parsers care less about line count than humans do, but pasted plain text from a PDF can glue long bullets into walls. Shorter, separate bullets survive exports better.
The best resume bullet length isn't a magic number from a blog. It's the shortest line that still lets a stranger explain what you changed for whom.
Too short: labels without proof
Micro-bullets often come from fear of bragging. They read humble and land empty.
Before: "Sales support."
After: "Supported 9 AEs on enterprise renewals; built Salesforce views so reps saw expiring contracts 60 days out."
Before: "Excel reporting."
After: "Built weekly pipeline Excel model for 40-opportunity board reviews; flagged stalled deals before quarter close."
The fix is not adjectives. It is scope plus change in the same breath.
Too long: paragraphs wearing a bullet point
Long bullets usually stack two projects, three tools, and a philosophy. Skimmers see fog.
Before: "Worked closely with cross-functional partners including product, marketing, and legal to design, launch, and iterate on a new customer onboarding journey that improved satisfaction and reduced time to value across segments while documenting playbooks."
After: "Led onboarding redesign with product and legal; cut time-to-first-value for mid-market trials."
After (split): "Documented onboarding playbooks in Notion for CS and sales engineers."
I've passed on strong candidates when bullet one was a paragraph because I could not repeat their main win thirty seconds into a phone screen.
How margins and font size change the line count
A bullet that fits on one line at 10.5 point may wrap at 11 point. That's fine if the wrap happens after the semicolon, not before the verb.
Narrow margins buy space but can trigger one-page fights. If you're forcing font to 9 point to stay on one page, you're usually hiding weak bullets instead of shortening them.
Standard US margins with Calibri 11 are the reference most recruiters expect. Test length there before you chase design tweaks.
The length band that survives skims
Target twelve to twenty-two words for most corporate bullets. Lead with verb, scope, tool. Close with an outcome clause separated by a semicolon or second short phrase.
Senior roles can run slightly longer if the first line names budget or team size. Junior roles should stay tighter because proof is in the specificity, not the adjectives.
Before: "Helped team with various marketing tasks."
After: "Owned email QA for product launches; caught template errors before 3 major sends."
Trim or split a bullet in four moves
Use this on any bullet that wraps to a third line or shrinks to a label.
Move 1: Highlight the verb
If the verb sits after a long setup, move it forward. Built, Led, Reduced, Documented should start the line when true.
Move 2: Delete setup clauses
Cut "responsible for," "worked closely with," and "various." They add length without proof.
Move 3: Split on and
Two wins joined by and become two bullets. Each gets its own outcome.
Move 4: Phone-screen read
Say the bullet in one breath. If you need a second inhale, keep cutting.
Copy-paste this length template: "[Verb] [scope] using [tool]; [outcome for named audience]." Example: "Reduced ticket backlog for 4-person support team using Zendesk macros; CS managers stopped daily status pings."
Length examples by function
Engineering bullets can name the system and the user impact in one line: "Reduced API latency for checkout service; mobile add-to-cart errors dropped after cache layer shipped."
Sales bullets should not list every account. One line per motion: "Closed 6 net-new logos in healthcare vertical; average cycle 90 days from first demo to signature."
HR and people ops bullets work when policy meets scale: "Rolled out parental leave FAQ and manager scripts; HR ticket volume on leave questions fell during open enrollment."
Before: "Various recruiting tasks."
After: "Sourced 40 niche engineering candidates via LinkedIn and GitHub; hiring manager filled two senior roles in one quarter."
Length mistakes by career stage
- Students stacking ten one-liners with no scope.
- Managers writing essay bullets to prove they did everything.
- Technical folks listing every library in one bullet instead of the shipped feature.
- Using sub-bullets under bullets, which many ATS exports flatten into soup.
Another trap is matching a template that forces exactly three lines. Your content should pick the length, not the margin gods.
Bullets that start with "Responsible for" almost always run long because the verb arrives late. Swap to owned, built, led, or reduced and you'll often drop a full line without losing proof.
If you're tempted to add a third line for context, ask whether that context belongs in bullet two. Spreading one project across two bullets reads clearer than one dense paragraph.
When you compare drafts, print at 100 percent zoom. Screen zoom hides wraps that show up on paper and in PDF exports recruiters actually open.
Tools after you resize bullets
Paste your export into the ATS checker to confirm bullets still break on separate lines in plain text.
Then score your job match so shortened bullets did not drop must-have nouns from the posting.
Let the verb show up on time
The best resume bullet length is whatever lets a tired recruiter repeat your win in one sentence. Trim labels, split essays, and keep scope up front.
When your top three bullets each land in that band, the rest of the page can breathe. Export once, read plain text, and confirm you didn't accidentally merge bullets into a wall.
Length is a symptom. Weak verbs and missing scope are the disease. Fix those and the line count usually fixes itself.
Read more
Frequently asked questions
Aim for one full line plus a short outcome clause on the next line in 11-point Calibri, or a single tight line if the outcome fits. If you need three lines, split into two bullets or cut adjectives until the verb shows up earlier.
Ultra-short bullets waste proof. A three-word line like Managed projects tells a recruiter nothing they could not guess. Short is fine only when scope sits in the same line: Managed 12 enterprise renewals in Salesforce.
Prefer one sentence with a semicolon instead of two periods. Two sentences often mean you are stacking two wins; make them two bullets so skimmers catch both.
Length alone rarely breaks parsers. Dense paragraphs without line breaks can blur together in plain-text exports. Keep one idea per bullet and use standard round bullets so copy-paste reads cleanly.