Principal Product Manager, Content Services & API

Condé Nast is one of the world's most renowned media publishing companies, creating and distributing every type of media today, spanning print and digital publishing in all formats. With a portfolio of some of today's most influential brands, the company continues to grow its audience through a global operational and content infrastructure across its 12 owned and operated markets. Headquartered in New York City, the company's owned and operated markets include China, France, Germany, India, Italy, Japan, Mexico & Latin America, Spain, Taiwan, UAE/Dubai, the U.K., and the U.S., with additional local license partners in over twenty additional markets across the globe.

Lead brands include Vogue, The New Yorker, GQ, Architectural Digest, Condé Nast Traveler, Vanity Fair, Wired, Allure, Ars Technica, Bon Appétit, House & Garden, Pitchfork, Tatler, and Vogue Business.

Job Description

Location:

New York, NY We're hiring a technical Product Manager to own the strategy and roadmap for this layer: the REST Content API, GraphQL Content Service, GraphQL Federated Gateway, Content API Search and Games Service. We need someone who can sit with engineering as a technical peer. Systems thinking, architectural design and scalability are central to the job. You should have clear opinions about how a content platform should work and the judgment to make difficult tradeoffs.

You'll own the product direction for our content APIs and shared services. You'll bring the needs of consuming teams into one roadmap and make the priorities, API contracts and service expectations clear. You'll hold the full picture: content models, schemas, search, federation, performance, reliability and developer experience. You'll understand how a decision in one service affects editorial tools, the audience platform, mobile apps and brand delivery.

You'll decide where common capabilities create value and where a specific use case warrants flexibility. You'll shape architectural choices with engineering: service boundaries, schema evolution, gateway behavior and migration paths. You'll weigh the effects on consumers, operating cost and future scale, and translate those tradeoffs into product decisions. Engineering owns the technical design and implementation; you bring enough depth to challenge proposals and make informed decisions together.

You'll work closely with the Copilot PM, who owns the editor-facing product, and the Audience Platform PM, who owns the front end. Your focus is the services those products depend on. This is an individual contributor role with responsibility for aligning teams around a shared platform direction.

Understand the developers who depend on us. Spend time with Copilot, Verso, mobile and brand engineering teams. Understand their integration workflows, recurring workarounds and unmet needs. Turn those findings into shared capabilities and a roadmap that makes it easier to build and deliver content experiences. Think in systems. Trace content from creation and ingestion through modeling, indexing, retrieval and delivery. Map dependencies and ownership across services.

Before changing a schema or gateway, understand what it means for consumers, content freshness, permissions and failure behavior. Shape the architecture with engineering. Take an active role in design discussions about REST and GraphQL, federated schemas, service boundaries and data access patterns. Evaluate build, buy and evolve options. Make the product consequences of consistency, coupling, caching and technical debt explicit.

Design for scale and reliability. Define service expectations with engineering and consuming teams. Balance latency, availability, throughput, content freshness and cost. Plan for traffic peaks, query complexity, rate limits and failures in dependent services. Make resilience and capacity part of roadmap decisions. Own the API experience and lifecycle. Set a clear direction for schemas, versioning, backward compatibility and deprecation. Improve search and retrieval, documentation, examples, onboarding and error behavior.

Make contracts predictable and give teams a workable path to adopt changes. Measure what matters. Agree on baselines and targets for latency, errors, availability, content freshness, search quality and cost to serve. Track time to first successful integration, adoption and support burden. Use these signals to prioritize work and check whether the platform is getting better. Lead platform evolution.…