Oil Programme QA Lead - 1 year FTC

Main purpose

The Oil Programme is a signature strategic initiative at Trafigura to implement a new, fully integrated end-to-end trading system for the energy business. It replaces the legacy platform with two interconnected ecosystems:

• Atlas — Front Office and Middle Office: trade capture, pricing, deal lifecycle, and logistics workflows.

• Titan — downstream finance processing: a dedicated Energy instance of the Titan platform currently under active development.

The two ecosystems share a bidirectional, real-time integration boundary — the highest-risk surface in the programme.

The Oil Programme QA Lead is a programme-level quality assurance role, independent of both delivery teams. It owns end-to-end QA coverage for the full programme: everything that falls outside the scope of the individual Atlas and Titan ecosystem QA leads, plus the integration and coherence between them.

The role is a standing member of the Oil Programme Readiness Group. It has authority to define programme-wide QA standards, set UAT entry and exit criteria, block UAT entry if criteria are not met, and escalate quality risks directly to the Programme Director.

This role is a 1 year fixed term contract.

Key responsibilities

Programme-level QA ownership

• Own the programme-level QA strategy, incorporating and coordinating the Atlas and Titan ecosystem testing strategies.

• Define and maintain the E2E scenario model in partnership with the Product Validation team, ensuring every UAT acceptance criterion maps to tested coverage.

• Publish a single, authoritative programme QA status view to delivery leadership and business stakeholders.

• Own the escalation path for cross-team defects, coverage disputes, and quality risks.

Cross-ecosystem and integration testing

• Define and oversee testing of end-to-end business scenarios spanning both Atlas and Titan.

• Own QA coverage for cross-cutting systems such as Hydra that interact with both ecosystems.

• Coordinate E2E and performance testing workstreams, sequencing them so UAT entry criteria are met before formal UAT begins.

• Identify and close coverage gaps that neither individual ecosystem strategy addresses.

Reporting and data validation

• Coordinate the QA workstream for approximately 100 QlikSense reports that consume data from both Atlas and Titan.

• Define data validation scenarios and expected outputs; coordinate business sign-off on report accuracy.

• Ensure report validation is sequenced and completed before UAT entry.

UAT readiness and governance

• Define UAT entry and exit criteria at programme level, based on UAT scenarios and business risk.

• Work with Atlas QA Lead and Titan QA Lead to ensure ecosystem-level activities meet programme entry criteria.

• Bridge the different testing cadences: Atlas agile sprint-based testing and Titan manual release-cycle-based testing.

• Act as standing member of the Oil Programme Readiness Group; contribute to programme readiness decisions and cutover planning.

Stakeholder engagement

• Report QA status, risks, and blockers to the Programme Director and Steering Committee.

• Engage with Front Office, Middle Office, and Back Office business stakeholders during UAT definition and execution.

• Represent QA interests in programme planning, milestone reviews, and risk forums.

• Co-ordinate with infrastructure, release management, and environment teams to ensure test environments are stable and available.

Required qualifications

• Significant experience leading QA at programme or portfolio level — not just within a single delivery team.

• Background in financial services or commodities trading technology; familiarity with front-to-back trade lifecycle (trade capture → risk → P&L → settlements → accounting).

• Proven ability to design and own end-to-end test strategies across multiple systems and teams.

• Experience defining UAT entry and exit criteria and driving readiness decisions with senior business and technology stakeholders.

• Strong understanding of system integration testing: messaging, APIs, event-driven architectures.

• Skilled at bridging different delivery methodologies — agile and waterfall / release-cycle-based teams working in parallel.

• Excellent written and verbal communication; able to present quality status and risks clearly to non-technical audiences.

• Independence and authority: comfortable escalating risks upward and holding delivery teams accountable to programme standards.

Preferred qualifications

• Experience with large-scale platform migration or legacy decommission programmes.

• Familiarity with commodity trading platforms, ERP financial modules, and reporting tools.

• Exposure to performance testing strategy and tooling.

Attributes for success

• A programme-level QA strategy is in place and accepted by all stakeholders prior to system integration testing.

• Every UAT acceptance criterion has documented, traceable test coverage before UAT entry is declared.

• All QlikSense reports are validated and business-signed-off before UAT cutover.

• The programme enters UAT with a clear, agreed entry gate that has been met — not waived.

• Cross-ecosystem defects and coverage gaps are visible, owned, and resolved — not lost between teams.

• Programme leadership and business stakeholders have a single, trusted source of QA status throughout.