Director Technology - Martech Technology Strategy

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Job Summary", "Key Responsibilities", "Qualifications", "Preferred Qualifications", "Base salary range", "Benefits". Also "About WPP" and EEO etc should be removed. Also "Who We Are" is a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map sections accordingly. We have "Who We Are" - maybe treat as "About the role"? Actually "Who We Are" is about the company, not role. Might be considered "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include sections that have real content. Likely sections: About the role (maybe combine Who We Are + Job Summary?), Responsibilities (Key Responsibilities), Qualifications (Qualifications), Preferred Qualifications maybe as Skills? Or separate? Could treat Preferred Qualifications as Skills. Benefits: we have "We offer a competitive benefits package, click WPP Benefits for more details." That's vague but it's a statement about benefits. It says "We offer a competitive benefits package". That's substantive enough? It says not to include placeholder like "not specified". This is a statement that they offer benefits. Could include Benefits section with that sentence. Pay: we have base salary range: "$100,000 USD - $230,000 USD". That's specific, so include Pay section. Schedule: we have "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. So include Schedule. We should not repeat job title as heading. No Job ID. We need to remove boilerplate: EEO, equal opportunity, application instructions, privacy policy, etc. Also remove "About WPP" and "When you click Submit Application" etc. We need to preserve all substantive information. So we need to include the content from Who We Are, Job Summary, Key Responsibilities, Qualifications, Preferred Qualifications, Pay, Benefits, Schedule. We need to format using

for each section heading, then content: either

for prose,

