What an ATS actually does with your résumé

Almost everything written about applicant tracking systems describes them as gatekeepers that throw résumés away. That is not what they do, and the misunderstanding leads people to optimise for the wrong thing.

Parsing comes first

Before a résumé is scored it has to be read. The system converts your file into structured fields: name, contact details, a list of roles, each with an employer, a title and a date range. Anything it cannot confidently map is dropped or misfiled.

This is where most damage happens. A two-column layout can interleave two unrelated roles. A job title placed inside a text box may never be extracted. Dates written only as years can collapse a three-year role into a blank.

Then keyword coverage

Once parsed, the text is compared against the posting. Recruiters search and filter on terms the posting itself uses. If a posting says strategic sourcing and your résumé says procurement strategy, a human reads those as the same thing and a keyword index does not.

The honest move is not to stuff the missing terms in. It is to use the posting's vocabulary where your experience genuinely supports it, and to leave the rest alone.

What to actually do

• Single column. Standard headings. Real text, never an image of text.
• Month and year on every role.
• Mirror the posting's wording only where the underlying experience is real.
• Check what the parser extracted, not just how the page looks.

A résumé that reads beautifully and parses badly will lose to a plainer one that parses cleanly.

That last point is the whole argument. Design for the reader that comes first.