Writing a resume that survives ATS and human skim

A resume gets read twice — once by software, once by a human spending roughly six seconds on it — and it has to survive both passes to get anywhere near an interview at all.

Beginner

3 min read

Pass one: the applicant tracking system

Most mid-size and large companies route applications through an Applicant Tracking System (ATS) before a human ever sees them. It parses the document into structured fields and, often, ranks or filters candidates against keywords from the job description. This is why formatting choices that look fine to a human — text boxes, multi-column layouts, tables, headers/footers holding contact info, icons standing in for section titles — can actively break a resume: some parsers simply fail to extract text from them, and a name or an entire work-history section can silently vanish from what the system sees.

Practical implications:

Stick to a single-column layout with standard section headings ("Work Experience," "Education," "Skills") — an ATS is trained to recognize common headings, not creative ones.
Save and submit as the file type the application actually asks for (often PDF is fine and preserves formatting reliably; when in doubt, follow the posting's stated preference rather than guessing).
Mirror the language of the job posting where it's honestly true of your experience — if the posting says "REST APIs" and your resume says "web services," a simple keyword match can miss you even though you have the actual skill.

Pass two: a human skimming for seconds, not reading

Assume a recruiter or hiring manager is spending well under a minute on a first pass — eye-tracking research on resumes consistently finds this. That reality should shape the whole document:

The most important, most relevant information goes at the top of each section — not chronologically buried where a skim will miss it.
One page for most early- and mid-career candidates. A second page has to earn its place with genuinely relevant additional experience, not padding.
Bullet points, not paragraphs. A wall of prose doesn't get read at skim speed; a bulleted list of short, scannable lines does.

Writing a bullet that actually says something

The weakest bullets describe a responsibility with no outcome attached: "Responsible for the checkout flow." A stronger bullet follows action → what → impact:

Weak:   Responsible for the checkout flow.
Better: Rebuilt the checkout flow's validation logic, cutting failed
        submissions from ~9% to under 2% of attempts.

Not every bullet will have a clean metric, and a fabricated number is worse than none — but wherever a real number exists (a percentage, a time saved, a scale handled), it does more work than any adjective ever will. Where no metric genuinely applies, describing the concrete outcome ("...so the team could deploy without a manual QA pass") still beats describing the task alone.

Tailoring versus mass-blasting

Sending the identical resume to fifty postings is fast but weak — a resume tailored to the specific role's actual language and priorities, even with only 10–15 minutes of adjustment per application, consistently produces a higher response rate than volume alone. Tailoring here doesn't mean fabricating experience; it means choosing which true things about your background to lead with and how to phrase them, based on what a specific posting is actually asking for.

Writing a resume that survives ATS and human skim

A resume gets read twice — once by software, once by a human spending roughly six seconds on it — and it has to survive both passes to get anywhere near an interview at all.

Beginner

3 min read

Pass one: the applicant tracking system

Practical implications:

Stick to a single-column layout with standard section headings ("Work Experience," "Education," "Skills") — an ATS is trained to recognize common headings, not creative ones.
Save and submit as the file type the application actually asks for (often PDF is fine and preserves formatting reliably; when in doubt, follow the posting's stated preference rather than guessing).
Mirror the language of the job posting where it's honestly true of your experience — if the posting says "REST APIs" and your resume says "web services," a simple keyword match can miss you even though you have the actual skill.

Pass two: a human skimming for seconds, not reading

Assume a recruiter or hiring manager is spending well under a minute on a first pass — eye-tracking research on resumes consistently finds this. That reality should shape the whole document:

The most important, most relevant information goes at the top of each section — not chronologically buried where a skim will miss it.
One page for most early- and mid-career candidates. A second page has to earn its place with genuinely relevant additional experience, not padding.
Bullet points, not paragraphs. A wall of prose doesn't get read at skim speed; a bulleted list of short, scannable lines does.

Writing a bullet that actually says something

The weakest bullets describe a responsibility with no outcome attached: "Responsible for the checkout flow." A stronger bullet follows action → what → impact:

Weak:   Responsible for the checkout flow.
Better: Rebuilt the checkout flow's validation logic, cutting failed
        submissions from ~9% to under 2% of attempts.

Writing a resume that survives ATS and human skim

Pass one: the applicant tracking system

Pass two: a human skimming for seconds, not reading

Writing a bullet that actually says something

Tailoring versus mass-blasting

Further reading

Writing a resume that survives ATS and human skim

Pass one: the applicant tracking system

Pass two: a human skimming for seconds, not reading

Writing a bullet that actually says something

Tailoring versus mass-blasting

Further reading