26 direct answers to the most-searched questions about applicant tracking systems, resume optimization, keyword strategy, and AI-written resumes in 2026. No marketing fluff.
Yes, but parsing accuracy varies. Workday, Greenhouse, and Lever can read most text-based PDFs cleanly. Image-rendered PDFs (scanned resumes, designer-exported PDFs with rasterised text) often fail to parse — the ATS sees blank pages. Test your PDF by copy-pasting from it; if the text comes out scrambled, your ATS will see scrambled text too. DOCX is the safer default in 2026.
Keyword stuffing means repeating JD keywords beyond what's natural — for example, putting 'Python developer Python engineer Python expert Python coder' in your skills section. Modern ATS in 2026 detect this via n-gram repetition checks and BERT-based semantic outlier detection. Stuffed resumes either get flagged for human review (bad if no recruiter checks) or auto-rejected outright.
Workday parses resumes into structured fields using a combination of rule-based extractors (regex for emails, phone numbers, dates) and a trained NER model for skills and job titles. The parsed structure is then matched against the JD's required-skills list with TF-IDF and embedding-similarity scores. Workday weights the SKILLS section higher than narrative paragraphs.
Google uses Avature for general roles and an internal system (sometimes called gHire) for engineering. Both are less keyword-aggressive than Workday — they rely more on human recruiter screening. But Google's volume is so high that a recruiter still spends 6-15 seconds per resume, so the same scannability principles apply.
Two-column resume layouts are a known parsing failure mode for several ATS (Taleo, older iCIMS configs). The parser reads left-to-right and merges the two columns into one stream, scrambling section order. Single-column layouts are the safe default. Tables for ranges (Jan 2020 — Mar 2022) usually parse fine; tables for whole sections do not.
One page if you have under 8 years of experience; two pages if you have more. Three+ pages for academic CVs and very senior roles only. ATS doesn't care about page count, but human recruiters skim — anything past page 2 has near-zero read probability for most roles.
Inter, Calibri, Arial, Helvetica, or Georgia. Avoid display fonts (Pacifico, Lobster, anything 'designer'), light weights, and embedded webfonts that aren't in the parser's font table. 10-11pt body, 14-18pt headings.
Not for US, UK, Canadian, or Australian roles — anti-bias regulations and recruiter convention reject photo'd resumes. Continental Europe (especially Germany) historically expected photos but is moving away. Asian markets remain mixed. When in doubt, skip the photo.
No. They were useful when resumes were career-shifts focused; today, the JD-targeted summary or 'Profile' paragraph replaces them. A four-line summary stating your level, two specialisations, and most-recent impact is what every modern template puts first.
In the US, a resume is 1-2 pages and tailored per role; a CV is the longer academic document with publications, talks, and full work history. In the UK, India, and most of Europe, 'CV' is used for what Americans call a resume — 1-2 pages, targeted. Match the regional convention of the company you're applying to.
Companies vary. FAANG and most large companies cross-check; discrepancies between LinkedIn and resume — different titles, different dates — get flagged. They don't need to be identical, but the rough shape (titles, employers, approximate dates) should align. Tailor the resume; keep LinkedIn as the canonical truth.
Three signals matter: (1) explicit timezone availability near the contact info, (2) async-collaboration evidence ('led 8-engineer distributed team across 4 timezones'), and (3) prior remote experience listed clearly per role ('Acme Corp, fully remote, 2020-2024'). Remote-job ATS queries filter for these literal phrases.
AI is great for *rewriting* sections you've already drafted; less good for generating from scratch. Recruiters in 2026 spot ChatGPT's signature phrases (utilised, leveraged, spearheaded, em-dashes) within seconds. Use AI as a sparring partner: write your bullet, ask it to sharpen, then rewrite in your own voice. Local LLMs (Llama-3.1) produce less homogenous output than ChatGPT.
Match the top 15-20 keywords from the specific JD; aim for 65-85% coverage. Beyond that you're keyword-stuffing. Track the rank order of keywords in the JD (first-mentioned = most important to the hiring manager) and mirror that ordering in your skills section.
Sparingly. One accent colour for headings or section dividers is fine. Background colours, coloured body text, and rainbow skill bars look amateur. Black-on-white text with one optional accent (navy, dark green, deep red) parses cleanly and prints well.
Reverse-chronological with: (1) 3-line profile summary, (2) experience with outcome-bullets (cut p99 from X to Y), (3) skills ordered by JD-relevance, not alphabetical, (4) education last for ICs with 5+ years experience. Skip 'objective', 'references available on request', and exhaustive certifications. DOCX format.
Mixed. High-volume engineering at FAANG: rarely. Senior IC and design roles: often. Mission-driven orgs (non-profit, edu, gov): consistently. Small companies (under 50 employees): always. When unsure, write one — the cost is 20 minutes; the upside on the 30% of orgs that read them is significant.
List them only when they're either (a) directly required by the JD ('AWS Solutions Architect required'), or (b) evidence of recent relevant learning (a 2025 cert is more useful than a 2018 one). Buried bottom of resume in a compact 'Certifications' line. Don't waste a full section on a single Coursera certificate.
Compress older roles. Years 0-3: title, company, dates only. Years 4-10: title, company, dates, 1-2 bullets. Most-recent 3 years: title, company, dates, 4-5 outcome bullets. Recruiters skim recent first; depth before breadth communicates seniority.
Most common causes (in order): (1) keyword match too low — use a free match-score tool to check, (2) PDF rendering issues — open it after upload to confirm parsing, (3) experience-level mismatch — applying to senior with junior framing, (4) location filter — many ATS auto-reject out-of-region candidates, (5) gap years not addressed explicitly.
Five concrete things: (1) text-extractable PDF or DOCX, (2) standard section headings ('Experience', not 'My Journey'), (3) single-column layout, (4) no embedded images for skills/headers, (5) skills explicitly listed in a dedicated 'Skills' or 'Technical Skills' section. Beyond those, 'ATS-friendly' is mostly marketing fluff.
Honestly and concisely. 'Career break, March 2023 – January 2024 — caregiver responsibilities, returned full-time.' Or 'Sabbatical, Jul 2022 – Feb 2023 — open-source contributions, see github.com/...'. Recruiters increasingly expect non-linear careers; what they reject is unexplained gaps.
Yes for the top 5-10 roles you actually want; no for the rest. Use a base template and rewrite the summary + skills section per JD; the experience bullets stay mostly stable. A tailored resume on average matches 40-50% better than a generic one — the question is whether the time investment fits your application volume.
Hard skills are verifiable technical competencies (Python, Kubernetes, financial modelling). Soft skills are behavioural traits (leadership, communication). ATS systems weight hard skills 5-10× higher because they match deterministically. List soft skills only when the JD explicitly demands them, and back each with a concrete example bullet, not as standalone words.
Some tools claim to (Originality.ai, GPTZero) but reliably detecting LLM-written prose remains an open problem. What ATS *can* detect is the homogeneity that emerges when everyone uses the same model: identical phrasing patterns across thousands of resumes look like a template. Variety in your phrasing matters more than 'beating' detection.
75-90% is the sweet spot. Below 60% suggests the role is a stretch or your resume needs tailoring. Above 90% looks suspiciously over-optimised — recruiters notice when every bullet contains JD vocab. Aim for the band that signals fit without signalling keyword-stuffing.