ATS Resume Checklist

File & Formatting 5 items

Save as .docx — most ATS systems parse Word files better than PDFs

Critical

No tables, columns or text boxes — ATS reads left-to-right, single column only

Critical

No headers or footers — contact info inside the body, not in Word header/footer areas

Standard fonts only — Calibri, Arial, or Georgia. No decorative fonts that may not render

No graphics, icons or logos — skill bars, profile photos, icons break parsing

Critical

Keywords & Match 5 items

Mirror the job title exactly — if the JD says "Product Manager", your resume should too

Critical

Include hard skills verbatim — copy exact tool/tech names from the job description

Spell out acronyms once — write "Search Engine Optimisation (SEO)" before using SEO alone

Skills section matches JD language — don't write "JS" if the job posting says "JavaScript"

Match seniority language — "led", "managed", "owned" for senior; "contributed", "supported" for junior

Tip

Bullet Points & Impact 5 items

Every bullet starts with an action verb — Built, Led, Increased, Reduced, Delivered. No "Responsible for"

Critical

At least one metric per role — numbers (%, $, users, time) make bullets scannable and memorable

3–5 bullets per role — quality over quantity. Cut anything vague or obvious

Tip

No personal pronouns — never write "I", "my", or "we" in bullet points

Name the technologies used — "Built REST API using Node.js and PostgreSQL" beats "Built REST API"

Structure & Red Flags 5 items

Section headers are standard — "Work Experience", "Education", "Skills". Not "My Journey" or "Expertise"

Critical

Dates are consistent — use one format throughout: "Jan 2022 – Mar 2024" or "2022–2024", not both

No "References available on request" — it's assumed. Wastes a line recruiters notice.

Tip

No objective statement — replace with a 2–3 line professional summary that leads with your strongest value

File name is professional — "FirstName-LastName-Resume.docx", not "resume_FINAL_v3_USE THIS.docx"