Sourced directly from Netflix's careers portal — Job Requisition ID JR41124, Position ID 790316311096, Work Type: Remote. Posting: https://explore.jobs.netflix.net/careers/job/790316311096?microsite=netflix.com
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.
Hawkins is Netflix's design system and the foundation of the consumer experience across every surface: TV, mobile, and web. It is the shared language between design and engineering that ensures what designers create is delivered consistently across every engineering platform. It’s also the foundation for future automation and agentic design-to-code workflows.
We are looking for a Technical Program Manager to drive large, cross-team programs across Hawkins engineering and cross-platform UI foundations. This high impact role will be a force multiplier across the XD Platform team, client and server engineers, and design — owning planning, execution, and cross-functional alignment for high-impact initiatives that shape how Netflix builds consumer-facing UI at scale.
What You'll Do
- Drive large, cross-team programs across Hawkins ecosystem end-to-end: define scope, milestones, and sequencing; keep us honest on commitments; and adjust quickly as we learn.
- Navigate technical and organizational complexity across design, client, and server engineering, ensuring the right people are in the room and decisions are pragmatic, not perfect.
- Coordinate platform adoption across multiple client surfaces (TV, mobile, web).
- Bring clarity to ambiguity: create lightweight structure, clear communication, and simple mechanisms without over-engineering process or slowing teams down.
- Build alignment and strong relationships with partners across Design Platform, Engineering, Experience Design, and Product Management.
- Establish and manage the intake process from XFN partners.
- Surface and manage dependencies and risks so issues are addressed early and delivery stays on track.
What Sets You Apart
- 6-8+ years of technical program leadership, driving multi-team programs in large, complex engineering organizations, including significant experience on platform, framework, or client/UI engineering programs.
- Able to engage on technical trade-offs without writing code, and communicate naturally across audiences from ICs to senior leadership in Engineering, Design and Product.
- Experience with client/UI engineering, design systems, or platform/framework development, and a strong feel for developer and designer experience.
- Equally comfortable getting into technical details and setting direction within your area; clear-eyed about what the moment calls for, and skilled at driving accountability through clarity and relationships rather than process or reporting structure.
- Takes full ownership of outcomes and relentlessly drives execution, even when faced with ambiguity or cross-functional friction.
- Experience leveraging GenAI tools to scale your impact, and a genuine curiosity about how these tools are reshaping the way technical programs run.
- Familiarity with cross-platform delivery (TV, mobile, web) and design-to-code workflows is a plus.
Compensation
- Netflix’s compensation structure consists solely of an annual salary — no bonuses. You choose each year how much of your compensation you want in salary versus stock options.
- Salary range for this role: $290,000 – $460,000/year. Varies based on location.
Benefits & Culture
- Comprehensive benefits: Health Plans, Mental Health support, 401(k) with employer match, Stock Option Program, Disability Programs, HSA/FSA, Family-forming benefits, Life and Serious Injury Benefits, plus paid leave programs.
- Full-time hourly employees accrue 35 days annually for PTO (vacation, holidays, sick); full-time salaried employees have flexible time off from day one.
- Netflix culture and inclusion details: jobs.netflix.com/work-life-philosophy, jobs.netflix.com/culture, about.netflix.com/en/inclusion.
Question
Tell me about a time you led a major technical initiative or platform migration across disparate surfaces (e.g., TV, iOS/Android, Web). How did you handle varying client architecture constraints and surface-specific timelines?
Situation
Prime Video's consumer UI had forked across three client surfaces with no shared foundation. TV alone spanned 10+ device families (Fire TV, Roku, LG/Samsung OEMs, game consoles), each with its own rendering constraints, D-pad focus-navigation input model, and fragmented firmware cadence, versus iOS, Android, and web's direct-touch interaction and much faster release cycles. Each surface hand-coded the same components independently at 3–4 weeks per component per surface.
Action
- Resolved the architecture-constraint problem structurally: instead of forcing a common runtime, got all three surfaces to agree to a shared token-and-component contract, with each surface building its own independently deployable codegen adapter against that contract. TV kept full control over how a component rendered on constrained hardware — it just had to guarantee the same states, accessibility behavior, and content as mobile and web.
- Resolved the timeline-constraint problem by sequencing, not forcing a shared calendar: Phase 0 validated the contract against TV, the most constrained and slowest-moving surface, before Phase 1 extended it to mobile's faster cadence, before Phase 2 extended it to web — each phase gated by adoption and drift metrics, not a fixed date.
- Matched each surface's exit criterion to its own real constraint: TV's was zero rollback-blocking defects (TV firmware rollback windows are brutal); mobile's was adoption velocity; web's was org-wide onboarding.
- Kept the three surfaces' engineering leads in the room for the one decision that had to be shared — the contract itself — and let each org's engineering lead own every decision that only affected their own surface.
Result
Design-to-code lead time dropped from 3–4 weeks to under 2 days per component across every surface, cross-surface drift fell from 40%+ to under 5%, and 92% of client engineering teams onboarded within 9 months.
Reflection
The instinct on a cross-surface migration is to look for one architecture and one timeline that fits everyone. The surface that makes that impossible — here, TV's hardware — is exactly the one you design around first, not force into the same box as the easier surfaces.