• for lists. We need to decide what content goes where. Section headings suggestions: - About the role: could combine Who We Are and Job Summary? But Who We Are is about the company, not role. However instruction says use headings like About the role, Responsibilities, etc. So we can put "About the role" heading and include both Who We Are and Job Summary content. - Responsibilities: Key Responsibilities. - Qualifications: Qualifications (required). - Skills: Preferred Qualifications (maybe treat as Skills). - Benefits: Benefits statement. - Pay: Salary range. - Schedule: In-office presence and travel. We need to ensure we don't create sections with filler. All have content. Now we need to extract content. Who We Are paragraph: "WPP Enterprise Solutions designs, builds, and operates the growth systems that competitive businesses rely on. In a world where Al is reshaping how companies drive growth, we lead clients in business transformation and marketing modernization, connecting strategy directly to execution. Our 12,000 experts in engineering and platforms, commerce, consulting, content transformation, CRM, and CX work within a unified global operating unit across 40+ markets. WPP Enterprise Solutions works alongside best-in-class partners including Adobe, AWS, Braze, Google, Microsoft, Salesforce, and Shopify, as well as innovators in AI, to deliver growth solutions tailored to the needs of our clients’ businesses. VML, part of WPP, supports WPP Enterprise Solutions by helping brands activate transformation through creativity and experience." Job Summary paragraph(s): "The Director, Martech Technology Strategy is a senior client-facing role responsible for shaping and leading Mazda North America Operations’ enterprise Martech roadmap. This role sits within Technology Strategy and connects Mazda’s business goals to the technology, data, platform, governance, and operating model decisions needed to drive measurable growth. This leader owns the integrated Martech picture across CDP, CRM, personalization, content operations, taxonomy, media activation, analytics, and data engineering. They translate strategic needs into clear roadmaps, use cases, requirements, and decisions that cross-functional teams and partners can build, operate, and measure. The role will lead Mazda’s audience, segmentation, and taxonomy governance agenda, including the use of Claravine as the operational system of record for naming, metadata, campaign classification, and audience definitions across the Martech ecosystem. At the Director level, this person is expected to be a trusted advisor to senior Mazda stakeholders, making clear recommendations on what to build, buy, partner for, or defer while connecting technology decisions to business outcomes, marketing effectiveness, and customer experience. This role requires a minimum of four days per week in-office presence, with travel to Mazda and key partner locations as needed." Note: The schedule sentence appears also in Job Summary; we will extract schedule later but we can keep it there too? Might duplicate. Better to keep schedule in Schedule section only, but we can still keep it in Job Summary? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove it from Job Summary, we lose that detail unless we put it elsewhere. We can keep it in Job Summary and also have Schedule section? That would duplicate. Better to keep it in Job Summary and not have separate Schedule? But we need Schedule section per instruction if posting actually states them. It does state schedule. So we need a Schedule section. We could keep the schedule sentence in both places? That would be duplication but maybe acceptable? The instruction says preserve ALL substantive information; does not forbid duplication. However better to avoid duplication but still preserve. We could move the schedule sentence to Schedule section and remove from Job Summary. But then we lose it from Job Summary unless we keep a note that schedule is mentioned elsewhere. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we remove it from Job Summary, we are summarizing away detail (removing it). So we need to keep it somewhere. We could keep it in Job Summary and also have Schedule section that repeats it; that preserves detail (though duplicated). That's okay. Alternatively we could keep schedule sentence in Job Summary and not have Schedule section, but then we would not have a Schedule section despite having schedule info. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It does not say we must include Schedule section if schedule info exists; it's optional but we can include if we want. The examples list Schedule as a possible heading. It's not mandatory. So we could omit Schedule section and keep schedule in Job Summary. That would still preserve info. However they said "Prefer a few substantive sections over many thin ones." So maybe better to not create a thin Schedule section; just include schedule in Job Summary. But they also said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That's just examples, not requirement to include all. So we can decide. I'll include sections: About the role (Who We Are + Job Summary), Responsibilities, Qualifications, Skills (Preferred Qualifications), Benefits, Pay. Omit Schedule to avoid thin section. Now we need to format lists. Responsibilities: The Key Responsibilities section has multiple bullet-like paragraphs each starting with a bold heading? Actually the text includes headings like "Technology strategy and roadmap ownership", "CDP strategy, segmentation, and audience orchestration", etc. Each is a subsection with multiple sentences. We could treat each as a list item (

  ) with the content. Or we could keep as prose paragraphs. The instruction: Use

  • for any list of duties/requirements/benefits. The responsibilities are a list of duties, so we should make a
    with each duty as
    • . We need to extract each duty block. Let's parse the Key Responsibilities section: - Technology strategy and roadmap ownership Own 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 a sequenced technology strategy, roadmap, and portfolio of fundable use cases. Provide clear recommendations on build, buy, partner, defer, or stop decisions across the Martech ecosystem. Identify risks, dependencies, trade-offs, and decision points early, and frame them for executive stakeholders in clear business language. - CDP strategy, segmentation, and audience orchestration Lead 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 Lead Mazda’s enterprise taxonomy program, with Claravine serving as the system of record for naming, metadata, campaign classification, and audience definitions. Define 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 Set 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 the senior Martech Technology Strategy voice across Mazda Marketing, Digital, IT, Legal, Data Privacy, Analytics, Media, and executive stakeholders. Coordinate work across VML, WPP Media, WPP Choreograph, Shift Digital, Adobe, TransUnion, Salesforce, and other ecosystem partners. Pair with client and delivery leadership to shape roadmap decisions, maintain trust, and drive alignment 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. Build 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. - Practice leadership and team development Lead and develop Martech Technology Strategy resources supporting Mazda across CDP, CRM, personalization, taxonomy, content pipeline, and orchestration. Set the quality bar for roadmaps, use case maps, operating models, taxonomy frameworks, business requirements, recommendations, and points of view. Build team capability in strategic judgment, executive communication, business analysis quality, and client-facing presence. Contribute reusable frameworks, account learnings, and thought leadership to the broader Technology Strategy practice. We'll make each of these as
    • containing the sentences (maybe as

      inside

    • ? Usually
    • can contain multiple

      . We'll just put the sentences separated by spaces or
      ? Simpler: put the sentences as plain text within

    • , separated by spaces. Now Qualifications: list of bullet points? The qualifications paragraph includes multiple sentences each starting with a qualification. Could treat as list. Qual