Module 4: Bullet Points and Accomplishments — Evidence, Not Job Descriptions
Table of Contents
← Return to the Resume Optimization Course
Most people write job descriptions in their bullet points. Recruiters already know what a software engineer does, what a project manager coordinates, or what an analyst analyzes. What they don’t know — and what the resume needs to show — is what you specifically did and how well.
This module takes about 12 minutes. After reading it, you’ll have a formula, a verb bank, and rules for adding numbers to any bullet.
The Core Problem: Duties vs. Accomplishments
Weak bullet (duty):
Responsible for managing cloud infrastructure
Strong bullet (accomplishment):
Reduced AWS infrastructure costs 34% by migrating legacy EC2 workloads to containerized services on ECS
Both describe real work. One describes the job. The other describes the person doing it exceptionally well.
Recruiters read dozens of resumes that say “managed cloud infrastructure.” The accomplishment-based version signals that you made a measurable difference — which is the only information that matters in a hiring decision.
The Formula: Action + What You Did + Result
Every strong bullet has three components:
[Strong verb] + [what you actually did] + [measurable result or scope]
The verb signals ownership and initiative. The middle clause describes the actual work. The result shows the impact.
More examples:
| Weak | Strong |
|---|---|
| “Worked on backend API” | “Built REST API serving 2M daily requests with 99.95% uptime” |
| “Helped reduce churn” | “Reduced customer churn 18% by redesigning the onboarding flow based on dropout analysis” |
| “Assisted with hiring” | “Screened 60+ candidates and built interview rubric now used across all engineering hiring” |
| “Managed social accounts” | “Grew Instagram follower count from 4K to 28K in 8 months through weekly short-form video series” |
Strong Opening Verbs
The first word of each bullet determines its strength. Use verbs that signal ownership and action.
High-impact verbs by category:
| Category | Verbs |
|---|---|
| Built / created | Built, Designed, Architected, Developed, Launched, Shipped, Created, Deployed |
| Led / owned | Led, Owned, Directed, Managed, Spearheaded, Championed, Drove |
| Improved | Reduced, Increased, Improved, Streamlined, Accelerated, Optimized, Consolidated |
| Analyzed | Audited, Analyzed, Investigated, Diagnosed, Evaluated, Assessed |
| Trained / mentored | Trained, Mentored, Coached, Onboarded, Facilitated |
| Negotiated | Negotiated, Secured, Closed, Partnered with |
| Automated | Automated, Scripted, Integrated, Migrated, Refactored |
Verbs to avoid:
- Responsible for — passive, doesn’t signal ownership
- Assisted with — makes you a helper, not a doer
- Helped — same problem
- Worked on — no specificity
- Participated in — weaker than “contributed to”
- Was involved in — tells the reader nothing
Numbers Matter — Even Rough Ones
Quantified bullets stand out. Recruiters trust specifics more than generalizations.
If you have exact numbers, use them:
- “Reduced page load time by 2.3 seconds”
- “Managed $4.2M annual budget”
- “Led team of 12 across 3 time zones”
If you don’t have exact numbers, use ranges or context:
- “~20% reduction in support tickets” — the tilde signals “approximately”
- “team of 8 engineers” — scope still communicates scale
- “3M+ monthly active users” — the + sign handles the imprecision
- “$500K–$1M in annual contract value” — range is honest
If there are no numbers at all, describe scope and ownership:
- “Sole engineer responsible for authentication service serving all enterprise clients”
- “First hire on the data team; defined analytics infrastructure from scratch”
“I don’t have metrics” is rarely true. Every role affected something measurable. Find the closest proxy: how many users, how much revenue, how large the team, how frequent the task, how much time was saved, how many bugs closed.
What Counts as Evidence
Evidence isn’t only revenue and cost savings. Any of these work:
- Scale: users, customers, accounts, transactions, events per second
- Speed: how much faster, how much less time, launch date met vs. missed
- Quality: error rate, uptime, satisfaction score, NPS, defect rate
- Scope: team size, budget, number of projects, geographic spread
- Adoption: downloads, installs, active users, departments using your work
- Frequency: weekly, monthly, per quarter — volume signals reliability
Bullet Length and Density
Length:
- Aim for 1–2 lines per bullet, 3 lines maximum
- If a bullet requires 3 lines, it usually contains two separate accomplishments — split them
- One-line bullets are fine if they’re specific and strong
Density per role:
- 3–5 bullets per role is the standard range
- Most recent and most relevant roles: 4–5 bullets
- Older or less relevant roles: 2–3 bullets
- Short contract or early-career roles: 2 bullets maximum
Don’t pad roles to fill space. A role with 2 strong bullets is better than a role with 5 weak ones.
The “So What?” Test
Read each bullet and ask: so what?
“Built REST API” So what? How many users? What uptime? For what purpose?
“Built REST API serving 2M daily requests with 99.95% uptime” So what? This is self-contained — the scale and reliability make the value clear.
If you can still ask “so what?” after reading a bullet, it needs a result or scope added.
Tense Rules
Current role: Present tense
“Lead weekly architecture reviews with 4 engineering teams”
Previous roles: Past tense
“Led weekly architecture reviews with 4 engineering teams”
Don’t mix tenses within the same role. Pick one and stick to it.
Rewriting Weak Bullets: Practice
Work through these rewrites before moving on:
Before: “Responsible for customer support tickets” After: “Resolved 40+ support tickets weekly with 97% first-response satisfaction score; built FAQ that reduced repeat ticket volume 28%”
Before: “Helped with product launches” After: “Coordinated 3 product launches across design, engineering, and marketing teams; all shipped on schedule within Q2 2024”
Before: “Worked on data pipeline” After: “Redesigned ETL pipeline processing 10M daily records, reducing job runtime from 4 hours to 22 minutes”
Next Steps
Strong bullets are the evidence. The next module covers keywords — making sure the right vocabulary appears so the ATS matches you to the role.
→ Module 5: Keywords and the Skills Section
Or return to the course hub: Resume Optimization Course Start
