How ATS checkers work — and what to fix first

ATS stands for Applicant Tracking System — the software behind most career pages and recruiter inboxes. When you apply through Workday, Greenhouse, Lever, Taleo, SuccessFactors, or a company careers site, your resume is usually parsed into structured fields before a recruiter reads it. Titles, dates, skills, and bullets become searchable rows. Fancy columns, icons, and text-in-images often do not.

Structure: clear section headers (Experience, Education, Skills), consistent dates, and a single-column layout parsers can read top to bottom. Tables, multi-column designs, and graphics often scramble field extraction — your years of experience can land in the skills bucket or disappear.

Keywords: role-relevant terms that appear in your summary, skills, and bullets — tools, methods, and domain language employers search for. Stuffing a keyword cloud at the bottom rarely helps; recruiters and modern filters reward terms grounded in real work.

Impact and clarity: action verbs plus outcomes beat duty lists. "Responsible for reporting" parses, but "Built a weekly pipeline that cut reporting from 6 hours to 2" ranks and reads. Length matters too — for most corporate lanes, a tight one- or two-page dossier with 3–5 bullets per recent role beats a five-page archive.

Keep these two scores separate. An ATS strength check is job-agnostic: is your master CV readable and generally competitive? A match score is job-specific: does this profile cover this posting's requirements and missing keywords?

When you run match score against one posting, treat the output as a triage list — not a homework assignment to add every missing word. Start with missing skill keywords: tools and methods the JD names that do not appear in your skills row, summary, or bullets. Those usually move the score and the recruiter search. Soft phrases like "fast-paced environment" or "team player" are noise — skip them even if they show as unmatched.

Next, check where coverage should live. If Python is missing and you used it last year, put it in Skills and one bullet that shows scale ("Built ETL jobs in Python processing [X] records/day"). If the gap is a framework you only touched in a tutorial, leave it out — interviews will expose empty keywords. Language requirements are different: if the role lists Japanese or Bahasa and you speak them, add spoken languages under Profile so match accuracy reflects that signal.

Your skills row is the densest ATS field on the page. Aim for 8–14 terms for early-career and intern lanes, 10–18 for mid-level — enough coverage without a taxonomy dump. Order by the job you want this week: required tools first, then strong secondary skills, then domain language (SQL before "Microsoft Office" if you are targeting analytics).

Revise in three passes. 1) Cut: duplicates ("JS" and "JavaScript"), outdated stacks you cannot defend, and filler ("hard-working", "MS Word" unless the posting asks). 2) Align: copy the employer's spelling and casing for must-have tools when you truly have them — "React" not "react.js", "PostgreSQL" not "Postgres" if the JD uses the full name. 3) Prove: every skill you keep should appear in a bullet, project, or coursework line somewhere else on the resume so a human can verify it in thirty seconds.

Upload or refresh your master profile, run an ATS strength check, and clear the top structure and clarity suggestions. Open the role (or paste the JD), read the match gaps, revise the skill list and two bullets, re-score once, then apply and mark applied in your pipeline.

That sequence — parse-ready CV, job-specific coverage, honest skill revision, then submit — is what "pass the ATS" actually means in practice. The checker is a rehearsal for the filter; the interview still rewards the story behind the bullets.