Key Responsibilities

 Define the integration architecture across internal and external systems

involved in the workflow.

 Establish source-of-record rules, survivorship logic, and write-back

boundaries.

 Own the operational information model across case state, evidence, identity,

and integration payloads.

 Define system interaction patterns, API contracts, sequencing expectations,

and control boundaries.

 Design identity and cross-reference approaches across fragmented system

identifiers.

 Shape auditability, masking, information handling, and non-production data-

control patterns.

 Partner with engineering to ensure integration design is practical and

implementation-ready.

 Identify structural data and control risks early and turn them into explicit

design decisions.

Required Experience

 Strong experience in integration architecture across complex enterprise

landscapes.

 Experience defining canonical operational information models and source-of-

record patterns.

 Deep understanding of system boundaries, API interaction design, and data

control patterns.

 Experience working with governed or regulated information flows.

 Ability to simplify fragmented environments into workable architecture

decisions.

 Strong collaboration skills across architecture, engineering, and business

stakeholders.



Preferred Experience

 Experience in master data, identity resolution, or cross-reference design.

 Background in financial services, procurement, risk, legal, or other

operationally complex domains.

 Familiarity with audit, evidence, and control-driven system design.

What Success Looks Like

 Source-of-record and boundary decisions are clear and durable.

 Integration design reduces coupling and rework.

 Identity, evidence, and information-control patterns support both delivery

speed and auditability.

 Engineering teams can build integrations from stable design foundations.

Candidate Profile

This role suits an architect who combines enterprise integration thinking with strong

operational information design. The successful candidate will be comfortable solving

messy boundary problems without drifting into abstract documentation detached

from delivery.