ATS Resume Examples

It helps to know which elements survive extraction and which do not, because the failures are specific rather than general. Body text in a single column survives intact, and so does anything that is genuinely text: your name, your bullets, your dates, a URL written out in full. This is most of a well-built resume, which is why plain formats work so reliably.

Multi-column layouts are the first thing to break. A parser reading a page left to right across the full width produces alternating fragments of your sidebar and your job history, so a skills column beside an experience column becomes a shuffled mixture of both. A table is the same failure in miniature: the grid that made a skills matrix readable to you collapses into a run of words with no rows or columns left to give them meaning.

Text placed in a document header or footer region is frequently discarded outright, and this is the one that costs people interviews rather than points. Putting your name, email and phone number in the header of a Word document is a common and reasonable design choice, and it is also how a candidate becomes uncontactable in a database. Keep contact details in the first lines of the document body.

Icons and images carry no text at all. An envelope symbol beside an address leaves an address with no label, and a skill rendered as a five-star rating graphic leaves nothing whatsoever. A certification shown as a badge image is, to the system reading it, a certification you do not have.

An applicant tracking system is a database with a parser attached. It extracts text from your file, maps it into structured fields, and stores the result. A recruiter then searches and filters that database by skill, title, location or years of experience.

It follows that an ATS does not usually reject anyone. It is a filing system. What costs you the application is a recruiter running a search your record does not match, or your record being filed incorrectly because the file did not parse. Both are worth fixing and they are different problems: the first is a vocabulary problem, the second is a formatting one.

It also follows that no applicant tracking system shows candidates a score. There is no number inside Workday, Taleo or Greenhouse that an applicant can raise. Any ATS score you have been shown is a model of how well your resume matches a particular job, built by whoever showed it to you. That is a perfectly reasonable thing to build, as long as they say how it works.

Open your PDF, select all, copy, and paste it into a plain text editor. What you see there is roughly what a parser sees, and it is a better test than most tools because it has no opinion to sell you.

Check five things. Is the reading order right, or do columns interleave? Did your contact details survive, or were they in a header region? Are all the dates present, in one consistent format? Did the skills section become a readable list or an unpunctuated run of words? Are your links visible as addresses rather than as the word "portfolio"?

If that pasted text reads as a coherent document, the record built from it will be coherent too, and you can move on to whether it contains the right terms. If it does not, no amount of keyword work will help, because the keywords are landing in the wrong fields or not landing at all.

The most useful habit in this whole subject is refusing the choice. Maintain the plain version and a designed version of the same content, and send whichever suits the channel: the plain file to every application form, the designed one to a recruiter who emails you, to a referral, and into the interview loop where a person is definitely the reader.

Once the content is written, keeping both costs almost nothing. What it buys is the end of a false trade-off that a lot of advice on this subject is built on, between a resume that a machine can read and a resume a human wants to.