Netflix Product Operations & Vendor Systems
The Problem
Coordinating 8+ vendor relationships across a high-velocity product pipeline had no single source of truth. Status lived in email threads and siloed spreadsheets — blockers surfaced too late, and cross-functional teams were constantly misaligned on timelines and deliverables.
Airtable as Operational Infrastructure
Designed and maintained the Airtable base that became the team's operational system of record. This wasn't filling in a template — it meant structuring the database schema, building cross-table relationships, creating filtered views for each stakeholder group (design, production, retail), and setting up automations to surface blockers before they hit the critical path.
Cross-functional Coordination System
Built a shared timeline view giving each team visibility into upstream dependencies — design approvals blocking production starts, production completion blocking retail setup. This made the critical path legible to non-technical stakeholders without requiring them to understand the underlying data model.
Outcome
The operational system became the template adopted for subsequent product lines — proof that well-architected internal tooling directly determines whether cross-functional teams ship on time. This role demonstrated that product operations and data architecture skills transfer directly to Technical PM work: understanding how systems store, move, and surface information is the same cognitive muscle whether you're configuring an Airtable base or writing a product spec for an API.