RevOps Systems & Integration Lead, Totara Learning

• Strong CRM experience. HubSpot experience strongly preferred, as HubSpot is and will remain the primary source of data
• Hands-on experience with at least one iPaaS, Master Data Management or ETL/ELT platform (for example Workato, Celigo, Boomi, Tray.io, Informatica, MuleSoft or Syncari). Syncari-specific experience is not required, and structured onboarding and ramp-up time will be provided
• Experience modelling data for business intelligence so that reporting is simple and reliable. Power BI is the target
• Experience working across business and technical teams, and owning problems end to end
• Experience administering or supporting business systems, and acting as a liaison with external vendors
• Demonstrable bias for simplicity: able to show where complexity was removed, not only where it was built
• Able to explain complex systems simply to non-technical stakeholders
• Fixes root causes rather than symptoms, and challenges unnecessary tooling, including whether Syncari is warranted for a given job
• Strong collaboration and influence without formal authority, able to align independent system owners
• Working knowledge of APIs, integrations and data mapping
• Strong documentation discipline, producing material that is lean, accessible and maintained
• 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

Desirable

• The RevOps Systems & Integration Lead owns how data moves across Totara's commercial stack
• Accountability for this is currently fragmented: HubSpot has an owner, other tools do not, and data is often corrected downstream rather than at source
• That rework grows as the business grows
• This role creates a single accountable owner for the data layer, making data trustworthy, documented, native-first and reportable end to end, with the least complexity that works
• The role sits within Revenue Operations and works across Finance, Commercial, Customer Delivery and Product
• It owns Syncari, the integration and data layer, and sets the cross-system data standards that other system owners work to
• It also takes technical ownership of commercial tools that currently lack an internal owner, starting with Sage and ProjectWorks
• The role does not administer HubSpot, which has an existing owner, and does not build BI reports, which are produced by others
• It owns the modelled data those reports sit on, and it sets the data standards HubSpot must meet as the primary source, agreed with the HubSpot owner
• The guiding principle is to fix defects at source rather than downstream
• Syncari rules are the fallback, not the default, and a system that nobody understands is treated as a defect
• To make that work, the role carries a mandate, backed by the Global Director, Revenue Operations, to require changes in source systems owned by others
• Data platform and integration ownership (35 to 40%)
• Own Syncari administration and the rules governing what data flows where
• Own cross-system data standards: format, mapping, deduplication and conflict handling
• Define, implement and document account hierarchy and parent-child mapping rules, aiming for one clear rule set rather than a growing list of per-case exceptions
• Build deduplication and cleansing controls source first, working upstream with system owners. Add rules in Syncari only where source-side control is not feasible
• Connect Athena (product usage data) into Syncari and ensure it flows into Power BI and HubSpot in the correct format, with conflicts handled
• Within the first 30 to 60 days, review the Syncari roadmap and integration backlog and propose the approach and priority order for outstanding integration work, including Athena and ProjectWorks, for confirmation by the Global Director, Revenue Operations, and CFO before implementation begins
• Data modelling for reporting (20 to 25%)
• Own the modelled data layer feeding Power BI, structuring data so that key business reporting is simple and reliable
• Ensure CRM, finance, project and product usage data reconcile across systems
• Note: this is data modelling, not report building. Report building is done by others; this role owns the modelled data underneath
• System ownership and support for tools without an internal owner (15 to 20%)
• Act as technical owner for commercial tools that lack an internal owner, initially Sage
• Provide system knowledge, first-line support and vendor liaison for ProjectWorks (our resource planning tool)
• Systematise routine administration so that it can be minimised or delegated over time, rather than growing
• Work with IT on access, security and compliance, and ensure changes are controlled and tested
• Documentation and enablement (10 to 15%)
• Document the systems and the data flows, kept simple enough for non-specialists to follow
• Make clear to each system administrator what must stay stable and the operating rules that keep data working downstream
• Maintain documentation in a single source of truth, reviewing and sunsetting outdated material
• Support training and knowledge sharing so that system understanding is not held by one person
• Acquisition onboarding and exit readiness (5 to 10%)
• As Totara acquires businesses, onboard their tools into the stack, kept to the minimum needed
• Support the data room and analytics layer for due diligence. The Global Director, Revenue Operations, and CFO hold the strategic judgement calls on scope and priority; this role executes against their direction
• What success looks like?
• Data is consistent and trusted across systems, and business teams use it without manual workarounds
• Downstream cleansing shrinks over time rather than growing, because defects are fixed at source
• Key business reporting in Power BI sits on a stable, documented, modelled data layer
• Account hierarchy is governed by one clear rule set, not a growing list of exceptions
• Systems and data flows are documented well enough for non-specialists to follow, and no system depends on one person's memory
• Integrations are delivered reliably and to an agreed priority order
• Data is available and reliable for due diligence when required