Master Data & Integration Lead: Commercial Systems in London

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 explainably across HubSpot, 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.

What you will own

• Master data integrity
  • 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.
• Account identity, hierarchy and mapping
  • 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 HubSpot, 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.
• Syncari and integration ownership
  • 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.
• Source‑system controls
  • HubSpot has an existing technical owner, and other systems may have their own administrators. You will not take over every connected platform.
  • Agree the cross‑system data standards that each source must meet.
  • Work with system owners to implement appropriate upstream controls.
  • Identify where a source‑system change is preferable to another downstream correction.
  • Provide clear requirements covering fields, formats, identifiers, relationships and behaviours that must remain stable.
  • Escalate repeated upstream defects where they are creating avoidable downstream work.
  • Help system owners understand how their changes affect the wider data flow.
  • You will have the backing of the Global Director, Revenue Operations when cross‑system standards require agreed changes within source platforms.
• Modelled data for reporting
  • You will own the modelled data layer supporting Power BI and other business reporting.
  • Structure data so that reporting teams can build reliable measures and reports without repeatedly repairing or reinterpreting the underlying data.
  • Define stable relationships, keys, dimensions and shared business definitions.
  • Ensure reporting data can be reconciled to the appropriate operational source.
  • Document the model and the logic applied to it.
  • Work with report builders and business stakeholders to understand their data requirements.
• Documentation and change control
  • You will document the systems, data flows and operating rules so that they are understandable and maintainable.
  • End‑to‑end system and data‑flow diagrams.
  • Entity and attribute mappings.
  • Source‑authority decisions.
  • Account hierarchy and matching rules.
  • Transformation and validation logic.
  • Known constraints and approved exceptions.
  • Testing, release and rollback procedures.
  • Ownership and escalation routes.
  • The expected impact of proposed schema or system changes.

What you will bring

• Hands‑on experience building and operating production data integrations using Syncari or a comparable Master Data Management or Integration Platform as a Service platform. Relevant examples could include Workato, Boomi, Celigo, Tray.ai, MuleSoft, SnapLogic, Reltio, Profisee, Semarchy or Informatica.
• Demonstrable ownership of customer, account or other master data shared across multiple operational systems.
• Experience defining or implementing account matching, hierarchy, source‑authority, deduplication, mapping and conflict‑resolution rules.
• Experience personally configuring mappings, transformations, validation, error handling, monitoring and reconciliation; not solely consuming an integration built by someone else.
• Experience integrating a major Customer Relationship Management platform with finance, product or other operational systems.
• A strong understanding of data modelling and how operational data should be structured for reliable Business Intelligence reporting.
• The ability to investigate data problems methodically and distinguish their root cause from their visible downstream symptoms.
• Strong communication skills and the ability to align independent system owners without relying solely on formal authority.
• Evidence that you can simplify an existing system, not only build new capability.

Experience with any of the following would be helpful:

• Syncari.
• HubSpot as a connected Customer Relationship Management platform.
• Sage or another finance or Enterprise Resource Planning system.
• Power BI and semantic or dimensional data modelling.
• Structured Query Language.
• Application Programming Interfaces, webhooks and authentication methods such as OAuth.
• Custom connectors, scripting or cloud‑data platforms.
• Product‑usage or telemetry data.
• Data onboarding following an acquisition.
• Lean or Six Sigma improvement methods.

The right person will:

• Prefer the least complex solution that reliably meets the need.
• Use native and default platform capability before reaching for custom development.
• Fix defects at source rather than building permanent downstream workarounds.
• Make explicit decisions about ownership, authority and exceptions.
• Test changes before releasing them and confirm that the expected outcome occurred.
• Treat monitoring, reconciliation and documentation as part of the solution.
• Explain complex systems in plain language.
• Challenge unnecessary tooling and integration.
• Build systems that other people can understand and safely maintain.

Perks and Benefits

• Enhanced Parental Leave
• Private Healthcare
• Life Insurance 4x Salary
• Professional Development Opportunities
• Annual Wellbeing Allowance
• New Joiner home working set‑up allowance
• Additional Paid Leave: Birthday off, Working days between Christmas and New Years Eve

At Totara, we believe diverse perspectives make us stronger. We welcome applications from people of all backgrounds and experiences. If you're excited about this opportunity but don't meet every requirement, we'd still love to hear from you. We hire based on skills, leadership, potential and the unique experiences people bring to our team.