Proofread Your Resume Like an Editor

Proofread your resume in separate passes, each looking for one kind of error, with a break between writing and checking. One pass for spelling, one for dates, one for consistency, one aloud for rhythm, and one final look at the exported file. Trying to catch everything in a single read is why typos survive on documents people have opened fifty times — you stop seeing text you wrote.

Why your own errors are invisible

You read what you meant, not what’s there. Your brain fills in the word you intended, corrects the transposed letter, and skips the duplicated “the.” This gets worse the more times you’ve read the document, which means the resume you’ve been editing for two weeks is the one you’re least able to check.

Two things break the effect: time and disruption. A day between writing and proofreading resets your familiarity. Changing how the text looks — different font, different medium, different direction — forces your eye to actually track the characters.

Pass 1: spelling, with the machine and then without it

Run the spellchecker first, because it catches the easy things instantly. Then stop trusting it, because it cannot catch:

Real words in the wrong place. “Manger” for “manager,” “lead” for “led,” “form” for “from,” “then” for “than,” “your” for “you’re.”
Wrong-but-spelled-right names. “Javascript” for “JavaScript,” “Quickbooks” for “QuickBooks,” “Salesforce” spelled as two words.
Company names. Misspelling the employer you’re applying to is the single most damaging typo available, and it’s usually in a cover letter or a summary line you tailored in a hurry.
Your own job titles, which you’ve typed so many times you no longer look at them.

For this pass, read the document backwards — last bullet to first. It sounds strange and it works, because reading in reverse destroys the narrative flow your brain uses to autocomplete. You’re left looking at words as objects.

Pass 2: every number and date

Dates are the most error-prone content on a resume, because they get updated piecemeal.

Check, in order:

Chronology. Roles in descending order, no accidental reordering after an edit.
Overlaps and holes. Two jobs claiming the same three months, or a two-month hole you didn’t intend, both raise questions you don’t want asked. If a gap is real, that’s fine — just make sure it’s the real one.
The end date on your current role. It should say “Present.” A stale end date from a previous update is a classic.
Graduation years against your work history. A degree finished after a job you held during school is normal; a degree finished before you were born is a typo nobody catches.
Format consistency. One style across every entry — see tense, person, and punctuation for the dash and format conventions.
Every figure in a bullet. Not just whether it’s typed correctly, but whether you can say where it came from. If you can’t, replace it — how to quantify achievements without inventing numbers has the alternatives.

Pass 3: consistency, one attribute at a time

This is the pass that separates a good resume from a careless one, and it’s mechanical enough to do while tired. Scan for one thing at a time, all the way down the page:

Bullet-ending punctuation — all periods or none.
First word of every bullet — verb, right tense, not the same verb four times.
Section headings — same capitalization, same font size, same spacing above and below.
Job entry structure — title, employer, location, dates, in the same order every time.
Indentation and bullet glyph — the same throughout, including in sections you added later.
Font — check that a pasted line didn’t bring a different typeface with it.

Pasted text is the usual culprit for items 5 and 6. Anything you copied in from another document, an email, or a chat window may carry hidden formatting.

Pass 4: read it aloud

Reading aloud is the only reliable way to catch problems of rhythm and sense rather than spelling. You’ll hear:

Bullets that don’t parse as sentences, usually because you deleted a word mid-edit.
Two bullets in a row that say nearly the same thing.
Bullets so long you run out of breath — the signal to split them.
Jargon you can’t say without wincing, which is a good indicator it should be translated.
Empty adjectives, which sound much more obviously hollow spoken than written. This pass catches most of the phrases in resume clichés and what to write instead.

Read it to another person if you can. Explaining a bullet out loud often produces a better version of it on the spot — say the sentence you just said, and write that down.

Pass 5: the exported file

Everything above checked your source document. Now check what the employer receives.

Export it, close it, and reopen the exported file. Confirm it looks the way you expect, with no shifted lines or missing characters.
Check the filename. “Resume_v7_FINAL_reallyfinal.pdf” is a bad first impression. Use “Firstname-Lastname-Resume.pdf” — and never a filename containing another company’s name.
Check the document properties. Word processors record an author name and sometimes a title from the file’s original template. A resume whose metadata title reads “Free Modern Resume Template” is not fatal, but it’s a free fix.
Open it on your phone. A meaningful share of first looks happen on a phone. Text that requires zooming is text that gets skipped.
Confirm your contact details are visible in the exported version, particularly if they sit near the top edge — see the resume header, done right for why they should be in the document body rather than a header region.
Click every link. A dead portfolio link costs you the exact thing it was there to prove.

Get one other pair of eyes

A second reader catches things no process will, and they don’t need to be a hiring expert. Ask for three specific things rather than “what do you think”:

“What do you think I do for a living, after reading this once?”
“Which line is the most confusing?”
“Is there anything here you’d want to ask me about?”

Those three questions produce actionable answers. “Looks good” does not.

Build in the delay

The single highest-return habit is not sending on the same day you finish writing. Draft it, close the file, come back tomorrow. Everything above works better on a document you’ve had a night away from — and the errors you’ll find are the ones that would have gone out otherwise.