How to Write Resume Bullet Points That Get Interviews

I spent three years screening resumes at a staffing agency before I started rewriting them. In that time I read somewhere north of 15,000 resumes. I can tell you the single most common reason qualified candidates get rejected: their bullet points describe what they did, not what they accomplished.

"Responsible for managing the social media calendar."

That bullet tells me you had a job. It does not tell me whether you were good at it. Compare:

"Grew Instagram following from 12K to 47K in eight months by shifting from promotional posts to educational carousel content, increasing profile-to-website click-through rate by 340%."

Same job. Same person. But the second bullet tells me exactly what you did, how you did it, and what happened as a result. That is what gets you an interview.

The difference between these two bullets is not talent or experience. It is a formula. Once you know it, every bullet point becomes easier to write — and far more effective.

The formula: Action + Context + Result

Every strong resume bullet has three parts:

Action — what you did, stated with a specific verb. Not "helped with" or "worked on." "Built." "Led." "Redesigned." "Cut." "Grew." The verb matters more than anything else in the bullet.

Context — the scope or method that makes the action credible. "Led a team of 6" is stronger than "Led a team." "Migrated a 200K-line Rails monolith" is stronger than "Migrated a codebase." Context proves the action was meaningful.

Result — what changed because of what you did. Ideally a number. "Cut customer acquisition cost by 34%." "Reduced ticket resolution time from 48 hours to 6." The result is what hiring managers actually care about.

Most resumes have Action only. Good resumes have Action + Context. The resumes that get interviews have all three.

Let me show you the transformation:

Before: "Managed email marketing campaigns."

After: "Rebuilt the abandoned-cart email flow in Klaviyo, recovering an estimated $140K in lost quarterly revenue and lifting overall email-attributed sales by 22%."

The before tells me nothing. The after tells me you understood the problem (abandoned carts), knew the tool (Klaviyo), and delivered a measurable result ($140K, 22%). That is a bullet that earns an interview.

Why most people get this wrong

I see three reasons people write weak bullets, and all three are fixable.

Reason one: They copy their job description. Your job description lists responsibilities, not achievements. "Responsible for managing vendor relationships" is a responsibility. "Renegotiated contracts with 14 vendors, saving $180K annually without service reduction" is an achievement. As I wrote in nobody cares what you were responsible for, the word "responsible" is a red flag that tells the reader you have not thought about what you actually accomplished.

Reason two: They are modest. I once asked a client what she achieved at her last job. She said "nothing special, just normal work." Then she mentioned offhand that she had trained every new hire in her department for two years and written the onboarding manual they still use. That is not nothing. That is a bullet point.

Reason three: They do not know their own numbers. You probably do not track every metric in real time, but you can reconstruct the important ones. How many people did you manage? How big was the budget? How long did the project take? What was the outcome? If you genuinely cannot find a number, use scope instead: "Led the largest product launch in company history" or "Managed the team's highest-revenue account."

The action verb matters more than you think

Weak verbs kill bullets. Strong verbs save them.

The worst verb on a resume is "helped." It tells the reader nothing about your contribution. Did you help by doing the work, or did you help by holding the door? "Helped launch the new website" could mean you wrote the code or you ordered the pizza.

Replace vague verbs with specific ones:

| Weak verb | Stronger alternatives | |-----------|----------------------| | Helped | Built, Co-led, Delivered, Owned | | Worked on | Designed, Shipped, Implemented, Migrated | | Responsible for | Directed, Managed, Oversaw, Coordinated | | Handled | Processed, Resolved, Negotiated, Triaged | | Used | Built with, Deployed on, Automated using |

I cover the broader strategy of turning responsibilities into achievements in my resume summary guide, but the bullets are where the proof actually lives. Your summary makes the claim. Your bullets deliver the evidence.

How to quantify when you think you cannot

The most common objection I hear is "my work does not have numbers." Almost always, that is wrong. Here are eight categories of numbers that apply to almost any role:

