Technical Program Manager

I am a Technical Program Manager with over 18+ years of experience leading large-scale, high-impact technology initiatives across multiple organizations, platforms/systems, and business functions. As a TPM my core function is to define and own the technical program strategy for complex, business-critical initiatives, ensuring technical execution is tightly aligned to measurable business outcomes. My Strengths • Navigating Ambiguity: I thrive when a program is loosely defined, transforming extreme ambiguity into high-velocity, practical execution across large-scale, multi-platform initiatives, mapping intricate technical dependencies across APIs, client surfaces, and infrastructure into a sequenced, prioritized roadmap. • Cross-Functional Alignment: I achieve alignment across highly matrixed environments — bringing Product, UI Design, client engineering, QA, Operations, Risk & Compliance, and Legal teams together around shared priorities, clear dependencies, and cohesive delivery across TV, mobile, and web surfaces. • Context Over Control: I lead with context, not control, believing in clear intake mechanisms and automated guardrails that protect quality and consistency without suffocating innovation or speed. • XFN Force Multiplier: I act as the connective tissue between Experience Design, Product Management, and Engineering — ensuring design systems aren't just a static guideline, but a living design-to-code pipeline that accelerates developer velocity. What I'd bring to this TPM role is a very practical ability to take complex design, engineering, and platform work and turn it into lightweight systems teams can actually use. My Scale & Impact • In my Prime Video work, that meant helping TV, mobile, and web teams build more consistent customer and UI experiences while reducing duplicated engineering effort by 35% and accelerating cross-client feature delivery by 40% — without adding unnecessary process. • Unified 8 cross-functional teams around shared UI architecture and reusable design-to-code foundations during the Prime Video launch — where TV, mobile, and web teams had been solving similar UI challenges differently — reducing duplicated engineering effort by 35% and accelerating cross-client feature delivery by 40%. • Kept client, infrastructure, and reliability teams aligned during that cross-platform launch by creating simple checkpoints and early risk visibility, supporting a platform experience for 120M+ users while maintaining 99.99% availability. • Built a clearer intake and execution mechanism for publisher monetization onboarding — clarifying ownership, prioritizing XFN partner requests, and sequencing delivery across product, engineering, operations, and external partners — accelerating partner readiness from 12–18 months to less than 7 days. • Transformed fragmented internal developer workflows into a consistent platform delivery model for 1,300+ engineering teams, shaping the vision, operating model, and adoption path that reduced deployment time from 2 weeks to under 45 minutes. • Used GenAI and automation to create lightweight delivery health signals, cutting engineering overhead and reporting cycles by 40%. One lesson I've learned along the way is that the hardest part is rarely the technology itself; it is helping talented teams align quickly when each group is seeing the problem from a different angle. So the story I'd bring to Netflix is simple: I've repeatedly helped teams take complex, fragmented work and turn it into shared platforms, clearer execution rhythms, and reusable foundations that scale. That is what excites me about Hawkins — it is not just a design system to maintain, but a platform for helping design and engineering teams move faster together without adding unnecessary process. I would bring that same mix of platform thinking, cross-functional clarity, and delivery discipline to help Hawkins scale as a trusted foundation for Netflix product teams. What draws me to Netflix is your absolute rejection of bloated, over-engineered process. In a traditional company, cross-functional alignment means endless committees and rigid control — Netflix's philosophy of Freedom and Responsibility and Context over Control matches exactly how I operate: I give engineering and design teams the precise architectural context, clear milestones, and boundary lines they need, then get out of their way so they can run fast. The Hawkins Design System is the ultimate manifestation of this — it's not just a UI kit, it's a shared language and foundational framework connecting design to client/server engineering. I want to use my experience leading massive platform and client-surface transformations to champion Hawkins, manage its complex multi-team intake, and scale it into a frictionless, invisible superpower for Netflix developers and designers alike.