Strip away the header and the headings and a resume is a list of bullet points. They are what a recruiter actually reads, what an applicant tracking system actually indexes, and where most resumes quietly fail: duties instead of results, "responsible for" instead of a verb, and no numbers anywhere. The fix is mechanical once you see the pattern. Here is the formula, then twenty rewrites you can pattern-match against your own lines.
The Four-Part Formula
Every strong bullet contains the same four parts, usually in this order:
Reduced customer wait time by rebuilding the ticket-routing rules — from 48 hours to under 6.
- Action verb. Past tense for previous roles, present for your current one. Our action verb list has sixty grouped by type.
- What you did. The task, named specifically — not "various projects" but "the checkout redesign."
- How. The tool, method or approach. This is where the posting's keywords naturally land.
- Result. A number, a before/after, or a concrete outcome. This part is what separates a bullet from a job description.
Not every bullet will have all four. But every bullet in your most recent role should try, and the first bullet under each role must.
Finding Numbers When You "Don't Have Any"
Most people have more numbers than they think — they are just not on a dashboard. Look for scale (how many customers, tickets, students, transactions, lines of code, locations), frequency (per day, per week, per release), money (budget managed, revenue touched, cost avoided), time (hours saved, days cut from a process), and people (team size, stakeholders, trainees). An honest estimate stated as one — "roughly 200 tickets a week" — is far stronger than no number, and far safer than an invented precise one.
Twenty Before-and-After Rewrites
Each pair keeps the same underlying job; only the writing changes. The figures are illustrative — substitute your own.
- Sales. Before: Responsible for managing client accounts. After: Managed a portfolio of 35 mid-market accounts, renewing 92% and growing annual revenue by $410K.
- Software engineering. Before: Worked on backend services. After: Built a Go service handling 2M requests/day, cutting p95 latency from 800 ms to 120 ms with Redis caching.
- Teaching. Before: Taught mathematics to secondary students. After: Taught mathematics to 150 students across five classes; raised the pass rate from 71% to 88% in two years with weekly diagnostic quizzes.
- Customer support. Before: Handled customer complaints. After: Resolved roughly 60 support tickets a day at a 94% first-contact resolution rate, the highest on a team of twelve.
- Operations. Before: Improved warehouse processes. After: Redesigned the pick-and-pack flow for a 40,000-SKU warehouse, cutting order errors by a third and overtime by 15 hours a week.
- Marketing. Before: Ran social media accounts. After: Grew the company's LinkedIn following from 4K to 27K in 14 months, generating 1,100 inbound demo requests.
- Finance. Before: Prepared monthly reports. After: Automated the month-end reporting pack in Excel and Power Query, reducing close time from five days to two.
- Human resources. Before: Involved in recruitment. After: Ran end-to-end hiring for 45 roles in a year, cutting average time-to-fill from 52 to 31 days by restructuring the screening stage.
- Nursing. Before: Provided patient care on the ward. After: Coordinated care for a 28-bed surgical ward, leading the handover redesign that reduced medication timing errors by 40%.
- Data analysis. Before: Analyzed data for the team. After: Built a churn model in Python that flagged 70% of at-risk customers a month early, informing a retention campaign worth $250K.
- Project management. Before: Managed projects. After: Delivered a 14-month ERP migration for 300 users on schedule and 8% under a $1.2M budget.
- Design. Before: Designed user interfaces. After: Redesigned the onboarding flow in Figma, lifting activation from 38% to 57% in the first quarter after release.
- Retail management. Before: Supervised store staff. After: Led a team of 22 across two shifts, cutting staff turnover from 60% to 35% and beating the store sales target for six consecutive quarters.
- Administration. Before: Handled scheduling and correspondence. After: Managed calendars and travel for four directors and reworked the shared scheduling system, eliminating double-bookings.
- Content writing. Before: Wrote blog posts. After: Wrote 80 long-form articles that now bring in 45,000 organic visits a month, including the site's top three pages.
- Logistics. Before: Coordinated shipments. After: Coordinated 120 international shipments a month across three freight forwarders, cutting average customs delay from six days to two.
- QA / testing. Before: Tested the application. After: Built an automated regression suite of 600 tests in Playwright, catching 30% of defects before code review.
- Internship. Before: Assisted the marketing team. After: Researched and shortlisted 40 podcast sponsorship targets, three of which the team booked within the quarter.
- Hospitality. Before: Worked front desk. After: Ran check-in for a 180-room hotel, keeping guest-review scores above 4.6 while processing 200+ arrivals on peak days.
- Volunteer / community. Before: Volunteered at a local charity. After: Organized a 40-volunteer food-drive team that collected 3.2 tonnes of supplies, double the previous year.
Length, Count and Order
- One to two lines per bullet. If it wraps to a third line, it is two bullets or one with padding.
- Three to five bullets per role. Six to eight for your current or most relevant role; two or three for older ones.
- Most relevant first. Recruiters read the first bullet under each role and skim the rest. Reorder for each application using the posting — our tailoring guide shows how.
- Start with the verb, not "I" or the company. "Led…" not "I led…" and not "At Acme I led…".
Phrases to Delete on Sight
- "Responsible for", "duties included", "tasked with" — replace with the verb for what you actually did.
- "Helped", "assisted with", "participated in" — say what your part was, specifically.
- "Various", "multiple", "several" — replace with the number.
- "Successfully", "effectively", "efficiently" — the result proves it; the adverb just asks to be believed.
- "Team player", "hard-working", "detail-oriented" — traits are demonstrated by bullets, not declared in them.
The free ATSVerse ATS checker scores exactly these patterns — quantified bullets, strong opening verbs and filler phrases — so you can see which lines still need work.