What makes a good resume bullet?

A strong action verb, the scope you worked at, and a measurable result, in that order, so the seven-second scan catches the win first. "Redesigned the checkout flow, cutting cart abandonment 18%" beats "Responsible for the checkout flow."

How do I quantify my resume if my work was not numeric?

Look for volume, time, frequency, comparison, or scale: how many, how much faster, how often, versus what, for how large a team or budget. A defensible estimate beats a vague claim; round conservatively and say "roughly."

How long should a resume be?

One page for most people: three to five sharp bullets per recent role, older roles trimmed to a line. Relevance and recency earn space, not seniority of memory.

Chapter II of IV

How To Write

Turn duties into evidence: bullets that show scope, action, and a measurable result.

By Kevin Tang · Updated July 2026

The short answer

A strong resume turns duties into evidence. Write every bullet as an action verb, the scope you worked at, and a measurable result, in that order, so a seven second scan catches the win first. Lead each role with its heaviest hit, and quantify with volume, time, frequency, or scale even when the work was not obviously numeric. Cut any word that carries no weight, mirror the exact language of the role you are targeting, and keep it to one page for most people. Format it as a clean single column a parser can read top to bottom.

You have the target from Chapter I. Now the resume has to prove it on the page, fast, to a reader who is barely reading. Good bullets are not written, they are engineered. Here is the mechanism.

The recruiter gives you seconds, not minutes

A recruiter's first pass over your resume lasts about seven seconds. In that window they are not reading, they are scanning: job titles, company names, dates, and the first few words of each bullet. That makes the front of every bullet prime real estate, and burying the result at the end wastes it. Write so the scan alone tells your story.

Think about what actually survives that scan. The eye jumps down the left edge and across the first few words of each line. Anything past the first half of a bullet is, on the first pass, invisible. So the front of every bullet is where the win goes and the setup comes after. You are writing for a skimmer first and a reader second.

One formula, every bullet

Strong bullets follow a shape: a strong action verb, the scope you operated at, and a measurable result. Verb first, so the scan catches it. Scope, so the reader knows the size of the game. Result, so they know you won. Compare these:

Weak: "Responsible for managing the company's social media accounts."
Strong: "Grew Instagram from 4k to 31k followers in nine months by shipping a daily short-form series."
Weak: "Worked on improving the checkout flow."
Strong: "Redesigned the checkout flow, cutting cart abandonment 18% and adding roughly $240k in annual revenue."

Notice what changed. "Responsible for" and "worked on" describe a chair you sat in. "Grew" and "redesigned" describe something you did. Duties tell the reader what your job was. Outcomes tell them what happened because you held it. Recruiters hire for the second one.

Break the strong version down: "Redesigned" is the verb, the thing you did. "the checkout flow" is the scope, what you touched. "cutting cart abandonment 18% and adding roughly $240k in annual revenue" is the result, what happened because you did it. Verb, scope, result. Once you see the shape you cannot unsee it, and every weak bullet on your resume starts to look fixable.

Lead each role with its heaviest hit

Within a single job, your bullets do not have to run in the order things happened. Put the most impressive, most relevant result first, because that is the one the scan will land on. Three to five sharp bullets per recent role beats eight thin ones, since the weak entries only dilute the strong ones and push them further down the page. Older roles can shrink to a line or two. Recency and relevance earn space, not seniority of memory. Keep the tense honest while you are at it: past tense for what you have finished, present tense only for what you are still doing right now.

Concretely: if one job gives you "managed the team calendar," "onboarded 12 new hires," and "cut onboarding time from three weeks to nine days," the last one leads, the second supports it, and the calendar line probably does not survive at all. Rank the bullets within each role by the size of the result, not the order you happened to do them in.

Find the numbers you think you do not have

"But my work was not quantifiable" almost always means you have not looked hard enough. Numbers hide inside ordinary work:

Volume: how many tickets, customers, releases, articles, or dollars you handled.
Time: how much faster something got, or how long you sustained it.
Frequency: daily, weekly, per sprint, per quarter.
Comparison: before and after, versus the target, versus last year.
Team and budget: how many people, how large a budget, how many stakeholders.

Work an example. "Handled customer support tickets" has no weight. Ask the questions above: how many (about 60 a day), how fast (resolved in under four hours on average), how consistently (across two years), compared to what (the team average was six hours), for whom (a 40-person support org). Now it reads: "Resolved roughly 60 support tickets a day in under four hours, a third faster than the team average." Same work, finally legible.

When you truly cannot measure the outcome, measure the input or the scale: "across 12 markets," "for a 40-person team," "on a $2M budget." A reasonable estimate you can defend beats a vague claim you cannot. If you are unsure, write "roughly" and round conservatively.

Cut the words that carry no weight

Every filler word shoves the number further down the line, past where the seven-second scan ever reaches. Delete these on sight:

"Responsible for," "tasked with," "duties included."
"Helped," "assisted with," "worked on." Say what you actually did.
"Successfully," "effectively," "various," "several." They add length, not meaning.
Articles and hedges wherever the bullet reads clean without them.

Read a finished bullet and try deleting each word in turn. If the meaning survives, the word was carrying nothing. "Successfully led a cross-functional team of five to effectively deliver the project on time" becomes "Led five engineers to ship the project two weeks early." Shorter, and it says more.

Match the words to the target

Verb, scope, and result make a bullet strong. Matching its language to the role makes it findable. Where a real result of yours lines up with a phrase from the postings you studied in Chapter I, use their phrase. If the role says "experimentation" and you ran A/B tests, the word "experimentation" belongs on your page. This is not keyword stuffing, it is speaking the role's language where it is genuinely true of you. The ATS resume guide covers how the parsing and matching actually work under the hood.

Format so a machine can read you

Most applications pass through an applicant tracking system before a human ever sees them, and those parsers are literal. Fancy layouts confuse them and quietly drop your content. Keep the structure boring and bulletproof:

One column. Multi-column layouts scramble when they are parsed.
Standard section headings: Experience, Education, Skills. The parser looks for those exact words.
No tables, text boxes, headers, footers, or images. Text trapped inside them often vanishes.
Real bullet characters and standard fonts, with no icons standing in for words.
Save as a text-based PDF or .docx, never a scanned image or a screenshot.

A clean, parseable, outcome-driven resume is doing two jobs at once: it clears the machine first, then it rewards the seven-second human scan waiting on the other side.