In the Gulf, your CV usually arrives on WhatsApp. Almost nobody builds one for that.

Here is the actual journey of a CV in the Gulf, more often than not.

You send it to a consultant on WhatsApp, because that is the number on the advert. The consultant forwards it to a colleague. The colleague attaches it to an email to the client's HR coordinator. The coordinator forwards it to a site manager, who opens it on a phone, in a car park, between two meetings.

Four hops, three applications, two devices. At no point did anyone sit down at a desktop with your document and a cup of coffee. And the version the site manager opens is the one that decides whether you are interviewed.

What breaks along the way

The file name

This is the most consequential detail that nobody thinks about. When your file is called CV.pdf or Resume_final2.docx or document (3).pdf, it arrives in a folder alongside forty others with the same name, and it gets renamed, lost, or overwritten. When the site manager searches their phone a week later for your file, they search your name — and if your name is not in the file name, nothing comes back.

Name it Firstname-Lastname-Role.pdf. Nothing else. No dates, no version numbers, no "final".

The file size

A CV carrying a high-resolution photograph, a scanned certificate page and a decorative header can run to several megabytes. On a slow connection at a site office, a large attachment does not get opened — it gets left for later, and later does not arrive. Keep it small. A well-built text CV is a small file.

The format

Send a PDF unless you are asked for something else. A PDF looks the same on every device, which is the entire point when you do not control the device. A .docx will re-flow on a phone, substitute fonts it does not have, and can arrive looking broken through no fault of yours.

The exception matters, though: when you are uploading to a portal or a job board that asks for Word, give it Word. Those systems parse the file, and a .docx parses more reliably than a PDF that was exported oddly. The rule is: PDF for humans, whatever the system asks for when it is a system. Keep both.

The scanned pages

Certificates, passport copies, visa pages and reference letters appended to the CV as scanned images make the file large, unsearchable and slow, and none of them are read at screening stage. Keep them in a separate file, ready to send the moment they are requested, which is usually after an offer is in sight.

Designed for the second screen

A phone screen shows roughly the top quarter of a page at readable zoom. That is your whole first impression.

On a desktop this works	On a forwarded phone view it does not
Two-column layout with a sidebar	Columns collapse or overlap; the sidebar can render last
A wide header band with a photo	Consumes the entire first screen before any content
9pt body text to fit one page	Unreadable without pinch-zooming, which most people will not do
Name and contact details in the page footer	Never seen; footers are the first thing skipped
Skills shown as chart bars or star ratings	Graphics that carry no text; on a small screen, decoration
Single column, name and target role at the top	Works everywhere, including here

The message you send it with

The attachment is half of it. The message carrying it is the other half, and a bare file with no text is easy to ignore.

1. Lead with the role and where you saw it, in one line.
2. State your current location and visa status — in the Gulf this is the first thing anyone needs and it saves a round trip.
3. Give your notice period or availability date.
4. One sentence on the single most relevant thing you have done.
5. Say the file name, so it can be found again: "Attached as Ahmed-Khan-Facilities-Manager.pdf".
6. Stop. Six lines is plenty; a long message on WhatsApp gets collapsed behind "Read more" anyway.

The version problem

One consequence of the forward chain deserves separate attention: once your CV leaves your hands, you cannot recall it.

A consultant who received your file in March still has it in September. When a new role comes up, they forward what they hold — not what you have since improved. People discover this when they are put forward for a role using a CV two versions old, with an outdated title, a missing recent job and a phone number they no longer use.

There is no technical fix, but there is a practical one. When you make a significant update, send the new file to every consultant who has your old one, with a single line: "Updated CV, please use this version." It takes ten minutes and it prevents the specific, avoidable failure of being represented by a document that understates you.

The same applies to the phone number and email on the file. A contact detail that has changed since you last sent the CV is the one error on this list that costs you an offer outright, because the call simply does not connect and nobody chases.

What this doesn't fix

A clean, correctly named, phone-readable file does not make you a stronger candidate. It makes you a legible one. Everything that determines the outcome — your experience, the fit, the timing — is unchanged.

Nor does it apply everywhere. Large employers with proper applicant systems, and most government entities, take applications through a portal where none of this is relevant. This is about the agency and contractor channel, which is where a great deal of Gulf hiring actually happens.

And no amount of file hygiene compensates for sending your CV to a consultant who has no live vacancy for you. The best-prepared file still needs somewhere real to land.