Every bilingual job seeker in MENA faces this question, and most answer it by habit rather than strategy: they send whichever CV they wrote first. The language of your CV is itself a signal, and the wrong one costs interviews before a human reads a word.
The decision rule
Match the language of the job posting. This resolves most cases. An English posting expects an English application, an Arabic posting expects Arabic, and overriding that expectation reads as either carelessness or a capability gap.
The judgment calls sit where the posting is bilingual or the employer's culture differs from its posting language:
- Government ministries and public entities (Saudi Arabia, Qatar, Kuwait especially): Arabic, even when an English posting exists. Internal circulation happens in Arabic.
- Semi-government and national champions: Arabic-first with an English version ready. Aramco, national banks, and telecoms operate bilingually but value Arabic fluency signals.
- Multinationals, tech, consulting, and most of the UAE private sector: English. An Arabic CV here may not parse in the company's global ATS at all.
- Family conglomerates: check the leadership and the posting; these vary the most.
- North African employers: French remains the business default in much of Morocco, Algeria, and Tunisia; Arabic for public sector; English increasingly for tech.
When you cannot decide: send both files in one application where the portal allows it, or default to the posting's language and mention bilingual fluency prominently.
An Arabic CV is not a translated English CV
The most common mistake is running an English CV through machine translation and reversing the alignment. A native Arabic CV differs structurally:
- Register: Modern Standard Arabic with professional vocabulary, not the literal calques translation tools produce. "Managed a team" has natural Arabic professional phrasing; machine output is instantly recognizable and reads as low effort.
- Direction and layout: true right-to-left formatting, including correctly mirrored dates, bullets, and margins. Numbers and Latin-script tool names (SAP, PMP, React) stay left-to-right inside RTL text; broken bidirectional text is the giveaway of a careless conversion.
- Dates: Gregorian is standard business practice region-wide; Saudi government contexts sometimes expect Hijri alongside. Write years explicitly rather than assuming.
- Personal information conventions: the nationality, status, and location fields covered in our ATS guide appear in both languages, phrased natively in each.
The ATS problem with Arabic CVs
Regional portals like Bayt parse Arabic properly. Many multinational ATS deployments do not; they mangle right-to-left text extraction or fail to match Arabic keywords against English job descriptions. Practical consequences: for multinationals, submit English even if you also attach Arabic; for regional portals and government systems, Arabic parses fine; and keep both versions as text-based files, never as scanned images, which fail in both languages.
Maintaining both without double work
Both versions should carry the same facts: identical dates, titles, and numbers, because discrepancies between your Arabic and English CVs look like dishonesty even when they are just drift. Update both when anything changes, and tailor both to each posting; a tailored English CV attached to a generic Arabic one undercuts the pair. This maintenance burden is exactly why most candidates let one version rot, and why keeping them synchronized is a real edge.
Yalliq maintains your CV in Arabic and English from one profile, tailors either version to a specific posting, and exports proper RTL PDFs, so both files stay current and consistent. Try it free.