Sr Product Manager-Extensibility Platform

Build alignment across teams you do not own. Design for agentic consumers. Translate extensibility investment into business outcomes—customer retention, partner ecosystem growth, competitive defensibility. We are looking for a PM who leads with the customer and earns agreement rather than waiting for authority. Someone who would rather spend an afternoon watching a developer struggle than an afternoon in a prioritization meeting, and who comes back with a story that changes what the team builds. We recognize that background takes many forms. We will consider candidates who meet one of the following experience profiles: Preferred: PM on a developer-facing or platform product. 4+ years in product management, including 2+ years owning a developer-facing, API, extensibility, or ecosystem product. Strong: Engineering or solutions background moving into product. 3+ years building software or implementing it for customers, plus 2+ years of product management. You speak engineering fluently because you were one. Also considered: PM with a strong research and communication track record. 4+ years in enterprise SaaS product management with real depth in customer discovery and unusually strong writing, paired with the technical curiosity to build API and SDK fluency fast. Regardless of path, you will need to demonstrate: Influence without authority. You can name a decision you moved without the authority to mandate it, and explain how. Storytelling as a working skill. You can take a messy problem and give it a shape that makes the next step obvious. We will ask to see your writing, and we will read it closely. Customer-forward instincts. Specific examples of research you ran yourself that changed what you built. Platform and API fluency. APIs, SDKs, authentication and authorization models, webhooks, and extension patterns—enough depth to hold a credible design conversation and earn engineers' trust. You understand that documentation, error messages, and versioning policy are part of the experience. Decision-making style. You make calls, defend them, and update when the data changes. You do not write requirements that hedge every decision back to engineering. Data-driven prioritization. Adoption funnels, time-to-value, and usage instrumentation drive your roadmap, not the loudest stakeholder. AI-native working style. AI agents are part of your daily PM workflow—research, synthesis, drafting, metrics analysis—and you understand how building with AI coding assistants changes the way requirements get written. Experience launching or scaling a developer portal, app marketplace, or partner ecosystem program. Experience with low-code or configuration-driven tooling built for non-developer administrators. Background in HCM, workforce management, or another enterprise SaaS domain with complex role and permission models. Familiarity with agent and tool-calling frameworks, or building capabilities intended for AI consumers. Bachelor's degree in a technical field or equivalent practical experience. What Success Looks Like In the first 90 days: Complete firsthand discovery with a meaningful set of builders—partners, customer administrators, and internal teams—and publish a synthesis the broader organization cites. Establish the baseline for time-to-first-app and name the friction points behind it. Land a shared definition of the extensibility surface with at least two partner product teams. In your first year: You are the source of truth on the builder. Others come to you for what builders need, and your research is quoted in decisions you were not in the room for.