What You Will Own
Enterprise Data Architecture and Master Plan
Publish and maintain the current and future state data architecture across ERP (Oracle E-Business Suite, Oracle Fusion Cloud and other legacy ERPs), CRM (Salesforce), master data (Reltio), the Snowflake analytical platform and downstream AI consumers.
Map end-to-end data relationships and touchpoints at two levels of detail: a one-page view for the executive team, and a detailed view that data engineers can build from.
Define the categories of data in motion (customer, supplier, product, finance) and name the system of record, owner and target for each.
Assess how changes elsewhere, such as the Salesforce re-architecture or the decoupling of the raw data layer, affect the plan, and keep it current.
Design Authority for the Oracle Fusion Data Workstream
Represent data at the program's Design Review Board. Review the integrator's conversion strategy, functional designs and mapping templates, and give or withhold data sign-offs.
Resolve ownership gaps, such as shared responsibility for data ETL and for the reporting data model, before they become change orders and scope disputes.
Set data quality exit criteria and reconciliation standards for each conversion cycle, with the Data Governance and Data Quality leads.
Architect coexistence between E-Business Suite and Fusion: chart of accounts mapping, supplier synchronization, calendar reconciliation, FX rate feeds and accounting hub flows.
Own the data sections of the cutover plan, including opening balances, historical data for planning and consolidation tools, and archival of non-converted source data.
Master Data Architecture
Provide architectural oversight of the customer MDM design in Reltio with the implementation partner, including match and merge rule risk, entity hierarchies, and integration with upstream and downstream systems in later phases.
Extend master data architecture to supplier, product and finance hierarchy data, and define how golden records feed Fusion, Salesforce and Snowflake.
Work with the MDM lead and data stewards. This role sets the architecture; day-to-day configuration belongs to the MDM team.
Integration Contracts and the Analytical Boundary
Define data contracts between source systems and the Snowflake Bronze layer, jointly with the Principal Data Architect, Snowflake and Lakehouse Platform.
Provide the architectural recommendation on Oracle's native analytics versus Snowflake Gold layer, and on moving controlled financial (SOX) reporting into Business Systems.
Review integration designs around Fusion, such as payroll, collections, tax and product lifecycle systems, for payload, error handling and data standards.
Governance, Risk and Communication
Maintain the data risk register for the transformation and brief the Data Enablement Decision Group and executive leadership.
Partner with Data Governance, Privacy, Security and Finance controls on access models, retention and SOX evidence in migration and test environments.
State architecture decisions as plain trade-offs that non-technical executives can act on.
Your First 90 Days
Review the integrator's data architecture, the data migration strategy and the coexistence options, and record where you disagree and why.
Validate any architecture work already completed, challenge it where needed, and take ownership of it.
Publish version one of the enterprise data architecture map and walk it through with the Head of Data, the CIO organization and the program leads.
Agree the ownership model for data ETL and the reporting data model, and take it to the design review forum.
Agree a shared data contract template with the Snowflake architect.
How This Role Works With the Snowflake Architect
Two principal architects in the Data Team share one boundary. This role owns the source side: how Fusion, Salesforce and Reltio structure, move and reconcile data, up to a published contract at the Bronze layer. The Principal Data Architect, Snowflake and Lakehouse Platform owns everything from Bronze onward: platform topology, medallion standards, access and cost. The two own the contracts at the boundary together and take unresolved disputes to the Head of Data.
Qualifications
Required Experience
12+ years in data architecture, including at least 5 years leading data design for large, multi-entity ERP migrations or consolidations. Oracle E-Business Suite and Fusion Cloud preferred; SAP S/4HANA or comparable platforms considered.
Hands-on command of conversion data design: extraction, profiling, mapping, cleansing, load and reconciliation across multiple test cycles through cutover.
Experience architecting master data management on a commercial platform (Reltio, Informatica, Stibo, Tamr or similar), including match and merge design and entity hierarchies.
Strong conceptual, logical and physical data modeling across transactional and analytical systems.
Working knowledge of Salesforce data models and integration patterns.
Experience acting as the client-side design authority over a systems integrator or other third-party delivery team.
Working knowledge of cloud data platforms such as Snowflake, and the ELT and lakehouse patterns around them.
Written and spoken communication for executives, with the decision and its trade-offs stated first.
Strong Signal Qualifiers
Oracle Fusion Cloud data conversion using FBDI and HDL, and E-Business Suite coexistence experience.
SOX-aware data design for finance systems.
Experience in a company built through acquisitions, with many ERPs to consolidate.
Grounding in DAMA-DMBOK, DCAM or TOGAF.
Experience in construction, engineering, industrial technology, or a combined hardware and software business.
Global program experience across the Americas, EMEA and APAC.
Employers have access to artificial intelligence language tools (“AI”) that help generate and enhance job descriptions and AI may have been used to create this description. The position description has been reviewed for accuracy and Dice believes it to correctly reflect the job opportunity.
- Dice Id: cxbcsi
- Position Id: Job45158
- Posted 1 hour ago
