Support Entity' approved data, pipeline, reporting and analytics platforms. The role coordinates with data owners and technical teams to maintain platform availability, data flow and operational reporting while business definitions, data ownership and governance decisions remain with the Entity.

•     Monitor and support approved data platforms, pipelines, scheduled jobs, semantic models and reporting services.

•     Investigate data-flow failures, refresh issues, performance concerns and platform incidents.

•     Coordinate with data owners to clarify issues relating to data quality, lineage, access and business definitions.

•     Support approved dashboards, analytics services and reporting platforms within the agreed support scope.

•     Maintain data-flow documentation, platform inventories, runbooks, schedules and dependency records.

•     Support access controls, data protection and operational evidence required by governance processes.

•     Identify enhancement, new-report or model-development requests and route them through formal approval.

•     Contribute to operational reporting, trend analysis and service improvement.

Requirements

Minimum Experience and Qualifications

•     Minimum 5 years of data engineering, analytics platform or BI support experience.

•     Experience with Power BI, Tableau, Databricks, Snowflake or equivalent enterprise data platforms.

•     Strong working knowledge of SQL, ETL/ELT, data pipelines, scheduling, monitoring and troubleshooting.

•     Understanding of data quality, lineage, access control and governance principles.

•     Ability to communicate effectively with technical teams and business data owners.

Preferred Profile

•     Previous experience supporting UAE government data and analytics initiatives.

•     Working knowledge of TDRA-hosted data platforms or related federal data processes.

•     Arabic language capability for stakeholder and data-owner coordination.

Expected Contribution

•     Data platform and pipeline incidents are owned and resolved against the confirmed service targets.

•     Operational documentation and dependencies remain current.

•     Business/data-owner decisions are clearly separated from technical support responsibilities.

•     New development requests are governed outside BAU support when applicable.