Data & AI Product Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate (EEO, legal, etc). Also remove duplicated lines, application instructions. We need to parse the posting. Let's extract content: - Who We Are: description of TKO Group Holdings. Could be "About the role"? Actually "Who We Are" is company overview. Could go under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe includes company description and team). We'll include that. - The Opportunity: description of role. Could go under Responsibilities? Or maybe "About the role". We'll decide. - What You’ll Own: list of duties. That's responsibilities. - What Success Looks Like: maybe also responsibilities or qualifications? Could be part of responsibilities. - Required: list of required experience/skills. That's Requirements/Qualifications/Skills. - Preferred: preferred qualifications. - Pay: includes hiring rate min and max. So we need Pay section. - Benefits: mention benefits briefly: "robust benefits, such as health care, retirement, vacation and other paid time off, and additional offerings." Also mention short- and long-term incentives, growth opportunities. So we can include Benefits. - Schedule: not mentioned explicitly. Employment type: Full-time. Location: Remote, New York, Raleigh, Stamford. Could be schedule? Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule details like hours, shift. So we omit Schedule. - Also we have Location and Employment type. Could be part of About the role? Might be metadata; we could include in a short

under About the role. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and employment type in a paragraph. - Also we have "Reports to: Lead Data & AI Product Manager". That's metadata. - Also "Team: Data & AI Products & Services (DAPS)". Also metadata. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all the substantive content from sections like Who We Are, The Opportunity, What You’ll Own, What Success Looks Like, Required, Preferred, Pay, Benefits. Also location, employment type, reports to, team. We must not include boilerplate: EEO, privacy policy, terms of use, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

TKO Group Holdings, Inc. (NYSE: TKO) is a premium sports and entertainment company... (Who We Are). Team: Data & AI Products & Services (DAPS). Reports to: Lead Data & AI Product Manager. Location: Remote, New York, Raleigh, Stamford. Employment type: Full-time.

Then maybe

Responsibilities

with

