Do typos on your resume actually cost you interviews?

Did a signed AI pledge really misspell the United States?

Yes. On 29 September 2026, a signed document titled White House Accord on Super Intelligence: Joint Commitment on Frontier Responsibilities went public with the line President of the Unites States printed beneath the presidential signature — one letter swapped, a D traded for an S, in four of the most familiar words in American public life. The pledge itself is a voluntary promise by frontier AI labs to add internal controls during training and deployment, an internal team empowered to check them, an independent external auditor and a board-level oversight committee. It was signed alongside the chief executives of Google, Anthropic, Meta, OpenAI, Nvidia and xAI. Every company name on the page was spelled correctly.

Think about how many pairs of eyes that page passed through. Government lawyers, communications staff, six corporate legal teams, the most heavily lawyered companies in technology — and a document built to reassure the public about careful oversight went out with a typo in its own signature block. Reporters spotted it within hours of the photo being posted, and the error travelled further than the policy did. That's the part worth sitting with. Nobody argued the misspelling meant the commitments were worthless. They just stopped reading the commitments and started talking about the mistake instead. Attention is a limited resource, and a visible error spends all of it.

Your CV faces the same mechanic with none of the protection. The pledge survived its typo because everyone already knew who signed it and why it mattered. You don't get that. A stranger opens your file for a few seconds, having never heard your name, holding forty other files, looking for a reason to move you to the no pile. In that setting a spelling error isn't a small blemish on an established reputation — it's one of the very few data points the reader has about how you work. The rest of this article is about which errors actually cost you, and which ones don't.

Do typos on a resume matter, or is that just scare talk?

They matter, though not as uniformly as the internet claims. Surveys of hiring managers repeatedly find that a majority would set a CV aside over a spelling or grammar error, with reported shares ranging from roughly 40% to nearly 80% depending on who ran the poll and how the question was worded. Treat those numbers as directional rather than precise: most trace back to a handful of recruitment-vendor and job-board surveys that get recycled across statistics roundups without published methodology or sample sizes. What's consistent across all of them is the direction, not the decimal. Recruiters read errors as a proxy for care, and care is exactly what they're trying to infer in the time they have.

The mechanism is elimination, not evaluation. Early screening isn't a search for the best candidate; it's a fast cull of a stack down to a shortlist, and an often-cited eye-tracking study put the initial scan at around seven seconds per CV. In seven seconds nobody is weighing your delivery record against a misplaced apostrophe. They're pattern-matching: does this look like someone who does the job, and does anything here give me permission to stop? A typo in a place the eye lands — your name line, your current title, your headline bullet — hands over that permission for free. A typo buried in the third bullet of a 2019 role usually doesn't.

Here's the opinion I'll defend: the job-search world is far too anxious about typos and far too relaxed about everything else. A stray comma has never beaten a CV that proves impact. I've seen error-free documents rejected in seconds because every bullet described duties instead of results, and I've seen a genuinely strong engineering CV with two misspellings go straight to interview. Errors cost you when they cluster — three or four across one page reads as indifference — or when they land in a field that carries machine-readable meaning. Chasing a perfect comma while your bullets say responsible for is optimising the wrong thing entirely.

Which typos on a CV actually get you rejected?

The expensive typos are the ones in structured fields, not prose. Your email address, phone number, job titles, employer names, dates and skill keywords all get read twice — once by a human forming a judgement and once by software matching text to a requisition. A typo in prose costs you a little goodwill. A typo in a field costs you the application outright, silently, with no rejection email to tell you why. Applicants who go months without a callback sometimes discover the cause is a transposed digit in a phone number or a missing letter in a domain name that has been quietly bouncing every reply since March.

