RolespectFind the role. Get the Rolespect.
Field notes

The resume headings a scanner cannot read.

A scanner does not rank a bad resume low. It fails to read parts of it, files what it can, and never tells you what it dropped. Here is what goes missing, and a two minute test for your own file.

Companion episodeRun The Mission, out Thursday, 15 October

Run The Mission is Bradley's podcast from Wendling Nonprofit Consulting: nonprofit operations, with a job search series beside these notes. Every episode

What the scanner actually does. An applicant tracking system turns your file into text, sorts that text into fields like name, contact, experience, education and skills, and stores the fields. A recruiter then searches the fields. A section that never made it into a field is not scored low. It is simply not there when someone searches.

The heading nobody sees break

Designers love a letterspaced heading. It looks clean on the page: C O R E   C O M P E T E N C I E S. On screen it reads as two words.

Export that file and the letters come out as letters. The scanner reads sixteen one letter words where your heading should be. It cannot match that to Skills, so the section is never classified, and nothing under it gets indexed. Every competency you listed there is invisible to the search.

You will never get a message about this. The application goes through, the portal says received, and the part of your resume you worked hardest on is missing from the record. Nothing about your experience is wrong. The file just hid it. That also makes it one of the easiest things in a search to fix.

Five layouts that lose whole sections

Letterspacing is the sneaky one. These are the loud ones. Rolespect treats each of them as serious enough to stop and rebuild before you send.

1. Contact details in the header or footer

Most common

Many scanners skip the document header and footer. Put your name and email up there and the record can end up with no name and no way to reach you.

2. A table or grid

Order scrambles

Table cells are read in an order you did not choose. Dates come loose from employers, and titles end up under the wrong job.

3. Two columns

Lines interleave

Many scanners read straight across the page. A skills sidebar next to your experience becomes one line of each, woven together into nonsense.

4. Text boxes, shapes and sidebars

Often skipped

Text inside a box is frequently skipped in full. If the box holds your summary, the summary is gone.

5. Skills shown as a chart or bar

Not text at all

Nothing inside an image is text. A bar that shows ninety percent in budgeting says nothing to a system that reads words.

Two more are softer. A custom section name like Where I Have Worked may not be classified, because scanners look for Experience, Education and Skills. And a photo or logo in the file adds parse risk, plus a screening risk in the United States that you do not need.

Check your own in two minutes

You do not need a tool for the first pass. You need the text the scanner will see.

  1. Open the exact file you send, the PDF or the Word document.
  2. Select everything and copy it.
  3. Paste it into a plain text editor. Notepad on Windows, TextEdit in plain text mode on a Mac.
  4. Read it top to bottom as if you were the machine.

What you should see:

  • Your name, email and phone near the top, as plain text.
  • Every section heading as a normal word you could search for.
  • Each job title sitting next to its employer and its dates.
  • Four digit years on every job. Date ranges are how a system builds your timeline.
  • No long runs of spaces, no lines that run on for a paragraph with no punctuation, no boxes or strange symbols where your bullets were.

If any of that fails, the scanner sees the same failure. Fix the layout, not the words. One column, headings typed as plain words, contact details in the body, plain round bullets.

Why there is no score out of a hundred

You have seen the sites that grade your resume against a posting and hand back a number. No applicant tracking system produces that number. Each system parses differently, and recruiters search in their own ways. A score out of a hundred is a guess dressed as a measurement.

Rolespect checks two things it can actually know. First, can the text be read: contact details found, sections recognizable, years present, no spaced headings, no signs of a collapsed table. Second, are the posting's required lines on your page, in words a search would match. Each required line is marked covered, partial or absent, and you see their phrasing next to yours. An absent line is a search you will never appear in.

When the layout is the problem, Apply can print a clean copy. It rebuilds the document and never the sentences. Every word survives as you wrote it. Spaced headings are collapsed, section names are set to the ones scanners classify, the contact block moves into the body, and the whole thing becomes one column with plain bullets. What it will not do is rewrite a line of your experience. What it does not do is written out here.

What this will not tell you

  • Which system the employer runs. They differ, and some parse better than others. A file that passes the plain text test is safe in all of them. A file that fails is a gamble in most.
  • Whether a person reads it. A clean parse gets you into the search. It does not get you the interview. The words on the page still have to answer the posting.
  • Anything about design for a human reader. Some roles, in design and marketing, reward a visual resume. Keep that version for the portfolio link and the hand delivered copy, and send the plain one through the portal.

Run the paste test on the file you sent last. If the heading you were proudest of comes out as sixteen letters, you have found at least one reason the portal went quiet.

Run it

Check the resume before you send it.

Rolespect reads your resume the way a scanner does, names every parse defect, and checks the posting's required lines against your own words. It never rewrites them. Free, no account, and nothing you enter leaves the device.