Business Intelligence Developer

Job Summary

Designs, builds and maintains all BI reporting through the multiple platforms by which EPMO performance is presented to the Group's executive leadership, delivery directors and project teams. Working on top of the governed data model owned by the Data Engineer, the role turns validated project, cost, schedule, commercial and procurement data into dashboards, executive reports and self service analytics that answer the questions decision makers actually ask. The position exists to replace manually assembled slide packs and spreadsheet trackers with a consistent, governed and automated reporting suite, so that every figure presented to leadership is current, consistent from one report to the next, and traceable to its source.

Job Responsibilities 1

Independent project assurance

•  Form and maintain an independent view of progress, schedule and cost to complete on each allocated project, tested against source evidence and not against reported status.

•  Run stage gate and monthly reviews for projects at the check it tier, and record decisions, owners and dates.

•  Validate baselines, critical path, float movement and resource loading, working with the Risk and Schedule Analyst.

Recovery and intervention

•  Sit with projects at the run it tier, own the recovery plan, and close actions daily with named owners until the project is stable.

•  Establish the real cause of delay or overrun, and flag the commercial consequence to Commercial Assurance early.

•  Hand a stabilised project back to the reporting system and move to the next project that needs a person.

Escalation and accountability

•  Hold Project Directors, entity COOs and managing contractors to agreed actions and dates, and escalate immediately and with evidence when they are missed, without waiting for the next reporting cycle.

•  Escalate delegation of authority and signatory findings as soon as they surface.

•  Represent the EPMO in delivery review forums, so that every level of leadership hears the same position.

One set of numbers

•  Draw delivery data from the governed model for the group pack, with no private spreadsheets or parallel versions.

•  Capture lessons from each recovery and add them to the EPMO playbook.

Job Responsibilities 2

AI Fluency, Essential

Genuine, demonstrated use of AI as a core working tool, evidenced by specific real examples from the candidate's own work. General awareness of tools, or use limited to drafting and presentation polish, does not meet the standard. Tested at the start of every interview, and a candidate who cannot give a real example does not proceed.

•  Able to describe a real instance of using AI to spot delay risk earlier, accelerate root cause analysis or shape a recovery plan, not a hypothetical.

•  Comfortable directing or working with technical colleagues to build AI assisted tools for schedule and delivery analysis, without needing to be a developer.

AI in the day to day work of this role

•  Comparing each programme update against baseline and prior periods to find float loss, changed logic and tasks slipping without being reported.

•  Reading site reports, minutes and correspondence at volume and testing them against reported progress.

•  Spotting the same contractor, package or interface failing across more than one project.

•  Checking every AI output against the source before it reaches a Director or a forum.

Additional Responsibilities 3

Job Knowledge & Skills

•  Fluent in the construction delivery lifecycle: mobilisation, design freeze, procurement, execution, testing and commissioning, handover and defects liability.

•  Able to read a project programme in Primavera P6 or equivalent and tell genuine critical path slippage from float erosion or a reporting artefact.

•  Understands the difference between delay caused by contractor underperformance, design or IFC delay, procurement or payment blockage, and client side or force majeure factors, and can substantiate which applies from the paper trail and not just the narrative in a meeting.

•  Comfortable with main contractor and subcontractor chains, including where both sit in the same group.

•  Understands what a genuine contractual notice or dispute escalation looks like against routine correspondence.

Working Style

•  Strong presence, able to hold their own in a room with subsidiary CEOs without EPMO leadership needing to run interference.

•  Persistent, and comfortable being the person who says an item is not actually closed when the room wants to move on.

•  Firm but not confrontational by default. Credibility comes from accuracy and not volume. Asks what changed since last time, and does not accept a restated status.

Job Experience

Job Experience

•  10 to 15 years in major projects delivery, ideally in a main contractor, PMO or client side delivery assurance function, with genuine construction or major infrastructure experience.

•  Has taken a project in trouble and brought it back, and can say what they personally did.

•  Track record of holding senior stakeholders, at CEO, COO and Project Director level, to account in a forum and not only in writing.

•  Gulf or wider MENA experience strongly preferred, including holding company to subsidiary delivery chains.

Competencies

Education