Technical Lead, Customer Data & Personalization Platforms

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. The posting text: "Lead the technical strategy and engineering of core MarTech data platforms, including Customer Data Platforms (CDP), Identity Resolution, Data Clean Rooms Customer Lake architectures, and AI-ready data products. This role is responsible for building the trusted, scalable, and privacy-first data foundations that enable modern marketing, performance marketing, personalization at scale, audience activation, customer intelligence, and GenAI-powered experiences. These capabilities power Marketing 360 (M360) and the next generation of intelligent, data-driven marketing solutions across Vanguard. Core Responsibilities Provide technical leadership for Vanguard's MarTech Data Platform ecosystem, including Customer Data Platforms (CDP), Identity Resolution, Data Clean Rooms, customer data assets, and activation platforms that power modern marketing and personalization at scale.Lead the architecture, design, and delivery of scalable, secure, and governed data solutions, ensuring reliability, performance, and operational excellence across the platform landscape.Drive engineering best practices across data architecture, DataOps, observability, CI/CD, testing, security, and platform operations.Partner closely with Product, Marketing, Analytics, AdTech, and Engineering teams to translate business objectives into durable, scalable technical solutions.Provide technical oversight for the full solution lifecycle, including architecture reviews, design decisions, implementation, testing, deployment, and ongoing optimization.Establish and enforce data governance, privacy, security, and compliance standards for customer and identity data, ensuring alignment with enterprise and regulatory requirements.Evaluate emerging technologies and platform capabilities, developing roadmaps and recommendations that advance Vanguard's marketing, customer intelligence, and activation strategies.Coach and mentor engineers and technical contributors, providing guidance on architecture, design patterns, engineering practices, and technology adoption.Communicate platform strategy, technical direction, risks, and recommendations to stakeholders at varying levels across Product, Engineering, and business organizations.Drive continuous improvement through modern engineering practices, automation, operational metrics, and platform optimization initiatives. Qualifications Minimum of 8+ years of experience in software engineering, data engineering, or data platform development, including 3+ years in a technical leadership role.Strong experience designing, building, and operating large-scale data platforms, data products, and distributed data processing solutions.Familiarity with modern MarTech and AdTech platforms, including audience activation, measurement, campaign orchestration, and digital marketing ecosystems.Knowledge of performance marketing, customer journey analytics, personalization, audience targeting, and marketing measurement.Experience with Identity Resolution, customer profile management, audience segmentation, consent management, and customer intelligence platforms.Experience working with Data Clean Rooms and privacy-safe data collaboration technologies preferred.Hands-on experience with cloud-native data platforms and architectures, preferably AWS.Deep expertise in data engineering technologies, including Python, SQL, Spark, Kafka, and modern data processing frameworks.Hands-on experience with Databricks, Delta Lake, Customer Lake CDP, Unity Catalog, and modern Lakehouse architectures preferred.Experience with GenAI, agentic AI, and MCP, enabling AI-powered personalization, customer intelligence, and marketing experiences through modern data platforms.Experience building scalable batch and streaming data pipelines with a strong focus on performance, reliability, observability, and data quality.Strong understanding of DataOps, CI/CD, Infrastructure as Code, automated testing, monitoring, and operational excellence practices.Experience designing APIs and data services to support consumer, analytics, and activation use cases.Strong understanding of data governance, metadata management, privacy, security, and regulatory considerations involving customer data.Proven ability to influence architecture decisions and collaborate effectively across Product, Engineering, Marketing, Analytics, and business stakeholders.Demonstrated ability to mentor engineers and provide technical leadership across cross-functional teams.Experience supporting AI/ML, customer intelligence, or next-generation marketing platforms preferred.Passion for evaluating emerging technologies and shaping enterprise-wide standards and best practices. Special Factors Sponsorship Vanguard is not offering visa sponsorship for this position. About Vanguard At Vanguard, we don't just have a mission—we're on a mission. To work for the long-term financial wellbeing of our clients. To lead through product and services that transform our clients' lives. To learn and develop our skills as individuals and as a team. From Malvern to Melbourne, our mission drives us forward and inspires us to be our best. How We Work Vanguard has implemented a hybrid working model for the majority of our crew members, designed to capture the benefits of enhanced flexibility while enabling in-person learning, collaboration, and connection. We believe our mission-driven and highly collaborative culture is a critical enabler to support long-term client outcomes and enrich the employee experience." We need sections: About the role (maybe the intro paragraph before Core Responsibilities). Responsibilities (the bullet list after Core Responsibilities). Qualifications (the list after Qualifications). Skills maybe not separate; but we could combine Qualifications and Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include a section only when posting has real specific content for it. The posting includes "Qualifications". It does not have separate "Skills" section; but we could treat the qualifications list as skills? However we should not invent. Probably we should not include Skills heading if no explicit skills list separate from qualifications. There's no explicit "Requirements" separate; qualifications cover requirements. Could we include Requirements heading with same content? Might be duplication. Better to follow the posting: we have "About the role" (intro), "Responsibilities", "Qualifications". Also there is "Special Factors Sponsorship" and "About Vanguard" and "How We Work". Those could be considered "About the company" but not in list. We could include "About Vanguard" as a section? Not in allowed headings list but we could maybe treat as "About the role"? Actually "About the role" is for role description; "About Vanguard" is company info. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.) meaning those are examples; we could also include other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. We have content for About the role (intro paragraph). Responsibilities (list). Qualifications (list). No explicit Benefits, Pay, Schedule. There's mention of hybrid working model under How We Work, which could be considered Schedule? It mentions hybrid working model, flexibility, in-person learning. That's about work arrangement, could be considered Schedule? But it's not explicit schedule like full-time, hours. Might be considered Benefits? Not really. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting does mention hybrid working model, which is a work arrangement, maybe could be considered Schedule? It's not explicit schedule like "full-time" or "remote". Safer to omit Schedule, Benefits, Pay. Requirements: The qualifications could be considered Requirements. But we already have Qualifications heading. Could we also include Requirements? Might be redundant. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one heading? But they gave both as examples. We could choose to include Qualifications only, and omit Requirements. Or we could include Requirements heading with same content as Qualifications? That would be thin duplication. Better to include Qualifications only. Thus sections: About the role, Responsibilities, Qualifications. Now we need to format:

