Data Analyst Job Description Template (GCC / UAE, 2026)

How to Use This Data Analyst Job Description Template

This is an editable, GCC-ready job description for a Data Analyst. Copy it, replace every bracketed placeholder, and delete what does not apply. The defining feature of hiring data analysts is that there is no licence and no professional-body registration to verify - so the job description has one job above all others: to screen on demonstrable skill, not on titles or certificates. The most effective single change you can make is to state in the post that a short hands-on SQL/BI exercise is part of the process. That one line self-selects out the large share of applicants who list SQL, Power BI and Python on a CV but cannot actually use them, and it does far more for applicant quality than any list of required certifications.

Data Analyst Job Description Template

Job title: Data Analyst [SQL & Power BI / SQL & Tableau] - [City], [Country]

Reports to: [Head of Data / Analytics Lead / BI Manager]

Employment type: Full-time, [on-site / hybrid] | Sponsorship: Employer-sponsored UAE/GCC work visa provided

About [Company]: [One or two sentences: your sector, the decisions this person's analysis will inform, and the data they will work with. Specificity attracts the right people.]

Role purpose: Turn data into decisions - extract and model data, build reports and dashboards, and partner with business teams to answer questions and track performance.

Key responsibilities:

• Write and optimise SQL queries against [data warehouse / database] to extract, join and model data.
• Build and maintain dashboards and reports in [Power BI / Tableau], with clear, trustworthy metrics.
• Define and track KPIs with [commercial / operations / finance] stakeholders and explain what the numbers mean.
• Investigate and resolve data-quality issues; document data definitions and sources.
• Use Python or R for ad-hoc analysis, automation and statistical work where appropriate.
• Present findings and recommend actions to non-technical audiences.

Required qualifications and experience:

• Strong, demonstrable SQL (this is the non-negotiable core - it will be tested).
• Hands-on experience building dashboards in [Power BI / Tableau].
• [X]+ years in a data/analytics role, with a portfolio of real analysis work.
• Ability to communicate insight clearly to business stakeholders.
• Bachelor's in CS, statistics, mathematics, economics or related - or equivalent demonstrable skill (degree not mandatory if the work is strong).

Preferred / nice to have: Python or R; PL-300 (Power BI), Tableau Desktop Specialist or Google Data Analytics certification; cloud data certs (Azure/AWS); [domain] experience (banking, retail, government, logistics); bilingual English/Arabic.

What we offer: Competitive salary (AED [X]-[Y]/month), [housing/transport allowance], medical insurance, employer-sponsored visa and end-of-service gratuity per UAE Labour Law. [Add learning budget, certification support, hybrid policy.]

How to apply: [Application instructions - e.g. include a link to a dashboard, notebook or analysis you are proud of. Note that shortlisted candidates complete a short SQL/BI exercise.]

Salary Bands to Anchor the Offer (UAE, 2026)

Use these indicative monthly bands so your posted range is credible. Junior (0-2 yrs): roughly AED 8,000-12,000. Mid-level (2-5 yrs): roughly AED 12,000-20,000. Senior (5+ yrs): roughly AED 20,000-35,000+, with banking and consulting at the top. Power BI/Tableau/cloud certifications can add roughly 20-30% to expected pay and double as ATS keywords. These are recruiter/job-board ranges, not an official survey, so confirm against a current 2026 salary guide before finalising the band.

Tips for Writing a Data Analyst JD That Converts

• Announce the skills test. Stating that a short SQL/BI exercise is part of the process is the single highest-impact line - it filters out CV-only candidates and signals you take craft seriously.
• Lead with the tools you actually use. Naming SQL plus your specific BI tool (Power BI or Tableau) is a sharper filter than a generic "data tools" list.
• Make the degree optional where you can. Because skill is what matters and there is no licence, "degree or equivalent demonstrable skill" widens a strong pool without lowering quality.
• Ask for a portfolio. Requesting a dashboard, notebook or analysis link surfaces proof of work that no certificate can replace.
• State the domain. "You'll work with [banking/retail/logistics] data" attracts candidates who understand your sector's quirks.
• Emphasise communication. The best analysts turn numbers into decisions; say so, and screen for it, not just for tool proficiency.
• Rank certifications as secondary. List PL-300, Tableau Desktop Specialist and Google Data Analytics under "preferred", not "required" - they are signals, not gates.
• State the visa stance. Confirming sponsorship or transferable-status requirements prevents late-stage drop-off.

Tailoring the JD by Seniority

A junior data-analyst description should emphasise foundations and trainability: strong SQL, a willingness to learn your BI stack, curiosity and clear communication, with a smaller portfolio (university projects, bootcamp work or a personal dataset) accepted as proof. Keep the requirements short and the salary band honest (roughly AED 8,000-12,000), and lean on the hands-on test rather than years of experience. A mid-level description should require independent ownership of dashboards and stakeholder relationships, demonstrable impact ("analysis that changed a decision"), and fluency in at least one of Python or R. A senior description should add mentoring, data-modelling and metric-governance responsibilities, the ability to define what gets measured across a function, and influence with non-technical leadership - here a stronger portfolio and a track record of business impact matter more than any certification. Matching the requirements to the level you are actually paying for prevents both over-specifying (deterring good juniors) and under-specifying (attracting juniors for a senior band).

Tailoring the JD by Domain

Domain context sharpens the post. In banking and financial services, signal regulatory and risk-data familiarity and expect to pay at the top of the band. In retail and e-commerce, emphasise sales, inventory and customer-behaviour analytics and the volume/velocity of the data. In government and semi-government, flag the reporting cadence, data-governance expectations and often a preference for Arabic. In logistics, emphasise operational and supply-chain metrics. Naming the domain and one or two of its quirks ("you'll work with high-cardinality transaction data" or "reconciling data across three legacy systems") does two things: it attracts candidates who have seen the problem before, and it quietly screens out those who have only worked with clean, textbook datasets.

Posting & Sourcing the Role

Data analysts respond to different channels than engineers. A niche GCC job board concentrates work-authorised regional candidates; LinkedIn is strong for mid-level profiles with visible portfolios; specialist technology and data agencies help on senior or niche-domain mandates; and analytics communities, meetups and a candidate's public GitHub, Kaggle or dashboard portfolio let you assess work before first contact. Whatever the channel, the line announcing a hands-on SQL/BI exercise is the highest-leverage element of the post - it self-selects the pool more effectively than any keyword. Pair that with naming the exact tools you run and the domain you operate in, and you convert a noisy, certificate-padded applicant stream into a short list of people who can actually do the job.

Common Mistakes to Avoid

The classic data-analyst hiring mistake is treating certifications as proof of ability and skipping the hands-on test, then hiring someone who looks strong on paper but cannot write a working query or build a defensible dashboard. The second is making a bachelor's degree mandatory when skill, not credentials, is what the role needs - this needlessly shrinks an excellent self-taught pool. The third is writing a generic "data" JD that lists every tool under the sun; instead, name the two or three you actually use and the domain you operate in. The fourth is mismatching requirements to the band - asking for senior ownership at a junior salary, or vice versa. Get the skills test, the optional-degree framing, the tool specificity and the seniority match right, and you will interview far fewer, far better candidates.