• items from What You’ll Own and What Success Looks Like and The Opportunity? We need to ensure we don't lose detail. Let's extract responsibilities bullet points: From What You’ll Own: - Core data products and decision capabilities - Own the product direction, roadmap, backlog, and lifecycle for On Location Base data products, including customer and transaction data, commercial reporting, marketing and audience activation, lead scoring, attribution, commissions, and operational analytics. - Oversee development of reusable data products on Snowflake, including dimensional models, curated data sets, semantic definitions, data interfaces, and governed self-service assets. - Partner with analytics and business teams to shape BI reporting and AI-enabled capabilities that solve real business problems and turn event-specific needs into reusable patterns where appropriate. - Product discovery and prioritization - Act as a trusted advisor to stakeholders across product, pricing strategy, marketing, finance, sales, operations, guest/customer experience, and event leadership. - Shape unmet needs into opportunities with a clear user, decision, action, value hypothesis, success measure, dependencies, and stop/reconsider criteria. - Manage a visible multi-horizon portfolio, making tradeoffs across business value, urgency, risk, reuse, delivery confidence, capacity, and displaced work. - Delivery and execution - Convert product intent into clear Jira epics, stories, acceptance criteria, data contracts, measures, and decision records. - Partner day-to-day with TKO data engineering, analytics engineering, data science, platform, governance, security, and external delivery teams to move work from discovery through production. - Keep dependencies, milestones, risks, decisions, blockers, stakeholder commitments, launch readiness, adoption, and post-launch ownership visible. From What Success Looks Like (these are success criteria, could be responsibilities or qualifications). We'll treat as responsibilities maybe. - Success measured by whether the business can reliably use the products you own to make better decisions and move faster. - Business stakeholders can clearly explain what the product does, who owns it, and when to use it. - Data products and Omni assets are adopted, reusable, documented, and trusted. - Engineering teams have clear priorities, well-shaped work, and fewer avoidable surprises. - Event-critical reporting and data flows are ready when the business needs them and are improved after each cycle. - Product health is visible through adoption, quality, reliability, latency, support signals, and outcome measures. - Repeated requests are converted into shared enterprise capabilities when reuse creates leverage. - Stakeholders know what is in flight, what is next, what is blocked, and what is intentionally not being done. From The Opportunity: maybe also responsibilities: building trusted data and AI foundation, owning portfolio of data products supporting On Location across commercial, customer, event, marketing, finance, sales, operational use cases. Translate complex needs into reusable data products, guide TKO engineering and data teams through delivery, ensure capabilities launched are adopted, trusted, measurable, continuously improved. Partner with On Location technology org. Enable reporting and decision-making across events. We'll combine. Now Requirements/Qualifications/Skills: From Required: - 3+ years of experience in data product management, technical product management, analytics product management, data engineering, data science, analytics engineering, or a closely related field. - Strong technical foundation in at least one of the following: data engineering, software engineering, data science, analytics engineering, or data analysis - with ability to reason credibly about the others. - Experience translating business problems into data models, analytical products, platform capabilities, integrations, APIs, pipelines, or AI-enabled workflows. - Working fluency with SQL and modern data concepts such as dimensional modeling, data quality, identity resolution, semantic layers, event instrumentation, warehouse/lakehouse architecture, APIs, and data lifecycle management. - Demonstrated ownership of products or complex initiatives from discovery through delivery, launch, adoption, and ongoing operation. - Strong execution and operating discipline: you keep commitments visible, follow up on dependencies, surface risks early, and close loops. - Excellent written and verbal communication, including ability to explain technical tradeoffs and data limitations to senior business leaders. - Experience balancing multiple concurrent priorities in an environment with changing requirements, hard deadlines, and cross-functional dependencies. From Preferred: - Career path that began in engineering, data science, data analysis, analytics engineering, or another technical discipline before transitioning into product management. - Experience with Snowflake, Omni or another semantic/BI platform, Salesforce, Marketing Cloud or comparable activation systems, Amplitude/GA4, Census or similar reverse-ETL tools, and/or modern AI platforms. - Experience with customer 360, event or behavioral data, audience activation, attribution, lead scoring, marketing analytics, commissions, or commercial reporting. - Experience delivering products for live events, entertainment, sports, travel, hospitality, e-commerce, or another time-sensitive, customer-facing industry. - Experience working with governance, privacy, security, PII, data-sharing agreements, model risk, or responsible AI requirements. - Familiarity with Jira, agile delivery practices, product discovery, experimentation, and portfolio or product-operations cadences. - Genuine enthusiasm for entertainment, sports, live events, and the brands that make TKO unique. We could separate into Requirements (Required) and Qualifications (Preferred) or Skills. The instruction list includes Requirements, Qualifications, Skills as possible headings. We need to decide which to use. We could have: -

  Requirements

  for Required. -

  Qualifications

  for Preferred. -

  Skills

  maybe not needed; we could combine technical skills into Requirements. But we must not create sections with filler. We have content for Requirements and Qualifications, so we can include both. Pay: we have hiring rate min $99,450 annually, max $132,600 annually. Also note that hiring pay rates based on location etc. We'll include that. Benefits: mention robust benefits: health care, retirement, vacation and other paid time off, short- and long-term incentives, growth and developmental opportunities. We should not include boilerplate like "TKO is an Equal Opportunity Employer..." etc. Remove that. Also remove lines about Privacy Policy, Terms of Use. Now we need to ensure we preserve ALL substantive information. Let's double-check we didn't miss any substantive content. From Who We Are: includes TKO owns iconic properties including UFC, WWE, PBR; reach 1 billion households across 210 countries; organize >500 live events year-round; attract >3 million fans; TKO also services and partners with major sports rights holders through IMG and On Location. That's substantive. From The Opportunity: building trusted data and AI foundation that helps its brands and enterprise functions understand the business, make better decisions, act with greater speed and precision. The Data & AI Product Manager will own a portfolio of data products and capabilities that support On Location, TKO’s sports and entertainment hospitality business, across commercial, customer, event, marketing, finance, sales, and operational use cases. This is a hands-on product management role for someone who can move comfortably between business outcomes and technical implementation. You will translate complex needs into reusable data products, guide TKO engineering and data teams through delivery, and make sure the capabilities we launch are adopted, trusted, measurable, and continuously improved. The role sits within DAPS, the cross-TKO Data & AI Products & Services organization, and partners closely with the On Location technology organization. You will help enable reporting and decision-making across a changing portfolio of major events and businesses - including NCAA, Super Bowl, UFC, WWE, World Cup, and other On Location programs - while building patterns that can be reused across TKO. We need to include all that. From What You’ll Own: we captured. From What Success Looks Like: captured. From Required: captured. From Preferred: captured. From Pay: captured. From Benefits: captured. Location and employment type: we included in About the role paragraph. Reports to and Team: also included. Now we need to format as HTML. We'll use

  for each section heading. Inside sections, we can use

  for prose and

  • for lists. We need to decide where to use lists. For responsibilities, we can break into sub-sections? But we can just make a
    with each bullet as
    • . For long sentences, it's okay. We'll produce something like:

      About the role

      TKO Group Holdings, Inc. (NYSE: TKO) is a premium sports and entertainment company. TKO owns iconic properties including UFC, the world’s premier mixed martial arts organization; WWE, the global leader in sports entertainment; and PBR, the world’s premier bull riding organization. Together, these properties reach 1 billion households across 210 countries and territories and organize more than 500 live events year-round, attracting more than three million