Resume fixes that actually move the needle (and the ones that don't)

Every job seeker eventually sits down to "fix the resume," and every one of them faces the same problem: the advice is endless and contradictory, and almost none of it is ranked. Fonts, colors, length, objective statements, headshots, skill bars — the internet will happily sell you a weekend of work on any of them.

We review resumes for a living. Here's our honest ranking: the short list of changes that change outcomes, then the long list that mostly changes how the document feels to its owner.

First, be readable by the machine

Nothing else matters if the applicant tracking system can't parse your file. Standard headings, a single column, real text in a PDF or .docx, contact details in plain type — this is the floor, not the ceiling. We laid out how that screen works in why your applications vanish; get those seven structural points right once and you never think about them again.

Put numbers on your bullets

This is the single highest-value edit most resumes never get. Compare:

• "Responsible for reporting and dashboards for the operations team."
• "Built the weekly operations dashboard used by 40 managers; cut report prep from two days to same-day."

The second bullet does three jobs at once. It tells a recruiter the scale you operated at. It gives the hiring manager something concrete to ask you about in an interview. And it separates you from every other applicant whose bullets describe duties — because duties are identical across everyone who ever held the job title, and results are not. Revenue, savings, team size, volume, time, error rates, territory: whatever your work touched, some of it can be counted. Count it. And keep the numbers honest — an invented figure is exactly the kind of thing that collapses in an interview, and it isn't needed. True numbers, even modest ones, beat impressive-sounding duties.

Mirror the posting's words

Recruiters find candidates by searching for the words in their job description. If the posting says "data modeling" and your resume says "database design," you may never appear in the search — even though you meant the same thing. The fix is translation, not invention: read the posting, list the tools, skills, and title language it uses, and wherever those words honestly describe your experience, use their words instead of yours.

Mirroring is not keyword stuffing. It's making sure the true things about you are written in the language the buyer is searching for.

Two places matter most. Your job titles: if your official title was idiosyncratic — "Manager II, Insights" — and the market calls the role "Analytics Manager," present the recognizable title (many people add the official one in parentheses). And your skills section: it should read like an index of the posting's requirements that are genuinely yours. This is per-application work, and it's supposed to be. A resume tuned to one serious target beats a generic one sent to fifty.

Pass the six-second scan

Survive the machine and you reach the human — who gives you seconds, not minutes, on the first pass. Recruiters scan in a rough F-pattern: title, employer, dates, then the first bullet or two of the most recent role. Build for that scan:

• Lead each role with your strongest bullet, not your most routine one. Order inside a job matters more than almost anything below the fold.
• Keep bullets to one idea each, and short enough to read at a glance. Dense paragraphs are where good experience goes to be skipped.
• Make dates and titles effortless to find. If the scanner has to work to establish your seniority and recency, you lose the tiebreak to someone whose layout answers instantly.
• Cut ruthlessly. Early-career roles from long ago, obvious skills ("proficient in email"), and anything that repeats an earlier bullet are taking scan time away from your proof.

Now the ones that don't move the needle

None of these are crimes. They're just where anxious job seekers spend hours that the bullets above would have repaid tenfold:

• Designer templates. Columns, color blocks, icons, and skill-rating bars look great in a design gallery and parse badly in a tracking system. For roles filled through an ATS, plain and structured wins.
• The objective statement. "Seeking a challenging role where I can grow" tells the reader nothing about what you can do for them. A two-line summary naming your level, your specialty, and your best result does the job instead.
• Font and color debates. Any clean, standard typeface at a readable size is fine. Nobody was ever hired for their font, but people have been filtered out for files a machine couldn't read.
• The one-page rule. A page is right for early careers; two pages is normal and expected for senior professionals. Padding to fill two pages is a problem; so is crushing twenty years into one with a tiny font. Fit the content, not the rule.
• A photo. In the US, leave it off the resume. It adds parsing risk and bias risk and answers no question the employer is screening for. (Your LinkedIn profile is a different story — there, a good photo belongs.)

The pattern: fixes that move the needle change what the document proves — to the parser, to the search, and to the scanning human. Cosmetic fixes change how it looks to you, the one person who was already convinced.

Start with structure, then numbers, then mirroring, then the scan test. That's a resume working at full strength — and it's a finite list, which means you can actually finish it.