Product Manager, Platform Experience & Developer Product

Required Qualifications

• 5+ years of product management experience, with meaningful time spent owning developer-facing or platform-layer products such as APIs, SDKs, developer tools, or technical infrastructure.
• Strong technical fluency with API design and SDK development, including an understanding of versioning, backward compatibility, and what makes a developer experience feel polished and reliable.
• A track record of thinking about infrastructure as a product, with the ability to translate system-level capabilities into clearly differentiated, customer-facing features.
• Experience building or owning developer tooling surfaces such as consoles, dashboards, usage analytics, or observability and debugging tools.
• Analytical by default: you define success metrics before you build, instrument thoughtfully, and use data alongside qualitative feedback to make decisions.
• Strong collaborator who works well across engineering, design, infrastructure, and GTM teams, and who can communicate technical tradeoffs clearly to a range of stakeholders.
• Highly execution-oriented with a bias toward shipping and iterating quickly.
• Demonstrated ownership across the full product lifecycle — from problem definition and scoping through launch, iteration, and eventual deprecation or migration.
• 5+ years of product management experience, with meaningful time spent owning developer-facing or platform-layer products such as APIs, SDKs, developer tools, or technical infrastructure.
• Strong technical fluency with API design and SDK development, including an understanding of versioning, backward compatibility, and what makes a developer experience feel polished and reliable.
• A track record of thinking about infrastructure as a product, with the ability to translate system-level capabilities into clearly differentiated, customer-facing features.
• Experience building or owning developer tooling surfaces such as consoles, dashboards, usage analytics, or observability and debugging tools.
• Analytical by default: you define success metrics before you build, instrument thoughtfully, and use data alongside qualitative feedback to make decisions.
• Strong collaborator who works well across engineering, design, infrastructure, and GTM teams, and who can communicate technical tradeoffs clearly to a range of stakeholders.
• Highly execution-oriented with a bias toward shipping and iterating quickly.
• Demonstrated ownership across the full product lifecycle — from problem definition and scoping through launch, iteration, and eventual deprecation or migration.