Software Engineer 5 - Member API

Netflix Netflix · Big Tech · United States · Remote · Engineering

Netflix is seeking a Software Engineer 5 for their Member API team. This role focuses on the Consumer Edge GraphQL service, API paradigms, and developer experience for discovery-related screens. The engineer will be a technical authority on client-server API design and GraphQL, working on evolving the GraphQL schema, owning API paradigms, and contributing to the API lifecycle. The role involves retiring legacy architectures and converging on GraphQL. Experience with AI-assisted contributions to the API development workflow is mentioned as a future consideration.

What you'd actually do

  1. Evolve the GraphQL schema layer, including federation patterns, and lifecycle governance
  2. Own the API paradigm portfolio across client-driven, server-driven, and emerging patterns, providing clear opinionated guidance on when each fits
  3. Partner with device client engineers and backend domain teams to design APIs that are correct, resilient, and intuitive to consume without requiring knowledge of Member Platform internals
  4. Contribute to the API lifecycle from design through deprecation: tooling, guardrails, governance, and payload health
  5. Shape how AI-assisted (and eventually AI-driven) contributions fit into the API development workflow

Skills

Required

  • GraphQL API design and evolution at production scale
  • Schema design
  • Federation
  • Breaking-change management
  • Field lifecycle governance
  • Client-server API relationships
  • Large, distributed systems
  • Blast radius reasoning
  • Schema ownership boundaries
  • Operational implications of changes
  • Precise and clear proposal writing
  • Productive tension with partner teams

Nice to have

  • Real-time or push-based API patterns (subscriptions, SSE)
  • Owning API platforms or developer-facing infrastructure
  • API observability
  • Schema validation tooling
  • Developer experience platforms

What the JD emphasized

  • Deep, hands-on experience designing and evolving GraphQL APIs at production scale, including schema design, federation, breaking-change management, and field lifecycle governance
  • Strong intuition for client-server API relationships: you can reason clearly about the tradeoffs between client-driven and server-driven paradigms and know when each is appropriate
  • Comfort operating in large, distributed systems, reasoning about blast radius, schema ownership boundaries, and the operational implications of changes that touch many downstream consumers
  • Strong communication skills: you can write precise, clear proposals and hold productive tension with partner teams when their design choices conflict with platform principles