Skip to content
All articles

Arabic or English CV in Saudi Arabia? The Rule That Decides

TrueSira team Published 10 min read اقرأ بالعربية

In Saudi Arabia the CV language question has a real answer, and it depends on who receives the file, not on how good your English is. Government entities and Jadarat-routed postings expect Arabic. Aramco, SABIC, stc, the banks and the giga-projects expect English. Everything in between is decided by one test: the language the job posting itself is written in.

Most advice on this hedges (“prepare both!”) because it is written for a global audience. That is not useful when you have one PDF and one submit button. Here is the rule, the employer-by-employer breakdown, and what actually happens to Arabic text inside an applicant tracking system.

Quick answer

  • Government, semi-government, municipalities, and postings through جدارات: Arabic primary.
  • Aramco, SABIC, Ma’aden, stc, banks, NEOM and the giga-project developers, and any multinational: English primary.
  • Everyone else (family businesses, SMEs, agencies, startups): match the language of the job posting, word for word. If the posting is bilingual, match the language of the requirements section.
  • Never send a side-by-side bilingual CV. Two columns is the layout that breaks parsers.
  • Keep both files ready, send one. The second one goes out only when asked.

For the full document strategy behind these choices, start with our Saudi CV guide; this post covers only the language decision.

What decides the language: the reader, not you

A CV language is a routing decision. It is chosen by whoever will read, file, and forward the document internally, and those people have a default working language they will not change for you.

That gives a clean test with three questions, in order:

  1. What language is the posting written in? This is the strongest single signal and it is right more often than any rule of thumb. If the requirements are listed in Arabic, apply in Arabic.
  2. Who owns the hiring process? A government HR department files in Arabic because its correspondence, approvals and archives are in Arabic. A multinational’s shared service center in Riyadh files in English because its global system is in English.
  3. Where does the file get uploaded? A portal whose interface, field labels and confirmation email are in English is telling you what its database expects.

When the three answers disagree, follow question one.

Employer type decision table

Employer typePrimary CVSecond file?Why
Ministries, government agencies, municipalitiesArabicEnglish only if requestedInternal correspondence, approvals and archiving run in Arabic
Postings routed through جداراتArabicNoThe platform, the announcement and the shortlist review are Arabic
Semi-government funds, authorities, commissionsArabic, with English terms in bracketsEnglish, ready to sendArabic governance layer, often English technical teams
Aramco, SABIC, Ma’aden, stc, Mobily, the banksEnglishArabic rarely neededEnglish application systems and English postings
NEOM, Red Sea Global, Qiddiya, Diriyah, ROSHNEnglishNoInternational hiring teams, English postings
Multinationals and consultanciesEnglishNoGlobal ATS instance, English-only screening
Family businesses and SMEsMatch the postingYes, keep bothOwner or office manager screens personally, in their own language
Startups and agenciesEnglish usually, match the postingNoFounder-led screening, English-heavy tooling
Recruitment agenciesBoth, sent as two filesYesThey forward to multiple clients with different defaults

The one place people get this wrong most often is the semi-government layer: authorities, commissions, funds and the newer regulatory bodies. Their technical teams run in English, their governance and HR run in Arabic, and the posting language flips depending on which team wrote it. Read the posting and follow it.

Does Arabic break ATS parsing?

This is the fear that makes people send English CVs to Arabic employers, and it is mostly misdirected.

Arabic script is not the problem. The systems used by large Saudi employers handle Unicode Arabic and right-to-left text. The problem is that Arabic CVs, far more often than English ones, are built in ways that break any parser regardless of language:

  • The bilingual two-column layout. Arabic on the right, English on the left. A parser reads in a linear order and produces interleaved nonsense: “مهندس مدني Civil Engineer 2019 شركة”.
  • Text inside tables and text boxes. A very common Arabic template pattern, and the single most reliable way to make content disappear.
  • Image-based PDFs. A CV designed in Word, printed, scanned, and saved as PDF has no text at all — just pixels. This happens more with Arabic documents because of font and layout worries.
  • Decorative Arabic fonts. Some display fonts embed characters in ways that extract as boxes or reversed letters.
  • Mixed digits. Arabic-Indic digits (٢٠٢٤) do not always match a date filter looking for 2024. Use Western digits 0-9 throughout, in both languages.

Fix those five and an Arabic CV parses about as well as an English one. Our ATS-safe CV rules apply to Arabic files unchanged: one column, standard section headings, real text, text-based PDF.

Weak: a two-column bilingual CV with a decorative header, Arabic on the right, English mirrored on the left, exported from a design tool.

Strong: two separate one-column PDFs, Sara-AlQahtani-CV-AR.pdf and Sara-AlQahtani-CV-EN.pdf, each with plain section headings, Western digits, and selectable text.

The bilingual file question: one file or two?

Three approaches exist. Only two of them are safe.

Two separate files (recommended). One Arabic PDF, one English PDF, same content, each a clean single column. Send the one the employer expects. Attach the second only if the posting asks for both, and name the files so a human can tell them apart at a glance.

