← New York Times Interview Insights

New York Times·Product Manager·Hiring Manager Screen·Senior

Senior
May 2026

Summary

Interviewed at the New York Times for a product manager role. The question was pretty conceptual, more about how you think about PM archetypes than anything tactical.

Questions Asked (1)

Q1

How do you distinguish the responsibilities of a platform product manager from those of a feature product manager?

Product StrategyCross-functional AlignmentStakeholder Management
Author's notes

I fumbled this a bit at first because I started talking about specific projects instead of the actual structural difference.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by defining both roles clearly, emphasizing that platform PMs focus on building scalable, reusable capabilities that serve multiple teams, while feature PMs focus on delivering user-facing value for a specific product area. Then, use examples from your experience to illustrate how you've navigated the differences, particularly in cross-functional collaboration and prioritization. Finally, tie it back to the New York Times' context, highlighting how both roles contribute to the company's mission.

Pro tip: Acknowledge that the lines can blur and that the best PMs adapt their approach based on the team's needs, but always keep the end-user and business impact in mind. Show that you understand the NYT's unique position as a subscription-based media company where platform investments (like a unified identity system) enable personalized experiences across products.

1. Define the core distinction

Explain that platform PMs own internal products (APIs, services, infrastructure) that enable other teams, while feature PMs own external products that directly serve end-users. Emphasize that platform PMs measure success by adoption, reliability, and developer productivity, whereas feature PMs measure by user engagement and business metrics.

2. Highlight stakeholder differences

Describe how platform PMs work primarily with internal engineering teams, data scientists, and other PMs as customers, requiring strong negotiation and alignment skills. Feature PMs work more with design, marketing, and external user research, focusing on user needs and go-to-market strategies.

3. Discuss prioritization and trade-offs

Explain that platform PMs prioritize based on cross-team impact, technical debt, and long-term scalability, often saying 'no' to one-off requests. Feature PMs prioritize based on user impact, competitive landscape, and revenue goals, often balancing quick wins with strategic bets.

4. Connect to NYT context

Relate the distinction to the New York Times: platform PMs might build a shared content management system or subscription platform that powers multiple digital products, while feature PMs might enhance the Cooking app or introduce a new newsletter feature. Show awareness of how both roles support the NYT's subscription-first strategy.

5. Emphasize collaboration and adaptability

Conclude by noting that despite differences, both roles must collaborate closely. A successful PM can switch hats depending on the project phase or organizational needs, and at the NYT, cross-functional alignment is key to delivering a seamless user experience.

Key Points to Mention

  • Platform PMs treat other teams as customers; feature PMs treat end-users as customers.
  • Platform success metrics: API adoption, uptime, developer satisfaction; feature success metrics: user engagement, retention, revenue.
  • Platform PMs focus on 'building it right' (scalability, reusability); feature PMs focus on 'building the right thing' (user value, market fit).
  • Stakeholder management: platform PMs need to influence without authority across teams; feature PMs need to align with marketing, design, and sales.
  • At NYT, platform investments (e.g., unified login, content APIs) enable personalized experiences across apps like News, Cooking, and Games.
  • Both roles require strong communication and the ability to say 'no'—platform PMs to feature requests that don't scale, feature PMs to scope creep.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.