Director Technology - Solutions Analyst (MarTech)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples. We need to decide which headings to use based on content. We have: Who We Are (company overview) maybe not needed as heading? Could be "About the role" but we have "Job Summary". Could use "About the role" for job summary. Or we could use "Job Summary" as heading? The examples list "About the role". Probably better to use "About the role" for the job summary paragraph. Then "Responsibilities" for key responsibilities. Then "Qualifications" for qualifications (maybe combine required and preferred?). Could separate "Qualifications" and "Preferred Qualifications" but they said prefer few substantive sections over many thin ones. Could combine both under Qualifications with subheadings? But we must use only for section headings; we could have multiple sections. Could have "Qualifications" and then within that we can have
sections. Could have "Qualifications" and then within that we can have
for required and then maybe a
for preferred. Or we could have separate sections: "Qualifications" and "Preferred Qualifications". That's two sections; still okay. But they said prefer few substantive sections over many thin ones. However we have a lot of content; splitting into Responsibilities, Qualifications, Preferred Qualifications, Benefits, Pay, Schedule seems fine. We also need to include "Who We Are" maybe as a brief intro? Could be part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have a heading "About the role" that includes the Who We Are and Job Summary? Might be okay. But we need to preserve all substantive information. So we need to include Who We Are text somewhere. Could put it under a heading "About the company" but not in list. Since they didn't list that as example, but we can still use
for any section heading; they gave examples but not exclusive. Safer to use "About the role" for job summary and maybe include Who We Are as a preceding paragraph without heading? But we need to output only HTML fragment; we can include
for Who We Are before any heading. That's acceptable. Thus structure:
Who We Are ...
About the role
Job Summary ...
Responsibilities
- ... each responsibility as list items.
- ? But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. Could do nested
- inside
- . That would preserve structure. Similarly for Qualifications: list of bullet points? The qualifications are a paragraph with sentences separated by periods. Could treat each sentence as
- . But maybe better to keep as
for prose. However they said use
- for any list of duties/requirements/benefits. Qualifications is a list of requirements; could be list. We'll make
- for each qualification sentence.
Preferred Qualifications similarly.
Pay: we can put
with salary range. Schedule:
with in-office requirement. Benefits:
with statement. We must not include boilerplate like EEO, etc. We must output only HTML fragment, no markdown fences. Let's craft. First, Who We Are paragraph: "WPP Enterprise Solutions designs, builds, and operates the growth systems that competitive businesses rely on. In a world where AI 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." Now About the role heading with Job Summary paragraph: "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 sentence appears here; we might want to move schedule to its own section. However the instruction says include schedule section only when posting actually states them. It does state it. We could still keep it in About the role but better to move to Schedule section. However we must preserve all information; moving is fine. We'll remove schedule sentence from About the role and put in Schedule section. Thus About the role paragraph will exclude the schedule sentence. Now Responsibilities section: We'll create
- with each top-level bullet as
- . Inside each
- we can have
- for sub-bullets.
Let's extract:
1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
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.
- 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.
7. 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.
Now Qualifications section: list each sentence.
Qualifications text:
"Bachelor’s degree in Computer
- for each qualification sentence.
Preferred Qualifications similarly.
Pay: we can put
- for any list of duties/requirements/benefits. Qualifications is a list of requirements; could be list. We'll make