HoweyahIf you're job hunting across Arabic-speaking and international markets at the same time — which is increasingly the normal case, not the exception — your professional page runs into a question a resume usually dodges by existing in only one version: which language does it speak?
The honest answer is usually both, and the reason has less to do with translation and more to do with who's actually going to read it.
Two audiences, two expectations
A local employer or an Arabic-speaking recruiter often expects — and responds better to — content in Arabic, written naturally rather than translated stiffly. A regional or international recruiter, especially one hiring across borders, is typically working in English and skimming quickly. These aren't two versions of the same preference; they're two different expectations, and a single fixed-language page can only meet one of them at a time.
Why a toggle beats maintaining two separate pages
The tempting workaround is keeping two completely separate CVs — one in each language — and sending whichever one fits. In practice this doubles the maintenance work: every update to your experience has to happen twice, in two files, and it's easy for them to quietly drift out of sync until one is noticeably out of date.
A single page with a language toggle solves this by construction. There's one underlying profile, presented in whichever language the visitor picks, which means there's only ever one place to update when something changes.
What this actually looks like in practice
- The same address, either language.
yourname.cvworks as the link regardless of which language the visitor lands on. - Content that reads naturally, not translated. Arabic copy that sounds like something a person would actually say, rather than a stiff, literal conversion of the English version.
- A visible toggle, so the choice is the visitor's, not a guess your page makes based on their browser settings.
Who this matters most for
If you're applying only within one market, in one language, this is a smaller concern. But the moment your search spans both — a local role and a regional one, a Cairo-based company and a Gulf-based one, a recruiter who prefers Arabic and one who only reads English — a single bilingual page removes a decision you'd otherwise have to make every time you send your CV somewhere new.
Building it without doing double the work
This is exactly why Howeyah builds your page in Arabic, English, or both from the same uploaded CV, rather than treating each language as a separate project. If you haven't gone through the setup yet, How to Turn Your CV Into a Website covers the full process — the language toggle comes as part of the same page, not an extra step bolted on afterward.
The short version
Your career doesn't stop at a language border, so your page shouldn't either. A single bilingual address, kept in sync by construction, reaches both audiences without asking you to maintain two versions of your own story.