Associate Director - Solutions Analyst (MarTech)
WPP Enterprise Solutions · New York, NY · 3 wk ago
HybridInformation Technology$75k/yrFull-time
We need to output HTML fragment with sections only if real content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
We have job summary and description. "Who We Are" is company description; could be "About the role"? Actually "About the role" heading should contain description of role. We'll put job summary and maybe who we are? The instruction: do NOT repeat job title as heading. Use headings for sections. We'll include:
- About the role: combine Who We Are and Job Summary? Probably "About the role" should describe the role and company context. We'll include the Who We Are paragraph and Job Summary.
- Responsibilities: list of key responsibilities bullet points.
- Requirements: maybe qualifications? Actually Qualifications heading for required qualifications. We'll have Qualifications for required qualifications.
- Skills: maybe not separate; we could combine skills within qualifications. But we can include Skills heading if there are specific skills listed. The qualifications list includes many skills/experience. Could treat as Requirements? The instruction: Use headings as given; we can decide which sections have content.
We have Pay: base salary range indicated: $75,000 USD - $180,000 USD. So we need a Pay section with that.
Schedule: "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.
Benefits: "We offer a competitive benefits package, click WPP Benefits for more details." That's benefits info.
Thus we have sections: About the role, Responsibilities, Requirements (maybe Qualifications), Qualifications (maybe separate?), Skills (maybe not needed), Benefits, Pay, Schedule.
But we should avoid thin sections. Could combine Qualifications and Skills into one? But we have both headings allowed. We could put Qualifications for required qualifications, and Skills for preferred qualifications? Actually preferred qualifications are listed under "Preferred Qualifications". Could treat as Skills. But we have both Qualifications and Skills headings; we can put required under Qualifications, preferred under Skills.
Thus:
. Could group under subheadings? Not allowed; only .
Skills (preferred qualifications):
From "Preferred Qualifications":
- Experience in automotive, retail, financial services, or another multi-tier, data-intensive industry.
- Experience with Mazda, MNAO, or automotive manufacturer / dealer ecosystem operating models.
- Adobe certification or equivalent expertise across AEP, RT-CDP, AJO, CJA, AEM, or Adobe Target.
- Experience with Claravine, Domo, TransUnion, LiveRamp, The Trade Desk, DV360, Meta, Google Ads, Salesforce CRM, or WPP Open.
- Experience designing taxonomy councils, governance models, change management processes, and platform adoption frameworks.
- Working knowledge of privacy, consent, profile stitching, deletion chain, and audience activation considerations.
- Experience with content supply chain or creative automation platforms such as Adobe Workfront, GenStudio, Frame.io, Bynder, or Brandfolder.
- Advanced degree in a related field.
We'll list each as .
Now About the role: combine Who We Are paragraph and Job Summary paragraph.
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: "The Associate Director, Martech Technology Strategy is a client-facing role responsible for supporting and advancing Mazda North America Operations’ enterprise Martech roadmap under the direction of senior Technology Strategy leadership. This role sits within Technology Strategy and helps connect Mazda’s business goals to the technology, data, platform, governance, and operating model decisions needed to drive measurable growth. This role helps manage the integrated Martech picture across CDP, CRM, personalization, content operations, taxonomy, media activation, analytics, and data engineering. They translate strategic direction into clear use cases, requirements, workstream plans, governance inputs, and decision support that cross-functional teams and partners can build, operate, and measure. The role supports 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 Associate Director level, this person is expected to be a strong day-to-day strategy partner to Mazda stakeholders and internal delivery teams, helping shape recommendations, clarify trade-offs, and prepare decisions for senior client and agency leadership. 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; but we also have Schedule section. We'll keep schedule info in Schedule section; but we might duplicate. However instruction: preserve ALL substantive information; duplication okay? Might be okay but we could keep it only in Schedule section and remove from About the role to avoid duplication. However the Job Summary includes that sentence; if we remove it, we lose that info from About the role. But we have Schedule section covering it. The instruction: preserve ALL substantive information; we can keep it in Schedule section and not repeat in About the role. But we need to ensure we don't lose any info. The schedule sentence appears also in Job Summary; we could keep it in About the
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
We have job summary and description. "Who We Are" is company description; could be "About the role"? Actually "About the role" heading should contain description of role. We'll put job summary and maybe who we are? The instruction: do NOT repeat job title as heading. Use headings for sections. We'll include:
- About the role: combine Who We Are and Job Summary? Probably "About the role" should describe the role and company context. We'll include the Who We Are paragraph and Job Summary.
- Responsibilities: list of key responsibilities bullet points.
- Requirements: maybe qualifications? Actually Qualifications heading for required qualifications. We'll have Qualifications for required qualifications.
- Skills: maybe not separate; we could combine skills within qualifications. But we can include Skills heading if there are specific skills listed. The qualifications list includes many skills/experience. Could treat as Requirements? The instruction: Use headings as given; we can decide which sections have content.
We have Pay: base salary range indicated: $75,000 USD - $180,000 USD. So we need a Pay section with that.
Schedule: "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.
Benefits: "We offer a competitive benefits package, click WPP Benefits for more details." That's benefits info.
Thus we have sections: About the role, Responsibilities, Requirements (maybe Qualifications), Qualifications (maybe separate?), Skills (maybe not needed), Benefits, Pay, Schedule.
But we should avoid thin sections. Could combine Qualifications and Skills into one? But we have both headings allowed. We could put Qualifications for required qualifications, and Skills for preferred qualifications? Actually preferred qualifications are listed under "Preferred Qualifications". Could treat as Skills. But we have both Qualifications and Skills headings; we can put required under Qualifications, preferred under Skills.
Thus:
About the role
Who We Are ... (the paragraph) ... Job Summary ... (the paragraph)
Responsibilities
- ... each responsibility bullet ...
Qualifications
- ... required qualifications bullet list ...
Skills
- ... preferred qualifications bullet list ...
Benefits
We offer a competitive benefits package, click WPP Benefits for more details.
Pay
The base salary range for this position at the time of this posting is $75,000 USD - $180,000 USD.
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 must ensure we preserve all substantive information. Need to include all responsibilities bullet points exactly as given. Let's extract them. From "Key Responsibilities" section: - 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 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 need to preserve all. We'll put each bullet as