Associate Director - Martech Technology Strategy

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" and "Job Summary". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to decide which sections to include based on content. We have "Who We Are" - that's about the company, not necessarily a required heading. Could be "About the role"? Actually "Who We Are" is about the company, not role. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if posting has real specific content. We have Job Summary (description). Could map to "About the role". We have Key Responsibilities (list). That's Responsibilities. We have Qualifications (list). That's Qualifications. We have Preferred Qualifications (maybe also Qualifications or separate? Could combine under Qualifications but we could have a separate section? The instruction only lists certain headings; we could put both under Qualifications (maybe separate subheadings not allowed). Better to include Qualifications and maybe "Preferred Qualifications" as part of Qualifications? But we could also include a "Skills" section? Not explicitly present. There's also Pay: they gave salary range. So we should include Pay section with that range. Benefits: they mention "competitive benefits package, click WPP Benefits for more details." That's vague; not specific benefits. The instruction says never create Benefits section unless posting actually states them. It states "We offer a competitive benefits package, click WPP Benefits for more details." That's not specific benefits; it's a generic statement. Likely we should not create Benefits section because it's not specific. Schedule: they mention "This role requires a minimum of four days per week in-office presence, with travel to Mazda and key partner locations as needed." That's schedule info (in-office requirement). So we can include Schedule section. Thus sections: About the role (Job Summary), Responsibilities (Key Responsibilities), Qualifications (Qualifications + Preferred Qualifications maybe combined), Pay (salary range), Schedule (in-office requirement). Possibly also "Skills"? Not needed. We must not include boilerplate like Who We Are, About WPP, EEO, etc. Remove those. We must preserve all substantive information. So we need to include the content from Job Summary, Responsibilities, Qualifications, Preferred Qualifications, Pay, Schedule. We need to format Responsibilities as

