Master Data & Integration Lead: Commercial Systems

Totara is a global learning platform trusted by more than 1,500 organisations and 21 million users worldwide. We help organisations build workforce readiness through flexible learning, compliance, and talent development solutions designed for complex and highly regulated environments across both the public and private sectors.

Totara is building a connected and trustworthy data foundation across its commercial, finance and product systems. Today, responsibility for how data is defined and moved between these systems is fragmented. This creates inconsistencies, manual reconciliation and repeated downstream corrections. As Totara grows, including through acquisitions, these problems will become more costly unless we address them at source.

We are therefore looking for a hands-on Master Data & Integration Lead to own the integrity of shared commercial data across our systems.

You will define what constitutes an account, how records are matched, how parent-child account hierarchies are formed, which system is authoritative for each attribute and how data is mapped and synchronised between systems. You will then implement these rules through Syncari and the connected systems, monitor whether they are working and work with individual system owners to prevent defects from being created.

Moving data successfully from one system to another is not enough. Success means that the same customer, account and relationship is represented consistently, accurately and explain ably across Hub Spot, Sage, product systems and the reporting layer. This is a hands-on Master Data Management and integration role. It is not a general Revenue Operations, Customer Relationship Management administration or report-building position.

You will be accountable for the integrity of shared commercial data across Totara’s connected systems.

This will include:

• Defining the shared data model, terminology and standards used across systems.
• Determining which system is authoritative for each entity and attribute.
• Defining validation, standardisation, matching, deduplication and conflict-resolution rules.
• Establishing how trusted values survive when different systems contain conflicting information.
• Monitoring data-quality failures and identifying their underlying causes.
• Working with system owners to introduce controls that prevent defects at source.
• Making data ownership and decision-making clear enough that non-specialists can understand them.
• Ensuring that downstream cleansing and manual reconciliation reduce over time rather than becoming permanent processes.

A major early responsibility will be establishing how Totara represents organisations and relationships between them.

• Define what Totara means by an account, customer, legal entity, logo, location, parent and ultimate parent.
• Establish the rules used to determine whether records in different systems represent the same organisation.
• Design and maintain parent-child account hierarchy rules.
• Define how account identifiers and relationships map across Hub Spot, Sage, product systems, acquired businesses and the reporting layer.
• Establish matching, merging and survivorship rules for duplicate or conflicting records.
• Determine how changes such as acquisitions, mergers, restructures and account moves should be handled.
• Create a controlled approach to genuine exceptions without allowing a growing collection of undocumented, case-by-case rules.
• Ensure hierarchy and mapping decisions are traceable, testable and consistently applied.

You will own the day-to-day administration and development of Syncari and the rules governing how data flows between systems.

• Configure, test, publish and monitor Syncari pipelines.
• Manage entity, object and attribute mappings.
• Implement source-authority, transformation, validation and conflict-handling rules.
• Design appropriate one-way and bidirectional data flows.
• Monitor synchronisation activity, exceptions and platform health.
• Investigate failed transactions, mismatched records, authentication problems, schema changes and Application Programming Interface limitations.
• Reconcile data between source and destination systems and confirm that integrations have produced the intended result.
• Use native connectors and standard platform capability wherever practical.
• Challenge whether Syncari is required for a particular use case rather than automatically adding another integration or rule.