Data Lead - Title Lifecycle & Content Formats
Netflix
- Location
- Los Angeles,California,United States of America
- Work model
- On-Site
- Level
- Senior
- Salary
- $230k – $340k/yr
- H-1B history
- 80 approvals (FY2023)
Skills
About this role
At Netflix, our mission is to entertain the world. Together, we are writing the next episode - pushing the boundaries of storytelling, global fandom and making the unimaginable a reality. We are a dream team obsessed with the uncomfortable excitement of discovering what happens when you merge creativity, intuition and cutting-edge technology. Come be a part of what’s next.
We are looking for a Data Lead to join the Title Data Management team within Content Data Management under Content & Business Products (CBP). Our team manages the integrity and connectivity of title data across its full lifecycle — from a title's earliest creation through active production, launch, and ongoing catalog life. This role focuses on the lifecycle dimension: understanding how title data and structure change as a title moves through its life, and as Netflix's catalog expands into new formats.
In this role, you will own the team's knowledge and response to changes in the title lifecycle and structure across multiple entities and data models. As Netflix's catalog expands into new content formats and adjacent systems evolve, you'll define what "title" means in new contexts, build the frameworks the team uses to scope and prioritize work, and assess how upstream changes ripple through title data management practices and workflows. You'll partner with multiple product and engineering teams supporting development, production, finance, and legal, as well as other business use cases that require foundational, horizontal title data management — engaging early enough to shape outcomes, not just react to them. This requires collaborative and strategic thought partnership, the establishment and alignment of shared goals, authoring data requirements, measuring impact and telling that story through metrics, and normalizing edge case patterns into established workflows and structured data.
A successful candidate has the depth to investigate ambiguous problems and turn them into structure, builds strong partnerships across a wide set of teams through collaboration rather than authority, and can pivot as the systems and formats around them change. You'll hold a strong point of view grounded in a real understanding of multiple data models and how they connect — and you'll be comfortable being the person who defines the framework before one exists. You’ll also enjoy diving into new business problems and content formats to understand where gaps, overlaps, and discrepancies exist across a varied title infrastructure.
| Responsibilities
* Identify and establish relationships with product and engineering teams in order to collaborate on evolving data models, entity relationships, cardinality rules, attributes and taxonomies across title data
* Understand different title data models and content formats deeply, which involves prioritizing the most critical areas to learn about at a given point in time based on business needs
* Understand business drivers and multiple business teams throughout the lifecycle and across content formats to address impacts to title data management and establish relationships with these teams as needed
* Build trust and alignment with partner teams through influence, not authority — earning buy-in by communicating shared benefit and aligning on common goals
* Assess and communicate the impact of adjacent-system changes (e.g. shifts in production data model) on title data, and lead the team's response
* Create necessary documentation for both the team’s understanding of changes within the title lifecycle and structure, as well as contributing to automation and agentic workflows (e.g. how to handle multiple developments for a given title, status transitions, connected data workflows, etc)
* Define what "title" means for new and evolving content formats, and translate that into operational rules and handoff specs the rest of the team can act on
* Build and maintain the cross-domain duplicates framework, so titles that