Principal Product Manager, Content Services & API
New York City, NY, United States22h ago
Free account needed to apply or save. It takes a minute, and we'll bring you right back to this job.
Skills
About the role
Job Description
Location:
New York, NYWe'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.
The Role
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.
What you'll do
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. Sequence improvements and migrations across consumers while keeping production services healthy. Make ownership, dependencies and rollout plans explicit. Use pilots, compatibility checks and rollback plans to reduce disruption, and follow through until consumers have adopted the change.
Apply AI where it improves the platform. Use AI in discovery, prototyping and technical analysis. Evaluate opportunities in content discovery, metadata enrichment and developer tooling. Define quality, permissions, provenance, latency and cost requirements before expanding an AI-enabled capability.
What you bring
- A track record of owning technical products, APIs or shared platform services from discovery through delivery and adoption. You can explain the strategy you set, the tradeoffs you made and the outcomes.
- Real technical depth in API design, REST, GraphQL, schema evolution and versioned contracts. You can read an API specification, inspect a payload and challenge a proposed design.
- Demonstrated systems thinking. You've mapped dependencies across services and teams, identified upstream and downstream effects, and used that understanding to make better product decisions.
- Architectural judgment. You've contributed meaningfully to decisions about distributed systems, service boundaries, federation, caching, indexing or data consistency. You can explain the alternatives and why the chosen approach fit.
- Experience with scalability and reliability in production. You understand how traffic, query patterns, bottlenecks and dependency failures affect latency, availability and cost, and have prioritized improvements with engineering.
- Developer product instincts. You've improved integration, documentation or onboarding for technical users and can show how you reduced friction or increased adoption.
- Experience leading API changes or platform migrations. You know how to manage compatibility, deprecation and rollout across multiple consuming teams.
- Strong communication and product judgment. You write clear requirements and decision documents, align teams with competing needs, and explain technical tradeoffs to business stakeholders.
- Hands-on analytical ability. You can use API tools, logs, dashboards or SQL to investigate a problem and test a hypothesis with technical partners.
- Experience defining useful platform metrics and using them to make investment decisions. You connect service health and developer productivity to customer and business outcomes.
- An understanding of structured content, metadata, taxonomy, content relationships and publishing lifecycles. Experience with a CMS, headless content platform or digital asset system is valuable.
- A strong plus: experience serving multiple brands, markets or products from shared infrastructure, particularly in media or publishing.
- A strong plus: direct experience with GraphQL federation, content search or services consumed by both web and mobile applications.
- A strong plus: experience prototyping or delivering AI-enabled retrieval, content enrichment or developer tools, with a clear approach to evaluation and controlled access.
Condé Nast is an equal opportunity employer. We evaluate qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, age, familial status and other legally protected characteristics.
The expected base salary range for this position is from $185,000 - 215,000. Salary offers are based on a wide range of factors including but not limited to relevant skills, training, experience, and education.
What happens next?
If you are interested in this opportunity, please apply below, and we will review your application as soon as possible. You can update your resume or upload a cover letter at any time by accessing your candidate profile.
Condé Nast is an equal opportunity employer. We evaluate qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, age, familial status and other legally protected characteristics.