Volume — How many? Customers, projects, reports, tickets, accounts, events. "Onboarded 120+ new clients" beats "onboarded new clients."

Time — How fast? Or how long did something take? "Cut monthly close from 12 days to 4" beats "streamlined the close process."

Money — Revenue, cost, savings, budget size. "Managed a $2.4M annual ad budget" or "Saved $85K in annual software spend by consolidating three tools."

Size — Team size, company size, market size. "Led a 14-person cross-functional team" or "Owned product strategy for a 9-million-user app."

Growth — Before and after. "Grew the email list from 8K to 52K subscribers."

Rank — Where you stood. "Ranked #2 of 38 sales reps" or "Top-performing store in the region."

Frequency — How often. "Reviewed 200+ legal contracts per quarter" or "Shipped 23 features in 12 months."

Scope — What you affected. "Owned the redesign that touched every page on the site" or "Trained every new hire for two years."

Pick whichever category fits. You do not need all eight. One strong number per bullet is enough.

30+ before and after examples by role

These are real rewrites I have done for clients, anonymized. Notice how every "after" version uses Action + Context + Result.

Software Engineering

Before: Worked on the company website. After: Led the migration of a 200K-line Rails monolith to a microservices architecture, cutting average deploy time from 4 hours to 12 minutes and reducing production incidents by 40%.

Before: Helped with code reviews. After: Reviewed 40+ pull requests per week across a 12-engineer team, introducing a checklist that cut post-merge bug rate by 28%.

Before: Wrote tests. After: Built the team's first integration test suite in Cypress, raising coverage from 12% to 78% and reducing regression-related hotfixes by half.

Marketing

Before: Managed social media. After: Grew the LinkedIn following from 8K to 47K in 9 months by launching a weekly thought-leadership series, driving 35% of inbound demo requests.

Before: Ran email campaigns. After: Rebuilt the abandoned-cart flow in Klaviyo, recovering $140K in estimated lost quarterly revenue and lifting email-attributed sales by 22%.

Before: Did SEO work. After: Restructured 180+ blog posts around intent-based keyword clusters, growing organic traffic 165% in six months and pushing 14 pages into the top 3 Google results.

Sales

Before: Met sales targets. After: Closed $2.4M in new ARR against a $1.8M quota, ranking #3 of 42 reps and earning Presidents Club for the second consecutive year.

Before: Handled accounts. After: Grew a stalled enterprise account from $80K to $410K in annual revenue over 18 months by expanding into three new business units.

Before: Did cold outreach. After: Built the outbound playbook that two other teams adopted company-wide, lifting team-wide reply rates from 4% to 11%.

Data and Analytics

Before: Analyzed data. After: Built a churn-prediction model in Python that flagged 1,200 at-risk accounts and enabled a save campaign that retained $640K in annual revenue.

Before: Made dashboards. After: Replaced six manual weekly reports with an automated Tableau dashboard, saving the analytics team 14 hours per week.

Before: Helped with experiments. After: Designed and shipped 40+ A/B tests in 12 months, three of which produced double-digit conversion lifts now standard across the product.

Project and Operations Management

Before: Managed projects. After: Delivered a 9-month EHR implementation across three hospital units on time and 12% under budget, with zero post-launch critical incidents.

Before: Improved processes. After: Rebuilt the vendor onboarding workflow, cutting average time-to-first-invoice from 21 days to 6 and eliminating 90% of manual data entry.

Before: Led meetings. After: Facilitated weekly cross-functional syncs across 6 departments, surfacing blockers early enough to prevent 3 major launch delays.

Design

Before: Designed screens. After: Redesigned the onboarding flow for a 2M-user fitness app, lifting 30-day retention from 31% to 48% after a 3-week ship.

Before: Did user research. After: Ran 24 moderated usability sessions that exposed a checkout friction point, leading to a redesign that lifted completed purchases by 19%.

