How to Write Resume Bullet Points That Pass ATS and Impress Recruiters (2026 Guide)

Two candidates apply for the same software engineering role. Same years of experience. Same tech stack. Same educational background. One gets a callback. The other gets silence. In most cases, the difference is not what they did — it is how they wrote it. Specifically, it is the quality of their resume bullet points.

A strong resume bullet does three things at once: it starts with an action verb, contains a job-description keyword in context, and ends with a quantified result. Bullet points are the most read, most scanned, and most ATS-evaluated part of your entire resume. A recruiter spends 6–8 seconds on a first pass, almost all of it reading bullet points, and the ATS scores your resume by what keywords appear, in what context, and in which sections.

Yet most resumes — including those of highly qualified candidates — have bullets that do the opposite of what they should: they describe job responsibilities instead of impact, use weak verbs, contain no numbers, and miss the keywords the ATS is scanning for. Our own data shows how decisive this is: across the 1,000+ resumes ResumeLens has analysed, 70%+ of low ATS scores were caused not by a lack of experience but by how that experience was described — weak language, missing keywords, and no quantifiable impact in the bullets that matter most.

This guide covers the three frameworks used by Harvard, Boston University, and the leading product community, the complete action-verb library organised by skill type, and a full before/after transformation table you can use immediately.

➡ Check how your current bullet points are scoring in ATS — free scan on ResumeLens.

Why bullet points are the most critical part of your resume

Your work-experience bullets carry more weight than every other section combined — for both the recruiter and the ATS.

For recruiters, bullet points are all they read on first scan. Boston University's Career Development Center confirms employers spend under ten seconds on each resume they are initially screening. In that time they are not reading your summary, skills, or education — they are scanning bullet points for role titles, company names, and the 2–3 impact statements that decide shortlist or reject. Harvard's Mignone Center puts it directly: resume language should be written for people who scan quickly.

For the ATS, bullet points are where keywords must appear in context. A keyword in your skills section tells the system you claim that skill; the same keyword inside a work-experience bullet — in the context of a real role, action, and result — carries significantly more weight, because it signals demonstrated experience rather than claimed competence. This is why two resumes with identical skills sections can score very differently.

The double test every bullet must pass

Every bullet must pass two tests at once:

Test 1 (ATS): does this bullet contain at least one keyword from the job description, used in context?
Test 2 (Recruiter): does this bullet answer "what changed because this person was here?" — with a number?

Fail Test 1 and you are invisible to the ATS. Fail Test 2 and a recruiter skims past. The frameworks below make both automatic.

➡ Check how your bullet points are scoring — free check on ResumeLens.

The three bullet-point frameworks

Three authoritative sources each provide a framework for strong bullets — the underlying principle is identical; the framing differs, which makes each useful in different contexts.

Framework	Structure	Best for
CAR (Boston University)	Context → Action → Result	Narrative, research, consulting, teaching bullets
BAR (BU Questrom)	Background → Action → Result	Senior or scope-heavy roles where environment is a signal
Action + Metric + Impact	Strong verb → specific number → why it mattered	Tech and product hiring (fastest to apply)

Framework 1: CAR — Context, Action, Result

Boston University's Career Services recommends CAR as the foundation for every bullet: the context (situation or challenge), the action you took, and the result (what measurably changed).

Example: "Redesigned onboarding email sequence using Mailchimp A/B testing, improving 7-day activation rate from 34% to 61% and reducing support queries by 28%."

Framework 2: BAR — Background, Action, Result

BU's Questrom School uses BAR, where Background captures the scale and setting of the work — particularly useful for senior roles where the scope of your environment is itself a signal.

Example: "Within a cross-functional team of 12 across engineering, design, and marketing, led the GTM strategy for a new B2B product launch, achieving 140% of first-quarter revenue target and 3,200 enterprise sign-ups within 60 days."

Framework 3: Action + Metric + Impact

The most widely used framework in tech and product hiring, aligned with Harvard's principle that resume language must be fact-based, quantified, and qualified. Every bullet starts with a strong action verb, includes a specific metric, and explains why that metric mattered.

Example: "Optimised PostgreSQL query performance, reducing average API response time from 1.2s to 180ms, enabling the platform to scale from 50K to 400K daily active users without infrastructure changes."

Which framework should you use?

All three produce the same quality of bullet when applied correctly — use whichever is easier for you to write, then check the output against the double test. For most bullets, Action + Metric + Impact is fastest. For senior or leadership-heavy roles, BAR adds scope context that makes seniority visible. For narrative-heavy bullets, CAR is the most natural structure.

The five most common bullet-point mistakes

These appear in the majority of resumes, including those of experienced candidates. Each hurts your ATS score and your recruiter impression at once.

Mistake 1: starting with a weak or passive verb

Harvard explicitly flags passive language as a top resume mistake. Bullets that begin with "Responsible for," "Helped with," "Assisted in," or "Worked on" signal passive participation, not ownership. Start with a strong action verb instead.

Mistake 2: no numbers anywhere in the bullet

