Principal Data Architect/Modeler

TKO•New York, NY
•$187,500 - $250,000

About The Position

TKO is consolidating the data estates of five businesses onto one enterprise data platform. The Principal Data Architect/Modeler leads the data architecture work, defining the platform’s standards, data model, framework, and roadmap. The role is both hands-on and influential: it designs and writes models, semantic definitions, standards, and architecture decision records, and guides Product, Engineering, Data Science, Data Governance, and Master Data Management in building to a shared architecture. The platform’s north star is an AI-ready foundation for Fan 360, Event 360, and Customer 360, with Employee 360 sequenced behind higher-value domains. The role establishes the end state and sequences delivery incrementally, putting usable slices into production while improving the model through use. AI readiness is central: agents and reporting should rely on common definitions, context, relationships, and role-based access embedded in the semantic layer. The role owns the enterprise data framework and roadmap; canonical enterprise and dimensional models; master data architecture; certified semantic definitions and metric hierarchy; and the architecture that makes governance enforceable in the platform. It also establishes architecture decision records, reference implementations, templates, modeling patterns, domain target models, and migration parity criteria. The role reports to the VP, Data Engineering & Science within TKO’s Enterprise Data organization and influences teams and delivery partners without line authority.

Requirements

  • 12 or more years in data architecture and engineering, including substantial experience as a named architect accountable for enterprise-wide design across multiple business units or operating companies, adopted without line authority over adopting teams.
  • Deep enterprise-scale dimensional modeling expertise, including conformed dimensions, grain discipline, slowly changing dimensions, and judgment about when a star schema is not appropriate.
  • Hands-on master data architecture experience across multiple domains, including implementation-style selection, entity resolution, survivorship, and golden-record design, with understanding of scale-related challenges and the cost of unmerging.
  • Production ownership of a semantic layer used by multiple teams, including metric definition ownership, certification, and resolving competing definitions of the same metric.
  • Deep, current Snowflake architecture experience, including medallion design, role and access taxonomy, tag-driven masking, row-access policies, and the cost implications of modeling decisions.
  • Strong dbt experience, including project and mesh structure, macros, contracts, versions, testing, and consolidating overlapping projects.
  • Experience architecting a substantial platform migration or consolidation, including parity validation.
  • Practical command of governance from a semantics perspective, including glossaries, metric definitions, lineage, data contracts, classification, access models, and platform enforcement.
  • Exceptional written communication, including the ability to produce design documents, standards, and decision records that remain useful after the author has moved on.

Nice To Haves

  • Direct experience making enterprise data consumable by AI systems, including exposing semantic models as agent tools, creating retrieval-ready and context-rich datasets, and knowing when generated SQL is appropriate.
  • Identity graph, Customer 360, or Fan 360 design experience, and working knowledge of consumer privacy regimes such as CCPA and GDPR and of consent management as a modeling input.
  • Experience designing data substrates for ML, including feature stores, training and retrieval pipelines, and in-platform serving.
  • Experience in media, sports, entertainment, live events, ticketing, or consumer and fan data environments.
  • Familiarity with open semantic interchange, open catalog and metadata standards, and the vendor landscape around them.
  • Experience working with offshore and partner delivery teams and raising their output to an architecture standard.

Responsibilities

  • Define the target-state enterprise data architecture and roadmap, including ingestion, medallion curation, serving, data science and ML consumption, environments, promotion paths, and layer standards.
  • Establish dimensional and conformed-dimension standards, including grain, conformance, slowly changing dimensions, surrogate and business keys, and shared dimensions across brands.
  • Design modular enterprise models that enable additional domains, properties, partnerships, and source systems to be onboarded with less re-engineering.
  • Design master data architecture across fan, event, rights holder, sponsor and partner, employee, and vendor domains in partnership with Master Data Management and Governance.
  • Select and justify master data implementation styles and design entity resolution, survivorship, versioned match rules, and defensible, reversible merges.
  • Model consent state, opt-out signals, and retention obligations as master data carried with identity across brands.
  • Own enterprise-certified semantic definitions and domain models for shared concepts, define metric tiers and certification criteria, and manage promotion from exploratory to certified metrics.
  • Determine where semantic definitions are represented across Snowflake semantic views, dbt, BI semantic layers, and the Open Semantic Interchange specification, and keep representations aligned.
  • Design platform mechanisms for catalog population, lineage capture, data quality, product observability, classification, and access boundaries across tools and agents.
  • Convert standards into automated checks such as model contracts, linting, pre-merge data diffs, and quality thresholds.
  • Establish and maintain architecture decision record practices, reference implementations, templates, and modeling patterns.
  • Define target models before domain migration waves and establish parity criteria for determining whether cutovers are complete.
  • Work with Data Governance & MDM, Product Management, Data Engineering & Platform, Data Science & ML, and Application Teams according to their respective responsibilities.
  • Raise architectural issues early and in writing, lead trade-off discussions with engineering and business leadership, and explain the costs and implications of decisions to non-engineers.
  • Mentor engineers in dimensional modeling, semantic design, and master data practice.
  • Guide teams and global delivery partners in adopting architecture standards without direct line authority.

Benefits

  • Health care
  • Retirement
  • Vacation and other paid time off
  • Short- and long-term incentives, as applicable
  • Growth and developmental opportunities
  • Additional benefits and offerings
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service