Before: Made the brand look better. After: Built the company's first design system (62 components, 4 platforms), cutting average feature-design time from 3 weeks to 9 days.

Healthcare and Nursing

Before: Took care of patients. After: Managed care for 4-6 critical ICU patients per shift, maintaining a zero-incident safety record across 1,200+ shifts over four years.

Before: Trained new staff. After: Preceptored 11 new graduate RNs through their 12-week orientation, with 100% retention at the one-year mark.

Before: Helped with quality improvement. After: Co-led a central-line infection reduction initiative that cut CLABSI rates by 60% unit-wide over 18 months.

Finance and Accounting

Before: Did month-end close. After: Cut the monthly close from 12 days to 4 by automating 3 reconciliation workflows, freeing the team to take on board-level reporting.

Before: Managed budgets. After: Oversaw a $4.2M annual operating budget, identifying $310K in reallocated spend that funded a new hire without headcount approval.

Before: Helped with audits. After: Led the SOX documentation refresh for 14 controls, passing the external audit with zero material findings for the first time in three years.

How many bullets per job?

This is one of the most common questions I get. The answer depends on relevance.

For your most recent and most relevant roles: 4 to 6 bullets. These are the bullets that get read.

For older or less relevant roles: 2 to 3 bullets. Enough to show you did the job, not so much that you bury the good stuff.

For roles more than 10 years ago: 1 to 2 bullets, or just the job title and dates if the role is not relevant. I cover how far back your resume should go in my guide on resume length — the short version is that old bullets rarely earn their space.

The first bullet under each job is the most important. Recruiters often read only the first bullet of each role during their initial scan. Put your strongest achievement there, not your most mundane responsibility.

Four mistakes that quietly kill your bullets

1. Starting with "Responsible for." As I noted above, this phrase is the universal signal that you have not thought about your achievements. Strike it from your vocabulary. Start every bullet with a verb.

2. Writing paragraphs instead of bullets. A bullet point is one line, maybe two. If your bullet wraps to three lines, it is a paragraph disguised as a bullet. Cut it in half or split it into two bullets.

3. Using corporate jargon. "Synergized cross-functional stakeholders to operationalize strategic initiatives." No one knows what that means. Write the way you would explain your job to a smart friend. Clarity beats sophistication every time.

4. Listing the same metric twice. If three of your bullets all say "increased revenue by 20%," you have one achievement stretched across three lines. Pick the strongest framing and cut the other two. Variety matters — recruiters notice when every bullet claims the same result. This is one of the resume mistakes that quietly kill your chances, and it is more common than you would think.

The 5-minute bullet rewrite exercise

Take your three weakest bullets right now and run them through this:

Step one: Find the verb. What did you actually do? Not your job title — the action. "Built." "Cut." "Grew." "Led."

Step two: Add scope. How big was it? How many people? How much money? How long did it take?

Step three: Find the result. What changed? Even a rough estimate counts. If you cannot find a number, use scope or rank instead.

Step four: Combine. Action + Context + Result, in one or two lines.

Most people can rewrite a bullet in under two minutes once they have the formula. The hard part is not the writing — it is remembering what you actually accomplished.

When you are done, run your resume through ResumeScorer for a free ATS score. The scorer will flag weak bullets, missing keywords, and formatting issues before a recruiter ever sees them. It takes 30 seconds and it is the fastest way to know whether your bullets are pulling their weight.

The candidate I mentioned at the start — the one whose bullet said "Responsible for managing the social media calendar" — rewrote that single line in about ten minutes. She did not change jobs, get a promotion, or learn a new skill. She just described her work the way it actually happened.

She got two interview invitations the next week.

Your bullets are the proof behind every claim your resume makes. They are where hiring managers decide whether to keep reading or move on. Spend an hour on them. Use the formula. Quantify where you can. Cut the words that add nothing. Then test the result.

The difference between a resume that gets ignored and one that gets interviews is often three or four rewritten lines. Yours are next.