Score your resume for the six-second skim
See your resume the way a recruiter scans it.
Recruiters don't read resumes, they skim them — six to eight seconds, mostly the first words of each bullet. The Readability Scorer grades your resume on exactly what survives that skim: how many bullets open with a strong action verb, how many carry a real number, how many start with weak filler like ‘Responsible for’, and how much passive voice slows it down.
You get a score out of 100, the key stats, and specific fixes — then you can rewrite the weak lines in Bullet Booster and check your fit against a real job in TrueFit. Metrics survive skimming; adjectives don't.
- ✓Score for action verbs, quantified results, weak openers
- ✓Flags passive voice and length problems
- ✓Specific, honest fixes — not vanity metrics
- ✓Free, instant, runs in your browser
The six-second skim and what actually survives it
A recruiter's first pass through a resume takes six to eight seconds. During this time, the recruiter is not reading prose—they are scanning the first word or two of each bullet point, glancing at job titles, and looking for immediate disqualifiers (bad dates, gaps without explanation, irrelevant companies). The only text that factors into this decision is the opening word of each bullet and the section headers. Everything else is noise until the recruit decides your background is worth a deeper read.
This scanning pattern is well-documented in eye-tracking studies of resume review, though the exact timing varies by recruiter experience. A hiring manager reading fifty resumes before lunch spends four to six seconds on each one. An overloaded HR screener who has to filter three hundred applications into fifty strong candidates spends three seconds—headline, titles, and the word count are enough. If your resume is dense, the skim ends with a rejection. If your opening words are weak ("Responsible for," "Managed," "Worked on"), the recruiter does not register a skill or accomplishment, just generalized activity. The resume is invisible to them.
The winning formula is mechanical: strong action verb to open each bullet, followed immediately by what changed or was built. Weak: "Responsible for improving system performance." Strong: "Optimised database indexing, reducing query latency from 2.3 to 0.4 seconds." The verb conveys capability (optimised shows action-orientation), the next few words show the domain (database), and the number proves the scale. A six-second skim captures all of this. The weak version wastes the first two words on responsibility framing that recruiters never see.
Why quantified results are non-negotiable for visibility
Numbers survive a resume skim in ways adjectives do not. "Excellent communication" is invisible. "Presented quarterly roadmap to 200+ stakeholders, securing buy-in for three-quarter initiative" is seen. The number anchors recruiter attention and makes the role concrete. A recruiter scanning the word "presented" continues skimming. Reading "200+" forces a micro-pause—they register that you have handled scale. This is not preference; it is how attention works under time pressure.
Most candidates quantify outcomes (revenue, time saved, error reduction) but miss the easier quantifications: how many users, how many team members you led, how many systems you supported, or how many customers you interfaced with. These are often easier to recover than business metrics. If you increased revenue, that is better. If you do not have revenue numbers, the size of the user base or transaction volume is a strong substitute. A recruiter does not care whether your win was measured in dollars or in thousands of automated transactions—either proves you handled meaningful scale.
The common error is overestimating what is quantifiable. "Improved user experience" cannot be quantified; "reduced app crash rate from 8% to 2%, raising daily active users from 50,000 to 120,000" can be. Some achievements genuinely have no metric (mentoring, architecture decisions that prevented future problems). For these, anchor to the concrete output: how many engineers you mentored (number), how long it would have taken to fix the deferred problem (time), or what the failure would have cost (order-of-magnitude estimate, if you have it). A guess—"probably saved the company six figures"—is better than no number, as long as you can defend it if asked.
How passive voice and weak openers tank your visibility score
Passive voice forces recruiters to do work you should do for them. "Tests were written to verify system stability" buries the actor (you), the action (writing tests), and the outcome (stability). Under skim time, a recruiter reads "Tests were written" and sees overhead, not contribution. Active voice: "Wrote 1,200 unit tests, raising system stability from 94% to 98.2%." The recruiter now sees you drove testing and see a metric that proves the scope. Passive voice is slower to parse and psychologically reads as removed from the action.
The structural problem is that passive voice is common in formal writing, so many candidates use it to sound professional. The résumé-writing culture has reinforced this: "The product was launched" sounds more dignified than "I shipped the product." The effect is the opposite. Recruiters are trained to spot candidates who own outcomes, and passive voice signals diffused responsibility. Every passive-voice bullet wastes reading time and weakens your positioning. Rewriting five passive bullets to active voice typically adds five to ten points to a resume readability score.
Weak openers include phrases that consume space without signaling action: "Involved in," "Contributed to," "Part of," "Assisted with." These are invisible in a skim. They also signal a supporting role rather than ownership. If you did contribute to something meaningful, name the specific contribution: "Designed the schema redesign proposal that enabled 50% faster queries," not "Contributed to schema work." If you were part of a team that shipped something, find your specific contribution. If you truly only assisted (rare for interview-relevant work), name the assist concretely: "Debugged three production outages, reducing mean time to resolution from 45 minutes to 12 minutes."
Frequently asked questions
What makes a strong action verb for a resume bullet?
Strong verbs are specific and show clear action: built, shipped, designed, optimised, reduced, increased. Weak verbs are vague or passive: helped, involved, responsible, contributed, worked on. The verb should signal your agency. Use "designed" over "was part of the design process." Use "led" over "helped manage." One strong verb per bullet is enough.
How many bullets should each resume role have?
Four to six bullets per role is standard. Current role may have five to six; older roles four to five. Each bullet should open with an action verb and include a concrete outcome or number. More bullets dilute the signal; fewer may omit your strongest accomplishments. Prioritize impact over completeness.
Should I include metrics I am not 100% sure about?
Estimate conservatively but include rough numbers if exact data is lost. "Reduced latency by roughly 40%" or "Handled ~200 customer escalations" signals scale honestly. Omit the metric if you are wildly uncertain. Vague claims ("significantly improved") are worse than no metric.
Does resume format affect readability scoring?
Yes. Single column, sans-serif font (Arial, Calibri), consistent spacing, and bullet points all improve scannability. Avoid tables, columns, or dense prose blocks. Recruiters skim in straight lines down the page. Format that supports vertical scanning scores higher than format that forces horizontal reading.
What is a realistic improvement from rewriting weak bullets?
Most resumes have five to ten weak openers or passive-voice bullets. Rewriting them to action-first, quantified language typically adds 10 to 20 points to a readability score out of 100. Combined with layout fixes, most resumes can move from 55 to 75+ points, which translates to better recruiter response.
Part of Resume tools — 5 free tools in this set.
Part of JobStraight — the honest AI job-search platform. Runs in your browser; your data stays on your device.