MarCom Enablement & Measurement Specialist

Global MarCom is consolidating its work onto Jira as the single operational work-management platform for around 300 users. To run as One MarCom, leadership needs reliable data on what the team is doing, what it costs, and what business value it supports.

Today that information sits in separate systems that do not share common identifiers: the work in Jira, the spend in finance systems, and the value across regional and other corporate functions. This role runs Jira as a well-governed source of truth, and builds the methodology that connects work, spend and value so leadership can make evidence-based decisions.

1. Jira administration, governance and enrichment (80%)

Administration and support

• Administer Jira for approximately 300 users, including boards, workflows, fields, permissions and configurations.

• Provide day-to-day user support and troubleshoot Jira issues.

• Manage access, onboarding and offboarding, and maintain training materials for users and super users (Team Leaders and Jira Leads).

Build and automation

• Build and maintain automations to reduce manual work and improve efficiency.

• Configure intake forms, request types and templates aligned to the MarCom service catalogue.

• Manage configuration changes through a change log and a test-before-release process.

Governance and data quality

• Assist on initiative intake process

• Maintain Jira governance and standards across teams.

• Monitor and improve data quality to ensure reliable reporting.

• Maintain the MarCom taxonomy in Jira, including T1–T5 tier, region, business unit/HGA, client journey stage, client/pursuit tag and initiative type.

• Run regular data-hygiene checks and follow up with owners to close gaps.

Reporting and continuous improvement

• Build and maintain dashboards for teams, Operations and leadership.

• Analyse Jira data to identify bottlenecks, inefficiencies and workflow trends.

• Optimise workflows and processes based on data and user feedback.

• Track operational metrics such as cycle time, throughput, planned/unplanned work and adoption.

• Drive continuous improvement of Jira as the organisation’s operational work-management platform.

2. Cross-platform reconciliation and measurement (20%)

Connect what MarCom does, what it costs and what it influences, including where systems do not share a common key.

Reconcile across datasets

• Work to spend: match Jira initiatives and portfolios to committed spend, purchase orders and actuals.

• Work to value: link Jira initiatives to GCP pursuits, TOPPS and priority clients by client, region, market and client journey stage.

• Spend to value: show cost by initiative, portfolio and tier against the pipeline it supports.

• Other sources: bring in campaign and engagement data, effort/time data and KPI framework inputs as required.

Build the connecting methodology

• Design matching rules where no shared identifier exists, starting with direct tags and moving through defined fallback levels (e.g., client, then region × market × journey stage, then global).

• Apply and document assumptions, including allocation rules, weighting, confidence levels and treatment of unmatched records.

• Label every output as matched, inferred or assumed, and report the share of each.

• Run sensitivity checks to show how far results depend on assumptions.

Close gaps at the source

• Identify root causes of breaks, such as untagged initiatives, purchase orders with no initiative, or pursuits not linked to client records.

• Feed fixes back into Jira governance through required fields, picklists and automations, reducing reliance on inference over time.

Report

• Maintain a reconciled work → spend → value dataset and Power BI view.

• Provide validated inputs to quarterly KPI and Marketing Influence on Growth (MIG) reporting.

• Experience: 3–5 years in Jira administration, PMO, business operations or operational analytics, ideally in a shared-services or GCC environment.

• Jira administration: hands-on Jira Cloud administration, including workflows, schemes, permissions, custom fields, JQL and Automation for Jira.

• Cross-platform reconciliation: proven experience reconciling data across systems that do not share keys, such as work-management, finance and CRM/pipeline data.

• Methodology: able to build and defend a reconciliation approach, including matching logic, allocation rules, weighting and documented assumptions.

• Data skills: advanced Excel and Power Query; Power BI modelling, including joins, mapping tables and data lineage.

• Commercial literacy: understands financial concepts (purchase orders, committed spend, actuals, cost centres) and pipeline concepts (weighted value, stage, win probability). Knowledge of any specific system is secondary.

• Communication: explains clearly which numbers are evidenced and which are estimated; strong written English.

• Mindset: strong attention to detail, governance discipline and a continuous-improvement approach.

Desirable

• Atlassian certification (e.g., Jira Administration).

• Experience with Tempo, Jira Service Management or Confluence.

• Exposure to ERP and CRM data (e.g., Oracle, Microsoft Dynamics).

• SQL or Python for data matching and transformation.

• Experience with marketing attribution or influence modelling.

• Background in marketing, creative or agency operations.

• Lean, Agile or process-improvement experience.