What an ATS actually is
An applicant tracking system is a database with a parser bolted to the front. When you upload a file, it extracts text, guesses which chunks are your name, your employers and your dates, and writes those into fields a recruiter can filter on. That is the whole trick. It does not read for quality, it does not score your career, and in most configurations it does not reject anyone automatically.
That last point matters, because the internet is full of advice built on the opposite assumption. The realistic risk is not a robot deciding you are unqualified. It is a parser mangling your job titles so badly that a human filtering for “Product Manager” never sees you.
How parsing works
The parser reads your file in a linear order and looks for recognisable landmarks: section headings it knows, date patterns, email addresses, phone number shapes. Everything else it treats as body text belonging to whichever heading came last.
Reading order is not visual order
A two-column layout looks orderly to you and arrives as interleaved nonsense to a parser that reads left to right across the page. Your job title ends up glued to a skills list, and the date beside it belongs to a different role entirely.
Headings are the index
“Experience”, “Education” and “Skills” are recognised almost universally. “My journey”, “Where I have been” and “What I bring” are not. Creative headings do not read as personality here; they read as missing sections.
Four things that break it
In rough order of how much damage they do:
- Text inside images. A designed header graphic containing your name means the parser finds no name at all. This is the single most costly mistake and the easiest to avoid.
- Tables holding job history. Frequently flattened into one unreadable line, or dropped entirely depending on the parser.
- Contact details in the page header or footer. Many parsers skip those regions completely. Your email belongs in the body.
- Two-column layouts for the main content. Sometimes fine, sometimes catastrophic, and you cannot tell which system you are facing.
None of these make a resume look bad to a person. That is exactly why they survive so long — the failure is invisible from your side.
Keywords, honestly
Matching the language of the job ad genuinely helps, because a recruiter filtering the database searches with the words the ad used. If the ad says “content strategist” and your resume says “content lead”, you are not in that result set.
What does not work is stuffing. White text, hidden keyword blocks and a wall of comma-separated skills are detected by most modern systems and, more importantly, read as dishonest by the human who opens the file next. Match the wording where it describes work you have actually done. Where it does not, leave it out.
A short checklist
- Single column for everything a recruiter needs to read.
- Standard section headings, in a standard order.
- Real selectable text — no name, contact detail or job title locked inside a graphic.
- Dates in a consistent format, one range per role.
- Job titles that match the language of the ad where that is honest.
Run a finished file through the ATS checker against the specific ad before you send it. Most of what it flags takes two minutes to fix.
General information only, not professional advice. Placeholder article written for this build.