1. How an ATS actually works
An ATS ingests your PDF, converts it to text, splits it into sections, and matches it against the job description. It then ranks candidates using keyword overlap, seniority signals, and format-quality checks. Popular systems in 2026: Workday, Greenhouse, Lever, Ashby, iCIMS, Taleo, SmartRecruiters, and Recruitee.
- Text extraction runs first — if your resume is an image, you score zero.
- Section headers are parsed by name. 'Work Experience' works; 'My Journey' does not.
- Bullets under each role are matched against JD keywords, not the summary.
- Most systems reject or downrank tables, columns, and text inside images.
- LLM-augmented parsers (rolled out 2024-2025) understand context but still tokenize first.
2. LLM-augmented parsers in 2026
Workday, Greenhouse, and Ashby all added LLM re-ranking on top of classic keyword extraction between 2024 and 2026. The extraction layer still trips on the same format issues; the ranking layer now weighs impact wording higher than raw keyword count.
- Impact wording beats keyword count: 'reduced onboarding from 6 weeks to 2' > listing 'onboarding' three times.
- LLM rerankers penalize obvious keyword stuffing — hidden white text is detected on ingest.
- Semantic matching means synonyms count now ('JS' matches 'JavaScript'), but exact terms still rank higher.
3. Keywords: match the JD, don't stuff it
The JD is your keyword list. Take the exact tools, frameworks, and responsibilities and reflect them in your bullets where truthful. Keyword stuffing (a hidden white-on-white list) is detected by every modern ATS and gets you rejected.
- Read the JD twice. Highlight nouns (React, SQL, Figma) and verbs (led, shipped, owned).
- Use the exact terms — 'JavaScript' and 'JS' don't always match despite semantic layers.
- Include the term once in a bullet and once in a skills list. That's enough.
- Never hide keywords with white text or 1pt font. Every ingest catches this in 2026.
4. Format: what parses cleanly
Single-column, one page (or two for 8+ years), standard section names, PDF export with embedded fonts. Every Kairos template is built to these rules by default.
- Fonts: use widely-supported (Inter, Arial, Calibri, Helvetica). Avoid decorative fonts.
- No text inside images, logos, or icons that carry information.
- Section names: Summary, Experience, Education, Skills, Projects, Certifications.
- Dates: 'Jan 2023 - Present' beats '2023-now'.
- Margins: 0.5-1 inch on all sides. Tighter margins get cropped by some parsers.
5. Workday deep dive
Workday powers hiring at ~50% of Fortune 500 companies. Its parser is strict: it rebuilds your resume into a structured profile before a human sees it. If a field doesn't parse, the recruiter sees a blank.
- Workday auto-fills its application form from your uploaded resume. If parsing fails, you refill 40 fields.
- Job titles must exactly match its taxonomy. 'Sr. SWE II' becomes 'Senior Software Engineer II'.
- Skills are extracted as tags — put them in a Skills section, not sprinkled in bullets.
- Upload PDF, not DOCX. Workday's DOCX parser is measurably worse.
6. Greenhouse & Lever & Ashby
Startups and mid-market run on Greenhouse, Lever, and Ashby. All three lean on keyword matching plus recruiter-defined scorecards. Cleaner parsing than Workday, stricter human review after.
- Greenhouse tags candidates with 'sources' — a referral tag beats a cold applicant every time.
- Lever surfaces 'strong match' candidates first based on keyword density in the top third of your resume.
- Ashby weights recent experience heavily — your latest role's bullets are ~60% of the initial ranking.
7. iCIMS, Taleo, and the enterprise stack
iCIMS and Taleo (Oracle) are the legacy giants — banks, healthcare, government, and big-box retail. Parsers are older, less forgiving, and often reject decorative resumes outright.
- Assume plain text. If it looks great in Word's outline view, it will parse.
- Taleo often maps 'Skills' to a picklist. Use standard names ('Project Management' not 'PM Ninja').
- iCIMS forms are long. Save your data in a scratch doc; you'll paste it many times.
8. Skills taxonomies (ESCO, O*NET, LinkedIn Skills)
Modern parsers map your skills to standardized taxonomies before comparing to the JD. ESCO (EU), O*NET (US), and LinkedIn Skills are the big three. Using the taxonomy's exact spelling boosts match scores.
- Check LinkedIn Skills autocomplete — those are the canonical strings.
- Prefer 'Python' over 'Python 3.11'. Version numbers rarely match.
- 'Machine learning' beats 'ML'. Full form is always the canonical form in taxonomies.
9. Multilingual & Arabic CV parsing
MENA-region hiring often runs bilingual (Arabic + English) applications. Most Western ATSs mangle right-to-left text; regional ATSs (Bayt, Naukri, Tanqeeb) handle it better but still trip on mixed layouts.
- For MENA multinationals (Vodafone Egypt, Careem, Talabat): submit English resume with an Arabic name in the header.
- For local Arabic-first employers: submit a separate Arabic PDF. Never mix RTL and LTR in one column.
- Embed a Unicode Arabic font (Noto Sans Arabic). Default PDF fonts drop Arabic glyphs entirely.
- Kairos exports both languages with correct RTL flow and embedded fonts by default.
10. Screenshot and image-based resume traps
The single fastest way to score zero on any ATS: hand it an image. Canva 'download as image' is the top offender in 2026.
- Never export as JPG or PNG. Always PDF, always with text layer.
- Icons that carry information (a phone icon next to your number is fine; a 'skills' bar graph is not).
- Text inside a logo header disappears at parse time.
- Test your resume: open the PDF, try to select and copy your name. If you can't, the ATS can't either.
11. Resume for engineering vs design vs sales vs data
Standard rules apply everywhere, but the ordering and emphasis shifts by role.
- Engineering: Skills stack goes above Experience. GitHub / portfolio link in the header.
- Design: Portfolio URL is the #1 element. Experience can be terse — the work is elsewhere.
- Sales: Numbers in every bullet. Quota %, deal size, ramp time. Skip fluff.
- Data / ML: Certifications and tools matter more than for other roles. Kaggle rank if relevant.
12. Fresh grads vs 10-year veterans
The order of sections changes with career stage. Everything else stays the same.
- Fresh grad: Education above Experience. Include GPA if >3.5. List academic projects.
- 5-8 years: Experience above Education. Drop GPA. Trim internships to one line each.
- 10+ years: One-page still possible with tight editing. Drop early roles entirely.
- 20+ years: Two pages OK. Consolidate first decade into 'Earlier career' summary.
13. Career gaps & how to explain them
ATSs don't penalize gaps — they can't tell a gap from any other missing dates. Human reviewers do. State gaps briefly and move on.
- Add 'Career break — caregiving, 2022-2023' as an Experience entry. One line. Owns the gap.
- Freelance work counts as employment. Group under 'Freelance / Consulting' with a date range.
- Sabbaticals, health, layoffs — one factual line each. Never apologize.
- Interviews will ask. Prep a 30-second answer that ends with 'and I'm excited to be back'.
14. Common mistakes that tank your score
Even senior candidates lose to junior ones because of format errors. These are the top offenders we see when auditing resumes in the Kairos Resume Checker.
- Two-column layouts — half your text gets read as one long paragraph.
- Custom section headers ('Cool Stuff I Made') that the parser ignores.
- Text inside a header/footer of the PDF — often skipped entirely.
- Contact info as an image (screenshot from Canva).
- Missing dates or role titles — the parser can't build a timeline.
- Emoji in bullets — most parsers strip them and leave broken spacing.
15. The order that ranks best
For most roles: Contact → Summary → Experience → Skills → Education → Projects → Certifications. For fresh graduates, swap Education above Experience. For technical roles, Skills can move above Experience.
- Contact: name, email, phone, city, LinkedIn, portfolio. Never a full address.
- Summary: 3 lines max, or skip entirely. Bad summaries are worse than none.
- Experience: reverse chronological. One dense role beats three shallow ones.
- Skills: grouped ('Languages', 'Frameworks', 'Tools'). No bar graphs.
16. Reverse-engineering the job description
The JD is a scoring rubric written by the hiring manager. Read it as a rubric and rewrite your resume against it. This is the single highest-leverage move you can make per application.
- Copy the JD into a doc. Highlight every noun and every verb.
- Score each highlight: 5 = you've done it, 3 = adjacent experience, 0 = never touched.
- Rewrite bullets to surface every 4-5. Drop bullets that don't map to a JD term.
- Use Kairos Resume Analysis (ATS Check vs JD) to see the exact match score before submitting.
17. PDF vs DOCX vs plain text
PDF is safe for every modern ATS (Workday, Greenhouse, Lever, iCIMS). DOCX is safe but sometimes reformatted. Plain text is bulletproof but ugly for the human reviewer. Recommendation: PDF from Kairos (embedded fonts, single column).
- Some legacy Taleo instances still prefer DOCX. If explicitly requested, use it.
- Never submit a Google Docs share link. Export to PDF first.
- Test on Chromium's built-in PDF viewer — if it renders wrong there, ATSs will fail too.
18. Cover letters: still worth it?
Some ATSs don't parse them, but many hiring managers do read them. A 3-paragraph, JD-specific letter differentiates you at zero cost. Kairos generates one from your resume + the JD in one click.
- Paragraph 1: why this company, this role (specific — mention a product or metric).
- Paragraph 2: one story that maps directly to the JD's top requirement.
- Paragraph 3: what you want next + one concrete question. End with a signature.
19. Final pre-submit checklist
Run through this before every single submission.
- One column, PDF, ≤ 500 KB.
- Standard section names.
- Contact info is real text (not an image).
- At least 3 bullets per role, each starting with a verb.
- At least one quantified result per role.
- JD keywords appear naturally in your bullets.
- No spelling errors — read it out loud once.
- File named 'FirstName-LastName-Resume.pdf'.
- ATS Check on Kairos scores ≥ 75 vs the target JD.
20. Quick answers to common questions
Fast reference for the questions that come up in every application. Longer FAQ below.
- Photo? Not for US/UK/Canada. Standard in MENA and parts of Europe.
- Length? One page under 8 years. Two pages beyond.
- Colors? One accent is fine. More looks like a Canva template and parsers ignore color anyway.
- Font size? 10-11pt body, 12-14pt section headers.
- Links? Only if clickable in the PDF and lead to something worth clicking.
الأسئلة الشائعة
- Does font choice really matter?
- Yes — decorative fonts can fail text extraction. Stick to Inter, Arial, Calibri, or Helvetica. Kairos templates use safe fonts by default.
- Should I include a photo?
- Not for US, UK, or Canada. Standard practice in parts of Europe, MENA, and Asia. When in doubt, omit — a photo can never help an ATS score.
- How long should my resume be?
- One page for under 8 years of experience. Two pages beyond that. Never three unless you're an academic with a required CV format.
- What if I have gaps?
- State them briefly ('Career break — caregiving, 2022') under Experience. ATSs don't penalize gaps; unexplained gaps confuse human reviewers.
- PDF or DOCX?
- PDF, always, unless the employer explicitly requests DOCX. PDF with embedded fonts renders identically for every reviewer and parses cleanly in every modern ATS.
- Do keywords still matter with AI parsers?
- Yes. AI parsers add semantic matching on top of keyword extraction — they don't replace it. Exact JD terms still rank highest.
- Should I use a template from Canva?
- Only if you export a single-column, text-based PDF. Most Canva templates use two columns and text-in-image, both of which tank ATS scores.
- How many keywords is 'enough'?
- Cover ~70% of the JD's noun-phrases across your bullets and skills section. Above 80% starts looking stuffed.
- Should I use colors?
- One accent color is fine — parsers ignore color entirely. Multiple colors read as 'design portfolio' to humans, which hurts non-design roles.
- Does the file name matter?
- Yes for humans, not for parsers. 'FirstName-LastName-Resume.pdf' looks professional and is easy to find in a recruiter's downloads folder.
- What if the JD asks for skills I don't have?
- List the closest adjacent skill honestly, mention it in a bullet where you touched it, and interview for the gap. Never lie.
- Can I use Chat GPT to write my resume?
- As a first draft, yes. But rewrite every bullet in your own voice, add real numbers, and match the JD manually. Pure AI text is generic and reads that way.
- Should I list every job I've had?
- Everything from the last 10-15 years. Older roles can go into an 'Earlier career' one-liner. Fresh grads: include everything, even short internships.
- What about certifications?
- List them only if they're recognized in your field (AWS, PMP, CFA, GCP, Meta Blueprint). Skip 'Certificate of Attendance' from unknown providers.
- Do I need a LinkedIn URL on my resume?
- Yes. Customize the URL (linkedin.com/in/firstlast) and make sure the profile matches the resume story.
- Should the resume match my LinkedIn word-for-word?
- The story should match; the wording shouldn't. Recruiters cross-check, and identical text reads lazy.
- What's the ideal margin?
- 0.5-1 inch on all sides. Tighter than 0.5 gets cropped by some ATS previewers.
- Should I include volunteer work?
- Yes if it adds relevant skills or leadership experience. One line each, in a dedicated 'Volunteer' section below Experience.
- How often should I update my resume?
- Every 6 months, even if you're not looking. It's easier to update in small increments than to rebuild from scratch when you suddenly need it.
- What if my industry uses long CVs (academia, medicine)?
- Follow the industry standard — but still export as PDF with embedded fonts and use standard section names. ATS rules apply everywhere.
شروحات معمّقة
ستة أدلة مركزة بتتعمق أكتر في الأنظمة والمواقف اللي بتوقع أغلب السير الذاتية.
ATS deep dive · Workday
Workday ATS: The Complete 2026 Parsing Guide
How Workday parses, tags, and ranks resumes across ~50% of the Fortune 500 — with the exact format rules that pass its auto-fill and taxonomy layers.
اقرأ الدليلATS deep dive · Greenhouse
Greenhouse ATS: How Startup Hiring Actually Ranks You
Greenhouse powers most Series A–D hiring. Here's how its keyword matching, sourcing tags, and scorecards decide who gets the recruiter screen.
اقرأ الدليلATS deep dive · Lever
Lever ATS: Recency, Density, and the Strong Match Filter
Lever ranks candidates by recent-role keyword density. Here's how the 'Strong Match' filter works and how to rank at the top of a Lever pipeline.
اقرأ الدليلRegional guide · MENA
Arabic CV & Bilingual Resumes: The MENA Parsing Guide
How Western and regional ATSs handle Arabic and bilingual resumes — and the format rules that get you shortlisted at MENA multinationals from Cairo to Riyadh.
اقرأ الدليلCareer stage · Fresh graduates
The Fresh Graduate Resume: Get Past the ATS With Zero Experience
How to build an ATS-safe resume with no full-time experience — including which sections to lead with, how to write bullets from projects, and what to skip.
اقرأ الدليلKeyword strategy · 2026
Resume Keywords in 2026: What Ranks, What Gets You Rejected
Keyword strategy for modern LLM-augmented parsers: how to match a JD without stuffing, and the exact terms that rank in 2026.
اقرأ الدليل