Resume language must be fact-based — quantify and qualify. A bullet without a number is a claim without evidence. If you think your work cannot be quantified, ask: how many users did it affect? By what percentage did the metric change? How many people were on the team? How much time or revenue was saved? In almost every case, there is a number.

Mistake 3: describing responsibilities instead of achievements

The single most common bullet problem. A responsibility describes the job; an achievement describes what changed because of how you did it. The test: "Would this bullet appear in the job description for my role?" If yes, it is a responsibility — rewrite it. "Does it contain a before/after or a measurable outcome?" If no, add the result.

Mistake 4: not tailoring bullets to the job description

Both Harvard and BU emphasise mirroring the language of the specific role. If the JD mentions "stakeholder management," your bullet should use those exact words — not "working with cross-functional teams." The ATS matches your language against the employer's; the closer the match, the higher your score.

Mistake 5: too long, too dense, too much

Keep each bullet to two lines maximum. A bullet that runs three or four lines forces a recruiter to read a paragraph, and recruiters scanning 200 resumes will not. The rule: one accomplishment per bullet — one action, one metric, one impact. If you use "and" to connect two achievements, split it into two.

➡ See how your bullet points are being read and scored — free check on ResumeLens.

How to write bullets that directly improve your ATS score

ATS optimisation for bullets is not keyword stuffing — it is strategic placement of the right terms in the right context.

Place your strongest keywords in the first bullet of each role. The first bullet under each job title gets more parsing attention — it is the first content read after your job title and company.
Use the exact terminology from the job description. "A/B testing," not "split testing"; "stakeholder management," not "working with stakeholders." Older systems like Taleo, still widely deployed in India, do not reliably recognise synonyms.
Spell out abbreviations on first use. Write "Amazon Web Services (AWS)" and "Key Performance Indicators (KPIs)" at least once — some ATS search for the full term, others for the abbreviation.
Make your tech stack visible in bullets, not just the skills section. A tool inside a bullet — "Built automated CI/CD pipeline using Jenkins and GitHub Actions" — tells the ATS you have used it in a real role, which scores higher than the same tool in a standalone list.

Every bullet needs a number. Quantify across these five categories:

Category	What to measure
Scale	Users, customers, team members, markets, products affected
Revenue	ARR, MRR, revenue generated, cost saved, budget managed
Efficiency	Time saved, process-speed increase, error rate reduced, release cycle shortened
Growth	User-growth %, market-share gain, conversion-rate improvement
Quality	NPS improvement, customer satisfaction, churn reduction, bug reduction

Before and after bullet transformations

Each transformation applies a framework and fixes the mistakes above.

Role	Before	After
Software Developer	"Responsible for backend APIs and improving performance."	"Built and optimised REST APIs in Node.js, cutting p95 latency from 1.2s to 180ms and supporting growth from 50K to 400K daily users."
Product Manager	"Owned the product roadmap and worked with stakeholders."	"Led the onboarding redesign across engineering and design, lifting day-30 retention 34% and cutting support tickets 22%."
Business / Operations	"Handled vendor relationships and reporting."	"Renegotiated 8 vendor contracts, saving ₹14L annually, and automated weekly reporting to free 6 analyst-hours a week."
Fresher / Internship	"Made a website for a college project."	"Built an e-commerce REST API in Django serving 500+ test users at 99.8% uptime, deployed on AWS EC2."

➡ Check how your transformed bullets perform in ATS on ResumeLens.

200+ action verbs by skill category

Harvard's Mignone Center compiled a categorised action-verb library as part of its official resume guide. Use verbs that match the skills the JD asks for — and do not start every bullet with the same verb. Never begin a bullet with "Responsible for," "Helped," "Assisted," or "Was involved in."

