Field Notes / Resume
Resume Bullets That Get Noticed
Most bullets describe the job. The reader already knows the job. They want to know what changed because you were the one holding it.
Responsible for the regional RFP process.
Led RFP responses for enterprise deals across the region.
Rebuilt the regional RFP process. Cut response time from three weeks to eight days and raised the win rate across the team.
The line I stopped on
Reading a stack, you develop a rhythm. Scan, scan, scan, stop. The stop is involuntary. Something on the page gave you a reason to slow down, and it was almost never the job title.
It was a line that told me what happened. Not what the person was assigned to do. What changed while they did it.
Duty, activity, evidence
Nearly every bullet sits on one of three rungs. The card above shows all three describing identical work.
- Duty. "Responsible for." This is copied from a job description. It tells a reader what the org chart said. Anyone in that seat had the same responsibility.
- Activity. "Led RFP responses." Better, because it names an action. Still incomplete. It says you were busy, not that it worked.
- Evidence. The action plus what moved. Now the reader learns something only you know.
Most resumes live on the first two rungs and never reach the third.
The question that lifts a bullet
Take any line and ask: so what happened?
"I managed the support queue." So what happened? "Backlog dropped." By how much? "From two weeks to three days." That is your bullet. The evidence was in your head the whole time. It never reached the page because nobody asked.
Ask it of every line. Most produce an answer within two rounds.
When you have no number
Not all good work carries a metric. Name the concrete outcome instead.
- A decision that stuck. "Chose the platform the team still runs five years on."
- A thing that shipped. "Delivered the first regional deployment, later rolled out to six countries."
- A person who grew. "Coached two engineers into team lead roles."
- A problem that stopped recurring. "Redesigned the escalation path. Repeat escalations ended."
These land because they are specific and verifiable. Vagueness is the enemy, not the absence of a percentage.
Where the strong lines go
Order inside a role matters as much as the writing. Your best evidence goes first under each job, not in chronological order of when it happened. A reader gives each role a few seconds. Spend those on your strongest line.
The same logic governs the page. Your most recent role carries the most bullets. Roles from fifteen years ago compress to a line.
Every bullet on your page describes a job someone held. Make it obvious that the someone was you. Ask what happened, then write that down.