Six seconds, and most bullets waste them
On the first pass, a recruiter or hiring manager spends a handful of seconds per resume - the research that floats around says roughly six or seven. Whatever the exact number, it is short, and it is a scan, not a read. Your bullets are competing for a glance.
Most engineering resume bullets lose that glance because they describe responsibilities instead of impact. Here is how to write ones that survive the scan.
Responsibilities are invisible. Impact is not.
Compare these two:
- "Responsible for maintaining the backend API and fixing bugs."
- "Cut API p99 latency from 1.2s to 300ms by adding query caching, unblocking the mobile team's launch."
The first describes a job. The second describes a result. In a six-second scan, the second one has a number that catches the eye and an outcome that means something. The first one blends into every other resume.
The pattern: led with the result, then the action, then the impact on something that mattered. What changed, what you did, and why anyone cared.
Put a number on it whenever you honestly can
Numbers are what the eye catches in a scan. Latency, throughput, error rates, time saved, users served, cost reduced, scope. You do not need precise telemetry for everything - "reduced deploy time from 40 minutes to under 10" from memory is fine - but do not invent precision you cannot defend, because the number you put on the page is a number you will be asked about in the interview.
If a result is genuinely hard to quantify, use scale or scope instead. "Migrated a service handling 2M daily requests with zero downtime" works even without a percentage.
Start with a strong verb, cut the filler
"Responsible for," "helped with," and "worked on" are dead weight. Start with what you actually did: built, shipped, cut, designed, migrated, automated, led. The verb is the most visible word in the bullet; make it earn its place.
And cut the hedges. "Helped improve" is weaker than "improved." If you did it, own it.
Order them by what you want them to notice
The bullets at the top of each role get read; the ones at the bottom often do not. So put your strongest, most relevant, most quantified bullet first under each job. Do not bury the impressive thing in position four where the scan never reaches it.
The test
Read each bullet and ask: does this tell the reader something changed because I was there? If it just describes what I was assigned, rewrite it around the result. A resume of impact bullets survives the scan. A resume of responsibility bullets gets six seconds and a polite pass.