Your ATS Can't Read Arabic — and GCC Employers Are Paying the Price

An analysis of 840,000 Arabic resumes found a 48% ATS pass rate — thirteen points below the global average. On Oracle Taleo and SAP SuccessFactors, 34% of Arabic CVs lose critical data before a recruiter ever sees them. The cause isn't a talent shortage. It's a parsing problem built into systems designed for English-first markets. In this episode, we break down the five technical root causes: RTL text rendering, Arabic morphological complexity, diacritics ambiguity, dialect variance across Gulf and Levantine Arabic, and code-switching between scripts mid-sentence. These aren't edge cases — they're systematic failures that compound at every stage of the hiring funnel. The stakes are rising fast. The UAE mandates 10% Emirati staff by end of 2026, with fines up to AED 108,000 for non-compliance. Saudi Arabia's Nitaqat system restricts expatriate hiring for companies that miss nationalization quotas. Every Arabic CV your ATS misparses is a potential compliance gap. We also look at what's emerging to fix it — MENA-native platforms like Talentera and Evalufy, and how OVI's Sora and Milo agents were built to handle the bilingual and compliance-heavy reality of GCC hiring. If your rejection data shows unexplained gaps in Arabic-language candidate performance, this episode is for you.