This list contains only the countries for which job offers have been published in the selected language (e.g., in the French version, only job offers written in French are displayed, and in the English version, only those in English).
The Head of Data Schema is accountable for defining, governing, and evolving the Investment Bank’s canonical data schemas, ensuring that business meaning, regulatory intent, and technical implementation remain consistently aligned across platforms, products, and regions. The role acts as the accountable owner for IB-wide trade data model and related governance, bridging business data definitions, regulatory requirements, and engineering delivery. This role is a critical control point for model-driven governance, supporting regulatory defensibility, platform rationalisation, and scalable data product delivery.
Job Responsibility
Own the IB canonical trade data schemas, including core client, product, transaction, reference, and risk data models, aligned to Group standards where applicable
Enforce IB data modelling standards, patterns, and conventions (conceptual → logical → physical)
Lead trade data, including approvals for schema changes and domain extensions
Ensure schemas explicitly support regulatory reporting, controls, and evidencing, including clear lineage from business definition to physical implementation
Partner with Risk, Compliance, Finance, and Legal to ensure schema decisions are regulatorily defensible and auditable
Embed schemas into the delivery lifecycle, ensuring alignment between models, code, interfaces, and deployed data products
Requirements
Deep, hands-on experience in enterprise and domain data modelling (conceptual, logical, physical)
Strong understanding of IB trade schema modelling, and physical schema implementation and controls
Proven experience operating at scale in complex, regulated financial services environments
Demonstrated ability to design and operate data governance frameworks that are practical and delivery-aligned
Experience balancing federation and standardisation without stifling delivery
Experience with model-driven engineering, schema registries, or metadata-driven platforms
Familiarity with financial services standards (e.g. ISO 20022, FpML, FIX, BCBS 239 concepts)