Writing Job Descriptions That Work in the GCC

GCC job descriptions

A strong job description does two things at once. It attracts the right candidates and quietly filters out the wrong ones. A weak one does neither, which is why a flood of unqualified applications usually signals a poorly written job description rather than a difficult market. This page lays out how Gulf-fluent job descriptions actually look, section by section, so the next role you post brings the right candidates to your inbox in the first place.

I am an HR Career Specialist, and I have read more weak job descriptions than I can count. The strong ones share a clear shape. Once you copy that shape, your hiring funnel improves immediately.

The structure that actually works

A Gulf job description should run six clear sections. A specific job title that matches the market language. A short company introduction, two or three sentences, that explains who you are and why a strong candidate should care. A clear list of responsibilities, ideally five to eight specific bullets rather than a vague paragraph. A required qualifications section that names the must-haves and the nice-to-haves separately. A salary and benefits indication, even as a band. And a clear application instruction.

That structure fits cleanly on one screen, reads in under ninety seconds, and gives candidates everything they need to self-filter. The GCC Job Description Generator drafts this structure for you in minutes, but the discipline of writing one by hand at least once helps you understand the why behind each section.

The job title matters more than you think

Job titles in the GCC are often more conservative and more specific than in some Western markets. A Western “Growth Marketer” reads as confusing here, where “Senior Marketing Manager, Digital Acquisition” would be clearer. So write the title for the candidates you want to attract, in the language they already use to describe themselves.

Avoid invented or playful titles that sound clever in a startup pitch deck but unsettle serious candidates. A senior banker scanning roles is not going to apply for a “Money Wizard” position, even if the work is identical to the Senior Investment Manager role they would have applied for. The title is a filter as much as a label.

Responsibilities, written as outcomes not chores

Most weak job descriptions list responsibilities as chores. “Manage the team”, “report on performance”, “ensure compliance”. These say nothing. Stronger ones write the same responsibilities as outcomes. “Lead a team of six analysts to deliver quarterly client reporting on time and to standard”, “build the monthly performance dashboard that the executive team uses to make commercial decisions”, “ensure regulatory compliance across the UAE and KSA operations, with zero audit findings”.

Outcome-led responsibilities do two useful things. They attract candidates who think in outcomes, who tend to be your strongest hires. And they unconsciously set the right expectation for the role. I once watched a hiring team rewrite five responsibilities into outcomes, then receive a meaningfully stronger calibre of candidate within a fortnight. [VERIFY ANECDOTE] The work was the same. The framing changed who applied.

Qualifications: must-have versus nice-to-have

One of the most common GCC job description mistakes is bundling every desirable trait into a single qualifications list, which scares off strong candidates who tick eight of ten boxes but assume they need all ten. Split the list. Name the genuine must-haves, which should be three to five items at most. Then name the nice-to-haves separately, with a clear caveat that they are bonuses, not deal-breakers.

I have seen candidates with strong fit refuse to apply because they could not match the seventh nice-to-have on a single combined list. They assumed it was a hard requirement. A split list saves you those candidates. It also makes your shortlist easier to defend internally, because you can show which boxes the candidate ticks and which they do not.

Visa eligibility and local context

Two GCC-specific lines belong on every job description. Whether you sponsor visas or require existing residence in the relevant country. And the location of the role with a clear note on remote, hybrid, or in-office expectations. Both of these self-filter candidates who would not have been viable, which saves you and them time later in the process.

For roles that genuinely benefit from Arabic, name that as a nice-to-have rather than a must-have unless the role truly requires it. Many strong expatriate candidates assume any mention of Arabic excludes them, and you lose applications you would have welcomed. Be precise about what the role really needs.

Should you publish a salary band?

This is a live debate in GCC recruitment, and my view is clear. Publishing at least an indicative band, or a top of band figure, attracts stronger applications and saves wasted process on candidates whose expectations are far from yours. The candidates who match self-filter in. The ones who do not self-filter out. Both sides save time.

Many GCC employers still hesitate to publish bands, fearing internal equity questions or competitive sensitivity. Those concerns are real, and they are usually outweighed by the gains in funnel quality. I once helped a hiring team move from “competitive salary” to a published band on their next senior role. [VERIFY ANECDOTE] The applications dropped by half in number and doubled in quality. They closed the hire three weeks faster than the previous equivalent role.

Bilingual when it matters, not by default

Some GCC roles benefit from a bilingual English and Arabic job description, especially in retail, customer-facing roles, and roles likely to attract national candidates. For senior expatriate roles in finance, technology, or engineering, English alone is usually fine. So make the bilingual decision deliberately rather than as a default. A bilingual job description posted in the wrong context can read as targeted at a different audience than the one you actually want.

The discipline of writing job descriptions well is part of the wider practice of running a serious hiring process. Once your job description is right, read the screening CVs page for the next step of the funnel.

The application instruction that quietly filters well

The final section of a strong GCC job description tells candidates exactly how to apply, including any specific document they should send, the application channel, and the realistic response timeline. I always tell my hiring teams to be explicit here rather than rely on candidates to guess. A clear instruction filters out applicants who cannot follow basic written direction, which is genuinely useful at scale.

The instruction also serves as a candidate-experience signal. The candidates I want most are the ones who care enough to read the instruction and respect it. Vague or missing application directions signal a sloppy employer brand, and the strongest candidates often quietly skip employers who project sloppiness even at the job description stage. So treat the final paragraph with the same care as the headline title. Both shape who decides to apply, and both are part of how the candidate reads you before you ever read them.

Common questions about GCC job descriptions

How long should a GCC job description be?
Long enough to attract the right candidates and short enough to read in under ninety seconds. Typically 400 to 700 words, structured into clear sections. Anything longer loses candidates before they finish reading.

Should you publish a salary band on a Gulf job description?
Yes, where you can. Published bands attract stronger candidates and save process time on misaligned applications. The funnel quality gains usually outweigh the internal equity concerns most employers worry about.

Does a GCC job description need to be bilingual in English and Arabic?
Only where the role genuinely benefits from it, especially in retail, customer-facing, and national-targeted roles. For senior expatriate roles in finance, technology, or engineering, English alone is usually sufficient.

This page gives general information, not recruitment advice. Practices vary by sector and employer, so adapt to your context.

๐Ÿ‘‰ Enjoying this content? Stay updated with more insightful articles and tips by subscribing to our newsletter. Subscribe Now ๐Ÿ‘‰ and never miss an update!