How ATS systems are fooled by Arabic CVs — and what I did about it
Applicant tracking systems read text, not design. I built a clean table-free, image-free version alongside the visual one — because the two jobs are different.
The first paradox of Arabic CVs: the most beautifully designed ones are often the least visible to applicant tracking systems. The system does not see the design, it sees extracted text. Every beautiful visual element can become noise in that extraction.
What breaks extraction
- Tables: a pretty CV layout is usually a two-column table. Extraction reads cell by cell, so "2025 · National University · B.Sc." comes out in an order nobody can parse.
- Images and text inside images: anything inside an image simply does not exist for the ATS. Your name in a drawn logo is a missing name.
- Decorative characters: dividers, arrows and ornamental symbols arrive as random characters in the extracted text.
- Arabic and English in one line: bidirectional (BiDi) results in extracted text come out reversed or fragmented.
The decision: two files, not one
The two jobs are completely different: a human reads design in seconds, and a system needs clean linear text. So I built two versions:
- The visual version: for printing and for holding in an interview — columns, colour and icons.
- The ATS version: no tables, no images, one heading per section, full textual dates and plain-text links.
Rules that hold for any Arabic CV
- Never place a meaningful fact inside an image or a logo.
- Write dates as month + year in text, not digits alone.
- Name every section without ornaments: "Experience", not "◆ Experience ◆".
- Do not mix Arabic and English in the same line; keep them in separate paragraphs.
- Keep a plain-text version and publish it alongside the pretty one, not instead of it.
What I have not done yet
I have not tested the version against one specific named ATS. The real test is submitting and tracking the result, and I will document that in a later note once real data exists. Until then, the rules above follow from how extraction works, not from a general compatibility claim.