• each bullet. The responsibilities list is long with many bullet-like sentences separated by periods. We need to parse them into list items. The original "Key Responsibilities" section includes multiple paragraphs each starting with a bold heading? Actually they have headings like "Technology strategy and roadmap ownership", then sentences. We should treat each sentence or clause as a list item? The instruction: Use
  • for any list of duties/requirements/benefits. The posting already has a list of responsibilities but not formatted as bullet list; it's paragraphs with bold headings. We should convert each distinct responsibility into a list item. Likely each bold heading plus its description could be one list item, but we could split further. To preserve all substantive information, we can keep the text as is within
  • elements, maybe each heading as a separate
  • . Let's extract each heading and its following sentences until next heading. Headings: 1. Technology strategy and roadmap ownership - Support the end-to-end Mazda Martech roadmap across CDP, CRM, personalization, content operations, taxonomy, analytics, media activation, and data engineering. - Translate Mazda’s business priorities and customer experience goals into workstream plans, requirements, roadmap inputs, and fundable use case detail. - Develop analysis and recommendation materials to support build, buy, partner, defer, or stop decisions across the Martech ecosystem. - Identify risks, dependencies, trade-offs, and decision points early, and escalate them with clear context and recommended paths forward. 2. CDP strategy, segmentation, and audience orchestration - Support strategy and ongoing optimization for Mazda’s Adobe Experience Platform and Real-Time CDP program. - Define audience frameworks, lifecycle segmentation, suppression logic, activation requirements, and measurement expectations. - Ensure audience definitions are consistent across CRM, paid media, personalization, analytics, and reporting. - Partner with data engineering and platform teams to validate feasibility, data readiness, identity logic, and activation dependencies. 3. Enterprise taxonomy and governance - Support Mazda’s enterprise taxonomy program, with Claravine serving as the system of record for naming, metadata, campaign classification, and audience definitions. - Help define and maintain governance standards across Claravine, Adobe Experience Platform, Real-Time CDP, AJO, AEM, CJA, Salesforce Marketing Cloud, media platforms, WPP Open, Domo, and reporting tools. - Establish naming conventions, metadata standards, decision rights, approval processes, versioning, and change management for taxonomy and audience governance. - Ensure taxonomy supports activation, reporting, measurement, personalization, AI classification, and long-term scalability. 4. CRM, personalization, and journey orchestration - Support the strategic direction for Mazda’s CRM and personalization roadmap across owned channels and customer journeys. - Translate priority moments into use cases with clear owners, dependencies, triggers, suppression rules, success metrics, and platform implications. - Connect segmentation strategy to measurable outcomes such as lead quality, conversion, service engagement, loyalty, retention, and sales lift. 5. Cross-agency orchestration and stakeholder leadership - Serve as a Martech Technology Strategy partner across Mazda Marketing, Digital, IT, Legal, Data Privacy, Analytics, Media, and related stakeholder groups. - Coordinate work across VML, WPP Media, WPP Choreograph, Shift Digital, Adobe, TransUnion, Salesforce, and other ecosystem partners. - Partner with client, strategy, and delivery leadership to support roadmap decisions, maintain alignment, and build trust across teams. - Facilitate workshops, roadmap reviews, retrospectives, and executive alignment sessions that turn complex inputs into a clear plan. 6. Measurement, value realization, and business impact - Define the measurement framework for CDP, CRM, personalization, media activation, taxonomy, and content orchestration. - Partner with analytics and reporting leads to connect platform activity to business outcomes. - Support value-realization narratives for executive forums, steering committees, quarterly business reviews, and roadmap funding conversations. - Identify opportunities for influenced revenue, expanded scope, reusable assets, partner motion, and broader WPP Enterprise Solutions value creation for review with senior leadership. 7. Practice contribution and team support - Provide day-to-day guidance and support to Martech Technology Strategy resources across CDP, CRM, personalization, taxonomy, content pipeline, and orchestration as assigned. - Help maintain the quality bar for roadmaps, use case maps, operating models, taxonomy frameworks, business requirements, recommendations, and points of view. - Mentor supporting team members in business analysis quality, stakeholder communication, platform context, and client-facing delivery practices. - Contribute reusable frameworks, account learnings, and thought leadership to the broader Technology Strategy practice. We could combine each heading's bullet points into a single
  • containing multiple sentences, but that might be less semantic. However instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid multiple sentences inside
    • . So we could make each heading a
    • with its sub-points as separate sentences within same
    • . That preserves all info. Similarly for Qualifications: we have bullet list of qualifications (required) and preferred qualifications. We'll combine required qualifications into a
      • list; preferred qualifications maybe also as
        • under same Qualifications section? Could separate into two sublists but still under Qualifications heading. We'll just make one list with all qualifications (required and preferred) but maybe differentiate? Better to keep required as list, then a note "Preferred qualifications:" then another list. But we can't add extra headings not allowed. Could embed as

          Preferred qualifications: ...

          then list. That's okay. Pay: we have salary range: "$75,000 USD - $180,000 USD". We'll put in

          under Pay section. Schedule: "This role requires a minimum of four days per week in-office presence, with travel to Mazda and key partner locations as needed." We'll put in

          under Schedule. About the role: Job Summary paragraph(s). We'll put in

          under About the role. We must not include Who We Are, About WPP, EEO, etc. Now produce HTML fragment:

          About the role

          ...Job Summary text...

          Responsibilities

          • Technology strategy and roadmap ownership: Support the end-to-end Mazda Martech roadmap across CDP, CRM, personalization, content operations, taxonomy, analytics, media activation, and data engineering. Translate Mazda’s business priorities and customer experience goals into workstream plans, requirements, roadmap inputs, and fundable use case detail. Develop analysis and recommendation materials to support build, buy, partner, defer, or stop decisions across the Martech ecosystem. Identify risks, dependencies, trade-offs, and decision points early, and escalate them with clear context and recommended paths forward.
          • CDP strategy, segmentation, and audience orchestration: Support strategy and ongoing optimization for Mazda’s Adobe Experience Platform and Real-Time CDP program. Define audience frameworks, lifecycle segmentation, suppression logic, activation requirements, and measurement expectations. Ensure audience definitions are consistent across CRM, paid media, personalization, analytics, and reporting. Partner with data engineering and platform teams to validate feasibility, data readiness, identity logic, and activation dependencies.
          • Enterprise taxonomy and governance: Support Mazda’s enterprise taxonomy program, with Claravine serving as the system of record for naming, metadata, campaign classification, and audience definitions. Help define and maintain governance standards across Claravine, Adobe Experience Platform, Real-Time CDP, AJO, AEM, CJA, Salesforce Marketing Cloud, media platforms, WPP Open, Domo, and reporting tools. Establish naming conventions, metadata standards, decision rights, approval processes, versioning, and change management for taxonomy and audience governance. Ensure taxonomy supports activation, reporting, measurement, personalization, AI classification, and long-term scalability.
          • CRM, personalization, and journey orchestration: Support the strategic direction for Mazda’s CRM and personalization roadmap across owned channels and customer journeys. Translate priority moments into use cases with clear owners, dependencies, triggers, suppression rules, success metrics, and platform implications. Connect segmentation strategy to measurable outcomes such as lead quality, conversion, service engagement, loyalty, retention, and sales lift.
          • Cross-agency orchestration and stakeholder leadership: Serve as a Martech Technology Strategy partner across Mazda Marketing, Digital, IT, Legal, Data Privacy, Analytics, Media, and related stakeholder groups. Coordinate work across VML, WPP Media, WPP Choreograph, Shift Digital, Adobe, TransUnion, Salesforce, and other ecosystem partners. Partner with client, strategy, and delivery leadership to support roadmap decisions, maintain alignment, and build trust across teams. Facilitate workshops, roadmap reviews, retrospectives, and executive alignment sessions that turn complex inputs into a clear plan.
          • Measurement, value realization, and business impact: Define the measurement framework for CDP, CRM, personalization, media activation, taxonomy, and content orchestration. Partner with analytics and reporting leads to connect platform activity to business outcomes. Support value-realization narratives for executive forums, steering committees, quarterly business reviews, and roadmap funding conversations. Identify opportunities for influenced revenue, expanded scope, reusable assets, partner motion, and broader WPP Enterprise Solutions value creation for review with senior leadership.
          • Practice contribution and team support: Provide