ATS CV for UAE and Saudi jobs: what matters, what's a myth

Short answer: an ATS-friendly CV for the UAE, Saudi Arabia or Egypt is a plain, single-column document with real text, standard headings, and the posting's own words for skills you actually have. That's it. The "beat the ATS" tricks (keywords hidden in white text, skills you don't have, graphics full of text) don't get you past a filter. They get you noticed by a person, for the wrong reason.

This guide covers what an applicant-tracking system (ATS) actually does with your CV, which popular claims about it are myths, what the Gulf-specific fields (photo, date of birth, nationality, visa status) mean for parsing, and whether an ATS can read an Arabic CV.

What an ATS actually does with your CV

An applicant-tracking system is the software a company uses to receive and manage applications. When you apply through a careers page, three things typically happen:

1. It stores your application: your CV file, your cover letter, and your answers to the form's questions.
2. It parses your CV: it extracts readable text into fields on your candidate profile. Lever's help centre, for example, describes the parser pulling out your name, contact details and employer, and filling the matching profile fields (Lever).
3. It lets recruiters search and filter: by keywords, by job title, and by your answers to the application questions.

What it usually does not do is read your CV and decide on its own. Greenhouse, an ATS vendor, says that "by and large, applications in Greenhouse are reviewed by real people, one by one, in the order received", and that its AI "doesn't score or rank applications" (Greenhouse). The same article is honest that some companies do use AI to score and auto-reject applications. From outside, you can't tell which kind of employer you're dealing with, so write for both: a CV that parses cleanly and reads well to a human.

Myth: "most CVs are rejected by the ATS before a human sees them"

You'll often see a precise-sounding percentage attached to this claim. We looked for a primary source behind it and couldn't find one, so we don't repeat it. What vendors do document is narrower, and more useful to know.

Automatic rejections usually come from the application form, not from your CV. Greenhouse's application rules are "automatic actions applied to job post questions", triggered by the applicant's answer, and one of those actions is auto-reject (Greenhouse). Workable lets employers automatically disqualify anyone who answers "No" to a yes/no question such as "Are you based in the UK?" (Workable).

Those knockout questions are where an employer can screen on visa status, location, notice period or nationality. Two practical consequences:

• Answer the form's questions truthfully, and make them match your CV. A "Yes" to "Are you currently in the UAE?" next to a CV that says "Cairo, Egypt" invites a phone call at best.
• If you fail a hard requirement, no CV format fixes it. A role that requires a nationality you don't hold, or a licence you don't have, is a skip. More on spotting those in the honest job-fit checklist.

What actually matters, part 1: plain structure

The goal is simple. Every word you wrote should come out of the file as text, in the right order.

• Real text, not an image. Lever says it can't parse image files (like JPG or PNG), and suggests a quick test: if you can't highlight the text in the document with your cursor, it's likely not parseable (Lever). A scanned CV, or a CV exported from a design tool as one flat picture, fails that test.
• PDF is fine. Greenhouse accepts .doc, .docx, .pdf, .rtf and .txt (Greenhouse), and Lever parses Word, PDF, RTF and other formats (Lever). Send Word only if the posting asks for it.
• One column, top to bottom. Two-column layouts, text boxes and tables in the main body can come out in a scrambled order when text is extracted. You can check yours: select all the text in your PDF, paste it into a plain-text editor, and read it. If the result is out of order, so is what a parser sees.
• Standard headings. "Experience", "Education", "Skills", "Certifications". Creative headings ("My journey") make it harder for software, and for a tired recruiter, to find things.
• No skill bars, icons or charts. A bar showing "Excel: 80%" carries no text a parser can use, and no information a recruiter can trust. Write the skill, and where you used it.

What actually matters, part 2: real keywords from the posting

Recruiters search their ATS for candidates. If the posting says "financial modelling" and your CV only says "built forecasting spreadsheets", you may not come up. So use the posting's own words, where they are true for you:

• Mirror the job title if it honestly describes what you did. If your title was "Commercial Analyst" and the role is "Financial Analyst", say what you did in terms the posting uses: "Built the monthly financial model for…".
• Use both forms of a term the first time: "Key Performance Indicators (KPIs)", "Customer Relationship Management (CRM)".
• Put keywords in context, inside the experience bullet where you used the skill, not only in a list at the bottom.
• Keep tool and product names exactly as written: "SAP S/4HANA", "Power BI", "AutoCAD".

You don't need to stuff. Greenhouse says the belief that you have to "stuff" your application with keywords "isn't the case" for its system, which suggests related terms and synonyms to recruiters when they search (Greenhouse). Write each skill once or twice, where it belongs.

Why "beat the ATS" tricks backfire

• White text. Pasting the job description in white text at the bottom of your CV is the best-known trick. Text colour is formatting; the words are still in the file. Select all and paste into a plain-text editor, and they appear. Anyone who sees that block, whether in a parsed profile, a text view or by highlighting your PDF, now knows you tried to game them.
• Skills you don't have. Even if a keyword gets you shortlisted, the interview asks about it. A candidate caught bluffing once usually isn't trusted on the rest of the CV.
• Keyword dumps. A paragraph of 40 comma-separated terms reads as filler to a human, and tells a recruiter nothing about what you did with any of them.
• Fancy templates. Graphics, icons and multi-column designs make a CV look modern and parse worse. The plain version wins.
• Chasing an "ATS score". Online checkers give you their own estimate, not the employer's view. There's no universal ATS score: each employer uses a different system with its own settings, and Greenhouse says its AI doesn't score applications at all (Greenhouse).

The honest CV is also the one that works: clear structure, true claims, the posting's language.

Photo, date of birth, nationality, visa: Gulf CV fields and the ATS

Gulf CVs usually carry a personal-details block that Western CVs leave out. We cover when to include each field in CV format for Saudi Arabia and the UAE. Here's what those fields mean for the ATS.

• Write them as labelled plain text. "Nationality: Egyptian", "Visa status: UAE residence visa, transferable", "Notice period: one month". One line each, under your name and contact details.
• Don't count on them landing in a database field. Some parsers can extract personal details. Textkernel's Tx parser, for example, has fields such as visa status and marital status, but its documentation lists them as "low-usage fields": all are available in English, while for other languages they are deprecated or unavailable (Textkernel). Whatever the parser does, the line stays in your CV, where the recruiter reads it. That's who it's for.
• The photo doesn't affect parsing, as long as there's no text inside it. A parser reads text, so a photo neither helps nor hurts, but your name or nationality written on an image is lost. Use a professional, passport-style photo for Gulf-style employers, and remove it for Western-style ones.
• Expect the same questions on the form. Visa status, current location and notice period are common application-form questions, and those answers can trigger the automatic rules described above. Keep the CV and the form consistent.
• Never add your passport number or a copy of your ID. It's not a parsing question. It's a risk if the file is forwarded.

Can an ATS read an Arabic CV?

It depends on the system, and vendors differ. Two documented examples:

• Greenhouse lists Arabic among the languages with full resume-parsing support (Greenhouse).
• Textkernel, a vendor that sells CV-parsing software to recruitment platforms, doesn't mark Arabic as supported for resume parsing on its Tx Platform, only for its skills, professions and ontology features (Textkernel). That's the table as of October 2026.

So you can't assume either way, and you usually can't see which system an employer uses. What you can do:

• Send the language the posting uses. An employer that advertises in Arabic is more likely to be set up to read Arabic CVs. For English postings, send English. More in Arabic CV or English CV?
• Keep two separate files, not one bilingual CV. Mixed right-to-left and left-to-right text can break when the text is extracted.
• In an Arabic CV, keep tool and product names in Latin script ("Excel", "SAP", "Python"), so a search for them can still match.
• Use standard Arabic headings: الخبرات العملية، التعليم، المهارات، الشهادات.

Checklist before you upload

1. Can you highlight every line of text in the file? Does select-all and paste give you your CV in the right order?
2. One column, standard headings, no text inside images, icons or skill bars.
3. PDF or Word, whichever the posting asks for (PDF if it doesn't say).
4. The posting's terms for skills you really have, used where you used them.
5. Nothing hidden, nothing invented. Could you talk about every keyword for two minutes in an interview?
6. Gulf-style employer: personal details as labelled text lines. Western-style employer: removed.
7. The form's answers (visa, location, notice period) match the CV.
8. CV language matches the posting's language.

ATS CV FAQ

Is a PDF CV ATS-friendly? Usually, yes. Greenhouse and Lever both accept PDFs. What matters is that the PDF contains real, selectable text, not a scanned image. Send Word only if the posting asks for it.

Should I put a photo on an ATS CV for the UAE or Saudi Arabia? For Gulf-style employers it's common, and a photo doesn't stop the text from parsing. Just never put text inside the image. For Western-style employers, leave it off.

Can an ATS read an Arabic CV? Some systems support Arabic parsing and some don't, and you usually can't tell from outside. Send Arabic when the posting is in Arabic, and keep the layout plain.

Does hiding keywords in white text work? No. Text colour is formatting; the words are still in the file, and anyone who sees them knows you tried to game the process.

Do I need a special ATS CV template? No. A plain single-column document with standard headings is the "ATS template". Templates with graphics and columns can parse worse.

Will the ATS reject me if I don't match every keyword? Not on its own, in the systems we checked: Greenhouse's and Workable's automatic rejection rules run on the form's questions, not on your CV text. Recruiters search and read CVs, so use the posting's words where they're true for you.

Where Taqdim fits

Taqdim writes a new CV for each role from your profile, and it's designed not to add skills, employers or achievements you didn't give it, so there's nothing in it you'd have to explain away in an interview. Before it writes anything, it checks your fit and flags knockouts such as work authorisation, nationality, location and language: the same things employers' form questions screen for. You review every document before you use it, and AI can make mistakes. What Taqdim does and doesn't do.

Taqdim is in closed beta. Join the waitlist.

---

Related: CV format for Saudi Arabia and the UAE: photo, date of birth and visa status · Arabic CV or English CV? · Should I apply for this job? The honest job-fit checklist.

Sources

• Greenhouse, "What really happens after you apply for a job?" (8 January 2025): greenhouse.com
• Greenhouse Support, Application Rules overview: greenhouse.io
• Greenhouse Support, supported file types for resumes and cover letters: greenhouse.io
• Greenhouse Support, resume parsing with non-English languages: greenhouse.io
• Lever Help Center, Understanding Resume Parsing: lever.co
• Workable Help, auto-disqualify candidates using application form questions: workable.com
• Textkernel Tx Platform, supported languages: textkernel.com
• Textkernel Tx Platform, resume parser low-usage fields: textkernel.com