We're looking for a project controls professional — someone who has lived inside EPC project teams building cost reports, schedules, and variation logs — to bring that expertise into an independent assurance role. You'll keep using the same technical toolkit (cost engineering, planning, EVM, claims), but apply it as a reviewer testing the integrity of other project teams' numbers, rather than as the one producing them.
This is a strong next step for a senior project control engineer or cost/planning lead who wants to broaden into risk, governance, and cross-project exposure — without leaving the technical substance of EPC project delivery behind.
What you'll actually be doing
- Digging into cost reports, forecasts, and cost-to-complete estimates across UCC's EPC and capital projects (including JV-structured projects) to test whether the numbers hold up
- Reviewing schedule quality — critical path logic, delay analysis, EOT claims — the way you would if you were sitting in the project, but now checking someone else's work
- Assessing variation orders, claims, and contractual entitlement positions for completeness and supporting evidence
- Evaluating contractor/subcontractor performance data and progress measurement methods
- Building structured review frameworks (Risk Control Matrices) around project controls processes — this is a methodology we'll train you on if it's new
- Writing up findings in a way project directors and commercial teams will actually engage with
- Sitting down with project directors, project controls managers, and contracts teams to walk through what you found and agree next steps
- Following findings through to actual closure, not just reporting them
What you bring
- Engineering degree (Civil, Mechanical, Electrical, or related)
- 6-8+ years in project controls — cost engineering, planning/scheduling, or contracts/commercial — on EPC, construction, or infrastructure projects
- Real fluency in EPC contract structures, claims, variations, and JV project arrangements
- Comfort interrogating cost and schedule data and spotting where something doesn't add up
- Strong writing — able to turn a technical issue into a clear point a non-technical stakeholder will act on
- PMP, CCP, or other project management and/or project controls certifications