Category	Action verbs
Leadership	Accomplished · Achieved · Administered · Analysed · Assigned · Attained · Chaired · Consolidated · Contracted · Coordinated · Delegated · Developed · Directed · Earned · Evaluated · Executed · Handled · Headed · Impacted · Improved · Increased · Led · Mastered · Orchestrated · Organised · Oversaw · Planned · Predicted · Prioritised · Produced · Proved · Recommended · Regulated · Reorganised · Reviewed · Scheduled · Spearheaded · Strengthened · Supervised · Surpassed
Communication	Addressed · Arbitrated · Arranged · Authored · Collaborated · Convinced · Corresponded · Delivered · Directed · Documented · Drafted · Edited · Energised · Enlisted · Formulated · Influenced · Interpreted · Lectured · Liaised · Mediated · Moderated · Negotiated · Persuaded · Presented · Promoted · Publicised · Reconciled · Recruited · Reported · Rewrote · Spoke · Suggested · Synthesised · Translated · Wrote
Research & Analysis	Clarified · Collected · Concluded · Conducted · Constructed · Critiqued · Derived · Determined · Diagnosed · Discovered · Evaluated · Examined · Extracted · Formed · Identified · Inspected · Interpreted · Interviewed · Investigated · Modelled · Organised · Resolved · Reviewed · Summarised · Surveyed · Systematised · Tested
Technical / Engineering	Assembled · Built · Calculated · Computed · Designed · Devised · Engineered · Fabricated · Implemented · Installed · Maintained · Operated · Optimised · Overhauled · Programmed · Remodelled · Repaired · Solved · Standardised · Streamlined · Upgraded · Automated · Deployed · Configured · Integrated · Migrated · Refactored · Architected · Containerised · Scaled
Creative & Product	Acted · Composed · Conceived · Conceptualised · Created · Customised · Designed · Developed · Directed · Established · Fashioned · Founded · Illustrated · Initiated · Instituted · Integrated · Introduced · Invented · Launched · Originated · Performed · Published · Redesigned · Revised · Revitalised · Shaped · Visualised · Prototyped · Piloted · Iterated
Quantitative & Data	Administered · Allocated · Analysed · Appraised · Audited · Balanced · Budgeted · Calculated · Computed · Developed · Forecasted · Managed · Marketed · Maximised · Minimised · Planned · Projected · Researched · Modelled · Measured · Tracked · Monitored · Reported · Benchmarked · Validated · Optimised
Teaching & Mentoring	Adapted · Advised · Clarified · Coached · Communicated · Coordinated · Demystified · Developed · Enabled · Encouraged · Evaluated · Explained · Facilitated · Guided · Informed · Instructed · Mentored · Persuaded · Set Goals · Stimulated · Taught · Trained · Upskilled · Onboarded
Organisational & Operational	Approved · Accelerated · Arranged · Broadened · Catalogued · Centralised · Changed · Classified · Compiled · Completed · Controlled · Defined · Dispatched · Executed · Expanded · Gained · Generated · Implemented · Inspected · Launched · Monitored · Operated · Organised · Prepared · Processed · Reduced · Reinforced · Retrieved · Screened · Selected · Simplified · Streamlined · Structured · Systematised · Updated · Utilised · Validated · Verified

The Harvard language rules for bullet points

Harvard's Mignone Center defines exactly what resume language should and should not be — among the clearest writing guidelines from any career institution.

What your bullet-point language should be:

Specific rather than general — "Reduced API latency by 65%," not "improved system performance."
Active rather than passive — "Led the migration," not "was responsible for leading."
Written to express, not impress — avoid jargon and filler; every word should do work.
Articulate rather than flowery — clear, direct, professional; no narrative storytelling in bullet form.
Fact-based — quantify and qualify — numbers, percentages, team sizes, time frames.
Written for people who scan quickly — the first word tells the reader what you did.

What your bullet points should NOT do:

Do not use personal pronouns — never start with "I," "My," or "We."
Do not abbreviate without explaining — spell out acronyms at least once.
Do not use a narrative style — each bullet stands alone; no connecting sentences.
Do not use slang or colloquialisms — "crushed our targets" or "killed it" — keep it professional.
Do not start each line with a date — dates belong in the job header.
Do not list responsibilities word-for-word from the job description — paraphrase and add your specific contribution and result.

➡ Upload your resume and see exactly how your bullet points score — free on ResumeLens.

Frequently asked questions

How long should a resume bullet point be?

One to two lines maximum. Boston University's career guides recommend keeping each bullet to two lines for white space and readability. A recruiter spending 6–8 seconds will not read a four-line bullet. If you are writing more than two lines, split the bullet into two achievements or cut the context and lead with the result.

How many bullet points should I have per job?

Five to seven for your two most recent and relevant roles; three to five for older or less relevant ones. Do not pad with weak bullets — five strong, quantified bullets beat eight generic ones.

What if I cannot quantify my achievements?

Almost every achievement can be quantified if you think differently. How many people did it affect? What percentage did the metric change? How much time was saved? How many projects, clients, or products were involved? If you genuinely cannot find a number, add scale context — "within a team of 8," "across 3 product lines," "serving 40,000 monthly users." Scale is a form of quantification.

Should I use the same bullet points for every job application?

No. Your base bullets should be strong across all applications, but the order and emphasis should shift to match each job description. For a role emphasising user research, lead with your user-research bullets; for a technical role, lead with technical achievements. The content stays; the prioritisation changes.

Do action verbs actually affect my ATS score?

Indirectly, yes. Action verbs do not register as keywords unless they appear in the JD, but strong, specific verbs signal structured, achievement-oriented bullets — which tend to contain more relevant keywords, more contextual usage, and more quantified outcomes, all of which improve scoring. They also improve human readability.

How do I write bullet points if I am a fresher with no work experience?

Apply the same frameworks to internships, academic projects, hackathons, open-source contributions, and volunteer work. CAR works especially well for academic projects: Context (what the project was and why), Action (what you built), Result (what it produced — users, features, ratings, awards). A well-described project with one quantified outcome beats vague professional experience with no numbers.

Is there such a thing as too many keywords in a bullet point?

Yes — keyword stuffing is recognisable to both ATS systems and recruiters, and it backfires. Modern ATS platforms flag unnaturally dense keyword usage, and recruiters spot stuffed bullets immediately. The goal is natural integration — core keywords in context, supporting a real description of real work.