About the role

then

with the intro paragraph(s). The intro paragraph includes multiple sentences; we can keep as one

. Responsibilities:

Responsibilities

then

• each responsibility. Need to split the responsibilities list. The text after "Core Responsibilities" is a long sentence with multiple responsibilities separated by periods. We need to break into list items. Let's extract each responsibility: - Provide technical leadership for Vanguard's MarTech Data Platform ecosystem, including Customer Data Platforms (CDP), Identity Resolution, Data Clean Rooms, customer data assets, and activation platforms that power modern marketing and personalization at scale. - Lead the architecture, design, and delivery of scalable, secure, and governed data solutions, ensuring reliability, performance, and operational excellence across the platform landscape. - Drive engineering best practices across data architecture, DataOps, observability, CI/CD, testing, security, and platform operations. - Partner closely with Product, Marketing, Analytics, AdTech, and Engineering teams to translate business objectives into durable, scalable technical solutions. - Provide technical oversight for the full solution lifecycle, including architecture reviews, design decisions, implementation, testing, deployment, and ongoing optimization. - Establish and enforce data governance, privacy, security, and compliance standards for customer and identity data, ensuring alignment with enterprise and regulatory requirements. - Evaluate emerging technologies and platform capabilities, developing roadmaps and recommendations that advance Vanguard's marketing, customer intelligence, and activation strategies. - Coach and mentor engineers and technical contributors, providing guidance on architecture, design patterns, engineering practices, and technology adoption. - Communicate platform strategy, technical direction, risks, and recommendations to stakeholders at varying levels across Product, Engineering, and business organizations. - Drive continuous improvement through modern engineering practices, automation, operational metrics, and platform optimization initiatives. We need to ensure each is a
• . Qualifications: similar list. Extract each qualification bullet (they are separated by periods). Let's parse: - Minimum of 8+ years of experience in software engineering, data engineering, or data platform development, including 3+ years in a technical leadership role. - Strong experience designing, building, and operating large-scale data platforms, data products, and distributed data processing solutions. - Familiarity with modern MarTech and AdTech platforms, including audience activation, measurement, campaign orchestration, and digital marketing ecosystems. - Knowledge of performance marketing, customer journey analytics, personalization, audience targeting, and marketing measurement. - Experience with Identity Resolution, customer profile management, audience segmentation, consent management, and customer intelligence platforms. - Experience working with Data Clean Rooms and privacy-safe data collaboration technologies preferred. - Hands-on experience with cloud-native data platforms and architectures, preferably AWS. - Deep expertise in data engineering technologies, including Python, SQL, Spark, Kafka, and modern data processing frameworks. - Hands-on experience with Databricks, Delta Lake, Customer Lake CDP, Unity Catalog, and modern Lakehouse architectures preferred. - Experience with GenAI, agentic AI, and MCP, enabling AI-powered personalization, customer intelligence, and marketing experiences through modern data platforms. - Experience building scalable batch and streaming data pipelines with a strong focus on performance, reliability, observability, and data quality. - Strong understanding of DataOps, CI/CD, Infrastructure as Code, automated testing, monitoring, and operational excellence practices. - Experience designing APIs and data services to support consumer, analytics, and activation use cases. - Strong understanding of data governance, metadata management, privacy, security, and regulatory considerations involving customer data. - Proven ability to influence architecture decisions and collaborate effectively across Product, Engineering, Marketing, Analytics, and business stakeholders. - Demonstrated ability to mentor engineers and provide technical leadership across cross-functional teams. - Experience supporting AI/ML, customer intelligence, or next-generation marketing platforms preferred. - Passion for evaluating emerging technologies and shaping enterprise-wide standards and best practices. Also there is "Special Factors Sponsorship Vanguard is not offering visa sponsorship for this position." That's a special factor; could be included maybe as a note under Qualifications? But it's not a qualification. Could be its own section? Not in allowed headings. Could we include as a

  under Qualifications? Might be considered extra info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So