Skill keywords deserve special attention because that's where automated screening bites. Recruiters filter and search on exact terms — Kubernetes, PostgreSQL, Salesforce, Xero, HubSpot, SolidWorks, ISO 13485. Write Kubernets, Postgress or Sales Force and a keyword search simply doesn't return you, no matter how much of the work you've actually done. The same applies to certifications and licence names: AWS Solutions Architect, CIPD, PMP, CompTIA Security+, RN licence numbers. These are proper nouns with one correct spelling, and a recruiter skimming a shortlist will read a mangled tool name as someone who hasn't really used the tool. That inference is unfair and completely predictable.

The single most common damaging error isn't a misspelling at all — it's a leftover. You tailored your CV or cover letter for one employer, reused the file, and the previous company's name or the wrong job title stayed in. Spellcheck will never flag it, because every word is spelled correctly. Recruiters see this constantly and it reads worse than a typo: it says you're sending the same document everywhere and didn't look before hitting send. If you tailor your CV per application, and you should, the company and role line is the first thing to verify and the last thing to trust.

Why does spellcheck miss the typos that matter most?

Spellcheck only catches strings that aren't words. It cannot catch a correctly spelled word in the wrong place, and that's the category that does the damage. Manager becomes manger. Public becomes pubic. Led becomes lead, then becomes led again in the next bullet. Assistant becomes assistant to a different noun entirely. Your, you're, their, there, its, it's — all valid English, all invisible to a basic checker, all instantly visible to a human reader. Add homophone pairs that change meaning in a professional context — principal versus principle, complement versus compliment, discrete versus discreet — and you have a set of errors that survive every automated pass and then land squarely in front of the person deciding.

Formatting hides errors just as effectively. Text inside headers, footers, text boxes, tables, shapes and images often falls outside what the spellchecker examines, and those are exactly the places designed templates put your name, contact details and section titles. A CV built in a design tool can push half its content into elements the checker never reads. The same structures break extraction when a parser converts your file to plain text, so a decorative layout can simultaneously conceal your typos from you and scramble your details for the machine. If your CV came from a two-column template, assume nothing in the sidebar has been proofed.

Then there's autocorrect, which introduces errors rather than catching them. Tool names get helpfully rewritten into real words, capitalisation gets normalised, and a correctly typed technical term ends up mangled by the very feature meant to help. Proper nouns are the weak point: your checker has no opinion about whether your previous employer is Bluestone or Blustone, so it stays silent either way. This is why a clean spellcheck report tells you almost nothing about whether your CV is clean. It confirms you typed real words. It says nothing about whether you typed the right ones in the places that count.

What's a five-minute resume proofreading checklist before you send?

Run five targeted passes, in this order, and you'll catch the errors that actually cost interviews. First, check the seven fields that carry consequences: your name, email, phone, city, current job title, the target role or company you've named anywhere in the document, and every employment date. Read them character by character, and send yourself a test email to the exact address on the page. Second, do a leftover hunt — search the file for the previous company's name and the previous job title you tailored for. Third, verify every tool, platform and certification name against how the vendor writes it. Those three passes take about three minutes and cover most real damage.

Fourth, change how the text looks so your eyes stop autocompleting. Copy everything into a plain-text editor: this strips your formatting, exposes anything trapped in text boxes or sidebars, and shows you roughly what a parser extracts from the file. It's the fastest layout sanity check there is, and if the result reads as jumbled fragments you have a structural problem that matters far more than any typo. Fifth, read the whole thing aloud, slowly. Reading aloud is the only reliable way to catch real-word errors and missing words, because your mouth trips where your eye glides. Reading the bullets bottom to top works too — it breaks the narrative your brain keeps supplying.

After the manual passes, get a second read that isn't yours. Upload the file for a free CV analysis and you'll get a score out of 100, five category scores including clarity and structure plus ATS compatibility, a visual layout analysis and your strengths — in other words, an outside read on whether the document is legible to both a person and a parser. Paste in the job description and the analysis also lists the skills you're missing for that specific role, which is usually a bigger gap than punctuation. If you want a dedicated parsing view, the ATS resume checker covers the formatting side. Proof the words yourself; let software check the structure.

Frequently asked questions