One file, stacked (acceptable). Arabic pages first, then English pages, in one PDF. No side-by-side anything. Use this when an upload form allows exactly one attachment and you genuinely need both languages — recruitment agencies, for example. Cost: the file is now four pages, and the parser will index both language versions as one blob, which slightly dilutes keyword matching.

Side-by-side bilingual (never). Two columns per page, one language each. It looks impressive to a human holding paper and it is unreadable to every parser and awkward on a phone screen. Skip it.

How to handle terms, titles and names inside an Arabic CV

An Arabic CV is not an Arabic-only CV. The Saudi professional vocabulary is bilingual in practice, and your document should reflect that rather than fight it.

  • Job titles: Arabic first, English in brackets on first use. محلل بيانات (Data Analyst). Do this for your current title and each previous one.
  • Tools and technologies: keep in Latin script, always. Python, Power BI, SAP, Excel, AutoCAD. Nobody searches for بايثون in a CV database.
  • Certifications: keep the official name in Latin — PMP, CFA, CMA, SOCPA — and add an Arabic gloss only if the certificate is genuinely obscure.
  • Company names: the form the company uses. أرامكو السعودية, سابك, stc — stc writes itself in lowercase Latin and that is what a recruiter searches.
  • Universities: Arabic name, as officially registered. جامعة الملك سعود, جامعة الملك فهد للبترول والمعادن.
  • Section headings: the conventional ones — الملخص المهني، الخبرة العملية، التعليم، المهارات، الشهادات والدورات. Do not invent creative headings; parsers look for the standard ones.
  • Dates: Western digits, Gregorian months, and one consistent format. 03/2021 – 08/2024. If your certificate shows a Hijri date, convert it and note the Hijri year in brackets if it matters.

Worked example: the same line in both languages

An operations coordinator applying to a semi-government authority in Riyadh.

Weak (English CV): “Responsible for coordinating operations and supporting the team with daily tasks.”

Strong (English CV): “Cut supplier invoice processing from 9 days to 3 across 4 departments by moving approvals into a shared tracker, handling 120+ invoices monthly.”

Strong (Arabic CV): “قللت مدة معالجة فواتير الموردين من 9 أيام إلى 3 أيام في 4 إدارات، بعد نقل مسار الاعتماد إلى متتبع مشترك، بمعدل أكثر من 120 فاتورة شهرياً.”

Notice the Arabic line is not a translation of the English line — it is the same fact rebuilt in natural Arabic sentence order. That is the standard to hold yourself to. A CV that reads like machine translation signals less care than a CV written plainly in one language. The achievement formulas work identically in both.

Common mistakes

  • Sending English to a ministry because “English looks more professional.” It looks like you did not read the posting.
  • Sending Arabic to a multinational’s global portal where a regional recruiter in Dubai or Cairo screens the first pass.
  • Translating the English CV word for word with an AI tool and shipping it unread. Job titles come out wrong, and Saudi readers spot translated Arabic instantly.
  • Arabic file names. سيرة ذاتية.pdf breaks in some upload forms and email gateways, and tells the recruiter nothing.
  • Different content in the two versions. They should carry the same facts, dates and numbers. Recruiters who receive both will compare them.

Keeping both versions honest and in sync

The real cost of a bilingual job search is maintenance. You update a number in the English CV, forget the Arabic one, and three months later you have two documents that disagree about your own career.

This is the problem TrueSira was built around. You keep one Master Profile holding your real experience, achievements and numbers once. When a posting comes in, you paste it and get a tailored, ATS-ready CV in the language that posting demands — with every line traced back to something you actually did, and shown to you for approval before it lands in the document. Update the fact once and both languages stay true. Get started free.

FAQ

Should a CV for a Saudi government job be in Arabic?

Yes. Government entities and postings routed through جدارات correspond, review and archive in Arabic. Send Arabic as the primary file. Keep an English version ready in case a technical team asks for it later in the process, but do not lead with it.

Can I send one CV with both Arabic and English?

Send one language per file. If a form allows only one attachment and you truly need both, stack them — Arabic pages first, then English — in a single PDF. Never lay them out side by side in two columns; that is the layout parsers handle worst.

Does an Arabic CV hurt me with ATS software?

Not because of the script. Modern systems read Arabic and right-to-left text fine. Arabic CVs fail more often because they are built with tables, text boxes, two columns, decorative fonts, or scanned images. Build the Arabic file with the same plain, one-column rules you would use in English.

Which language do Aramco and SABIC expect?

English. Aramco, SABIC, Ma’aden, stc, the banks and the giga-project developers post in English and run English application systems. Apply in English unless you are answering a specific posting published in Arabic.

Should my job titles stay in English inside an Arabic CV?

Write the title in Arabic and add the English in brackets on first use — محلل بيانات (Data Analyst). Keep tools, certifications and technologies in Latin script throughout. That way you match both the Arabic and the English search terms a recruiter might use.

Which version should I put on LinkedIn?

English profile, with Arabic used naturally in your About section if you want it. Recruiter searches on LinkedIn in the Saudi market run overwhelmingly in English. See our LinkedIn keyword guide for how those searches actually work.