Director Technology - Solutions Analyst (MarTech)

We need to output only HTML fragment with sections for headings that have real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive information. We need to decide which sections to include based on content. From posting: - Who We Are (company description) maybe not needed as a heading? Could be part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content. We have: - Job Summary (description of role) could be "About the role". So we can put that under

About the role

with paragraphs. - Key Responsibilities: list of responsibilities, we can put under

Responsibilities

with

• . - Qualifications: there is a "Qualifications" section with bullet-like paragraphs. Also "Preferred Qualifications". Could combine under Requirements? The instruction includes Requirements and Qualifications as separate possible headings. We have qualifications (required) and preferred qualifications. Could put required under

  Qualifications

  and preferred under maybe

  Preferred Qualifications

  but not in list of allowed headings? The allowed list includes Qualifications, Skills, etc. Not Preferred Qualifications. Could treat preferred qualifications as part of Qualifications or Skills. Might be better to put under Qualifications (including both required and preferred) or separate Skills? The instruction says prefer a few substantive sections over many thin ones. So we can combine required and preferred into Qualifications section. - Skills: not explicitly listed separate; but we could extract skills from qualifications (knowledge of Martech ecosystems, experience with certain platforms, etc.) Could put under Skills. - Pay: The posting includes base salary range: "$100,000 - $230,000 USD". Also mentions competitive benefits package. So we can include Pay section with that range. - Benefits: mention "We offer a competitive benefits package, click WPP Benefits for more details." That's substantive? It's a statement but not detailed. Could include Benefits section with that sentence. - Schedule: mentions "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 we can include Schedule section. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay, Benefits, Schedule. We must not include empty sections. Now we need to extract content. About the role: Use Job Summary paragraph(s). The Job Summary includes multiple sentences. We'll put as

  ...

  . Responsibilities: list from "Key Responsibilities" bullet points. Each bullet is a sentence or multiple sentences. We'll create
  • each bullet. Qualifications: combine required and preferred qualifications. Required qualifications list: Bachelor’s degree..., 8+ years..., Experience owning..., Strong knowledge..., Experience with Adobe..., Experience defining audience..., Proven ability..., Excellent written..., etc. Preferred qualifications list: Experience in automotive..., Experience with Mazda..., Adobe certification..., Experience with Claravine..., Experience designing taxonomy councils..., Working knowledge of privacy..., Experience with content supply chain..., Advanced degree... We'll put each as
  • under Qualifications? The instruction says use
    • for any list of duties/requirements/benefits. So Qualifications is a list of requirements, so we can use
      • . Similarly Skills could be a list. But we already used Qualifications for list; Skills could be another list of specific skills (like platforms). However to avoid thin sections, maybe we combine Qualifications and Skills into one Qualifications section. But the instruction allows Skills heading. However we prefer few substantive sections. Could we put skills inside Qualifications? Might be okay. But we need to follow instruction: Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both Qualifications and Skills. But we should avoid thin sections. If we split, we might have thin Skills section with just a few items. Could combine. I'll decide to have Qualifications (including required and preferred) and not separate Skills. That satisfies having a few substantive sections. Now Pay: include the salary range. Benefits: include statement about competitive benefits package. Schedule: include in-office presence and travel. Now we need to ensure we don't include boilerplate like "About WPP", equal opportunity, privacy policy, application instructions, etc. Remove those. Also remove "Who We Are" maybe not needed as a section; but we could incorporate into About the role? The "Who We Are" is company description; not required but could be part of About the role? The instruction says About the role heading for role description. Could we include company description under About the role as well? Might be okay but could be considered not role-specific. However we can keep it as part of About the role to preserve substantive information. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the Who We Are paragraph. Where to put? Could be part of About the role section as introductory paragraph. That seems fine. Thus About the role section will contain both Who We Are and Job Summary. Now we need to ensure we don't repeat job title as heading. Not using. Now produce HTML fragment:

        About the role

        Who We Are 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 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.

        But note schedule info is also in About the role; we might move schedule to its own section. Better to keep schedule separate. So we should remove schedule sentence from About the role and put in Schedule section. Thus About the role will exclude the schedule sentence. Now Responsibilities: list each bullet. We need to extract bullet points from "Key Responsibilities". They are: - 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 need to turn each bullet into
      • . Could group under subheadings? Not allowed; only

        headings. So we just list all responsibilities as

        items. That will be a long list but okay. Now Qualifications: list required and preferred. Required qualifications bullet points: - Bachelor’s degree in Computer Science, Information Systems, Marketing, Business, Strategy, or a related field. - 8+ years of experience in technology strategy, marketing technology strategy, digital transformation, business architecture, consulting, or enterprise platform strategy. - Experience owning or shaping enterprise technology roadmaps across multiple teams, platforms, and stakeholders. - Strong knowledge of Martech ecosystems, including CDP, CRM, personalization, analytics, customer journey