What the ATS Actually Does

The ATS doesn't read your resume. It parses it.

Here's what that means in practice: when you hit "submit," the software strips every piece of formatting from your document — images, columns, tables, icons, colors, boxes. It then tries to extract your name, email, phone, job titles, companies, dates, and skills and map them into structured fields in a database.

That database is what the recruiter searches. They are not reading your resume. They are searching a database of extracted resume data — like searching Google, not reading a webpage.

The ATS scoring sequence:

  1. Parse — Break your resume into sections. Identify name, contact, experience, education, skills.
  2. Index — Store extracted text in searchable fields.
  3. Match — Compare your indexed keywords against the job description requirements.
  4. Score — Assign a relevance score. Rank you against all other applicants.
  5. Filter — Recruiter searches the ranked results. If you're not in the top 50, you don't get seen.

What actually causes auto-rejection:

Format Issue What Happens
Tables and text boxes ATS reads left-to-right across the page, ignoring borders. A two-column resume becomes a scrambled sentence.
Headers and footers with contact info Most ATS systems skip headers and footers entirely. Your contact info may not be extracted at all.
Non-standard section headers My Journey, Career Highlights — ATS cannot categorize these. Use Work Experience, Education, Skills.
Image-based headers or headshots ATS cannot read images. A logo or headshot in your header means the system sees no name.
Ligatures in fonts (fi, fl, ff) Some ATS parsers misread these as different letters entirely. Turn off ligatures in your Word font settings before saving.
Scanned PDFs A scanned PDF is an image file to the ATS. It cannot read it. You're submitting a blank page.
Inconsistent date formats Mixing Mar 2023, 03/2023, March 2023, and 2023 causes parsing errors that can miscalculate employment duration.

File format rule: Submit .docx unless the posting specifies otherwise. Older ATS systems (Taleo, some BrassRing instances) still choke on PDFs.

What I Look at in the First 7 Seconds

The eye-tracking research (Ladders, 2018; InterviewPal, 2025) is consistent: the initial scan is 6–11 seconds. Here's my actual scan path — and I know this because I've timed myself doing it.

The eye path:

  1. Name and headline — I look for your current title and the target role. If those don't appear in the first two lines, I lose you.
  2. Current and previous companies — Are these recognizable brands? Relevant sectors? Steady progression or unexplained gaps?
  3. Dates — How long at each role? Job-hopping is the fastest disqualifier for senior candidates.
  4. Skills block — If I can't find a clean list of hard skills in the top third of the page, the resume gets harder to evaluate and harder to pass to a hiring manager.
  5. First bullet point under current role — This tells me more than any summary ever could. If it's a responsibility list (responsible for, managed, oversaw), I already know what kind of candidate this is.

"The first three bullets under your current role are the most expensive real estate on your entire resume. Most people waste it."

— Kim Taynor

What earns a callback:

  • Metric-based achievements in the top third of the page. Not "led sales team" — "grew ARR by $4M in 18 months."
  • Exact keywords from the job description — including the job title. If the role says "VP of Operations," and your resume says "Head of Operations," you're one word away from being unfindable.
  • Clean structure — section headers I can read in one second. I should not have to hunt for your experience.

What kills it in 7 seconds:

  • Cluttered layout with no white space
  • Inconsistencies in font, bullet style, or date format that signal carelessness
  • Long paragraphs instead of scannable bullets
  • A summary section that says nothing ("Experienced professional with proven track record of excellence")

The 5 Resume Patterns That Get Qualified Executives Auto-Filtered

These are the five I see most often in otherwise highly qualified candidates. Every one of them is fixable.

Pattern 1: The Two-Column Layout

Why it fails

ATS reads left-to-right across the page, ignoring column borders. Your left-column job title and right-column company name get read as one garbled phrase. ATS may drop or misplace entire job entries.

Before

Two-column template with skills in a sidebar and experience in the main column.

After

Single-column layout. Skills block at the top in plain text. Experience below with standard bullet points.

Pattern 2: Contact Info in the Header

Why it fails

Most ATS platforms skip the header layer entirely. Your email, phone, and LinkedIn URL may not be extracted at all.

Before

Name and contact info in the Word document header. Content starts on page 1.

After

Name and contact details as plain text at the very top of the document body. No header or footer content.

Pattern 3: Non-Standard Section Headers

Why it fails

ATS maps your content to database fields. "Work Experience" = indexable. "My Career Story" = ignored. Your entire professional background may go unindexed.

Before

"Professional Background," "Career Narrative," "My Journey," "What I've Achieved"

After

"Work Experience," "Education," "Skills," "Certifications"

Pattern 4: Responsibility-Based Bullets Instead of Achievement-Based Bullets

Why it fails

For senior roles, responsibility lists are noise. They tell me what the job entailed, not what you actually did. A recruiter evaluating 200 resumes is looking for signal — and signal is a result.

Before

"Responsible for managing a team of 12 and overseeing P&L for the western region."

After

"Led cross-functional team of 12 to restructure western region P&L, delivering $2.1M in cost savings in year one without headcount reduction."

Pattern 5: No Keywords from the Job Description

Why it fails

ATS scores on keyword match. If your resume doesn't contain the exact terminology from the job posting — including specific tools, certifications, and role titles — you're scored low and buried in the search results before a human looks.

Before

"Strong communication skills and experience with project management."

After

"PMP-certified Project Manager with 8 years of Agile/Scrum experience, including Jira and Confluence workflow design for cross-functional engineering teams."

What a Callback-Worthy Executive Resume Actually Looks Like

After screening thousands of executive resumes, here's the structure that consistently earns the callback:

Top third of page 1 (the decision zone)

  • Name + phone + email + city/state + LinkedIn (plain text, no header)
  • Professional headline that mirrors the job title
  • A 3–4 line executive summary: what you do, who you've done it for, the scale of your impact. No buzzwords.
  • Skills block: hard skills only, matching the job description terminology exactly

Experience section

  • Each role: Company name, your title, dates
  • 3–4 bullets per role, in this order: achievement first, scope second, specific methods/tools third
  • Every bullet starts with a past-tense action verb
  • Quantify everything: revenue figures, team sizes, percentage improvements, timeline
  • No responsibility lists — ever

Education and certifications

  • Bottom of page 2. No degrees below bachelor's unless it's a hard requirement.
  • Certifications listed with full names (PMP, not "Project Management Professional Certified")

The one thing that separates a callback resume from a discard pile: Every word on that first page was chosen because it matches what the hiring manager is searching for. Not what sounds impressive — what is literally indexed in their ATS.