How to Test Your Resume Before You Apply

Test one: does the text come out?

Export the file exactly as you would submit it, select everything, copy, and paste it into a plain text editor. This approximates the first thing any system does with your document, and it takes under two minutes.

• Something appeared at all — an empty paste means the file has no text layer.
• Your name is the first thing on the page.
• Your email address and phone number are present.
• Content reads top to bottom in the order a person would read it.
• Each job sits next to its own dates and employer.
• No stray symbols where bullets should be.
• Nothing from a sidebar is interleaved into a job description.

Any failure here is structural rather than editorial, and the causes are catalogued in our guide to why resumes get parsed wrong. Fix the cause and re-export before running anything else, because the remaining tests are meaningless on a document that does not extract.

Test two: does it match this posting?

This is the only test you repeat for every application. Paste the posting and your resume into our free ATS checker and read the list of terms present in one and absent in the other. The output to care about is the list, not the score.

Work down the gaps and sort them into three piles: terms you can genuinely evidence and should add, terms you have touched and can add with honest qualifying language, and terms you cannot claim. The third pile is left alone. If it is large, that is not a document problem — it is a signal that this posting may not be a good use of an application.

Test three: the first third

Cover everything below the top third of page one and read what remains as though you were a hiring manager who has never heard of you. You are looking for four answers, and they should arrive without effort.

If any answer is missing, the fix is usually sequencing rather than writing — the material exists, further down. Our guides to the summary line and quantifying achievements deal with the two components this test most often exposes.

Test four: print it

Print one copy, in black and white, on ordinary paper. This sounds antique and it remains the fastest way to see a document as an object rather than as a file you have been editing for weeks. Interviewers frequently print, and so does anyone reviewing on a train.

• Contrast. Light grey body text that looked elegant on a screen can be genuinely hard to read on paper, and colour headings become similar greys.
• Margins. Content running close to the edge may be clipped by the printer.
• The page break. A job split across two pages, or a page two containing four lines, is obvious on paper and invisible while scrolling.
• Density. Held at arm's length, a page should still show visible structure. If it is a uniform grey block, the sections are not separated enough.
• Length honesty. Two pages feels different in your hand than in a scroll view, and it is a good prompt for whether the second one earns itself.

Then look at it on a phone. Recruiters open attachments on phones constantly, and a layout that only works at full width is a real handicap. The template gallery is built with both of these in mind, which is one fewer thing to test if you start there.

Test five: a person who does not know your job

The final and most uncomfortable test. Hand your resume to someone outside your field, give them thirty seconds, take it away, and ask three questions: what does this person do, how senior are they, and what is the most impressive thing on the page.

You are not asking whether they liked it. You are checking whether the argument survives without any of the context in your head. Wrong or hesitant answers point at a specific fault: they could not name your job means the title or summary is unclear; they could not gauge seniority means scope is missing; they could not name an achievement means the numbers are buried inside sentences about responsibilities.

If you have nobody to ask, our free resume review performs a version of the same reading and returns what stands out and what does not. It is the only one of these five tests that assesses persuasion rather than mechanics, which is why it is worth doing last, on a document that already passes the other four.

How often to run them

Tests one, three, four and five belong to the document. Run them properly once when you build or substantially rewrite it, and again after any structural change — a new template, an added section, a converted file format. Test two belongs to the application and takes three minutes per role.

That split matters, because the common failure is to re-run the cheap test forever and never re-run the expensive ones. A person who has run a match check on forty applications and never once extracted their own text is optimising the surface of a document that may not survive being opened.

One thing none of these tests can tell you

Whether you should be applying for this role at all. A document can pass every check here and still be aimed at a job you have no credible claim to, and that is the most common reason applications fail. If you want a neutral view of what an occupation actually involves before you spend an evening tailoring, O*NET OnLine describes the tasks and typical requirements of each one, and the Purdue OWL job search documents section is a sensible non-commercial reference for the surrounding paperwork.

Once the document passes, stop testing it. Every further hour spent on a resume that already works is an hour not spent on the next application, and the second one has considerably better odds. Build it once in the resume builder, verify it properly, and then let it do its job.