Director of Product Management, Enterprise API

Salesforce•Seattle, WA

2d•$197,300 - $344,700•Hybrid

About The Position

The Enterprise Application Programming Interface (API) team within Platform Services owns the APIs and frameworks that power how customers, partners, and AI agents — including Agentforce — interact with Salesforce data at scale. The Enterprise API portfolio (REST, SOAP, Bulk APIs, and the SOQL query language) handles billions of requests per day across every Salesforce Cloud. As a Director of Product Management, you own the strategy, roadmap, and delivery for this portfolio and lead a cross-functional team of 20+ engineers across multiple geographies. You aren't just managing a feature backlog; you are forming the point of view on what the portfolio becomes as AI agents complement human developers as primary API consumers integrating with Salesforce in a headless context. To be successful, you need excellent communication skills and a developer-centric mentality. Your customers are API producers and consumers, and you will ensure Salesforce meets their needs through the platform products you own. You work across Clouds with cross-functional partners to collect, vet, and prioritize requirements, then drive the roadmap and long-term direction from there.

Requirements

8+ years of product management experience, including at least four years owning developer-facing or platform infrastructure API products, and can show evidence of authoring and defending a portfolio strategy, not just executing a feature roadmap.
Hands-on working knowledge of API architectures, protocols, and specifications, including REST and OpenAPI, SOAP, GraphQL, OAuth 2.0, and API versioning patterns.
Exercise the APIs you own directly with clients like cURL and Postman, and you can read and prototype against them rather than work from secondhand accounts.
A clear point of view on what changes when the caller is an AI agent and not a human developer.
Proven track record of using AI tools to build working artifacts yourself: prototypes, proofs of concept, API clients and consumers, automations, and workflows that feed directly into what engineering builds.
Make them tangible and interactive, bringing product requirements documents (PRDs) and specs to life and accelerating the development cycle.
Generate direction rather than wait for it.
Identify problems and form a point of view before being asked, build the artifact, and drive alignment across engineering and leadership without instruction.
Make sound calls on high-risk, hard-to-reverse decisions: API contracts, deprecations, and breaking changes where a wrong move costs customers years of pain.
Reason through the second- and third-order effects before they land, and you bring commercial discipline to the portfolio, including adoption metrics, usage telemetry, cost-to-serve analysis, and competitive awareness.
Write clearly across requirements documents, strategy papers, executive briefs, and developer content, and you engage directly in customer advisory calls and field escalations.
Adapt to the audience in front of you, and the way you frame the portfolio's direction and tradeoffs gets picked up and reused by partner teams across Clouds.
Hold a BS or MS in Engineering, Computer Science, or related fields, or have equivalent experience in technical leadership roles.

Nice To Haves

Prior experience at Salesforce or a comparable enterprise platform (SAP, Microsoft, ServiceNow, Workday), and familiarity with Salesforce Core APIs as a builder, architect, or consultant.
Experience with AI agent frameworks, Model Context Protocol, or agentic orchestration patterns, especially access control and authorization when the caller is a non-human principal.
Hands-on with API clients and command-line tooling (cURL, command-line interfaces), and able to read code and build lightweight prototypes against an API to pressure-test its design.
Experience with API management platforms (MuleSoft Anypoint, Postman, Kong, Apigee) or API governance programs (standards bodies, specification authoring, breaking-change detection).
Experience leading product teams across multiple time zones, with comfort driving decision velocity asynchronously alongside engineering counterparts in the US and abroad.

Responsibilities

Define and defend the long-range plan and vision for the Enterprise API area, looking several releases ahead to how the portfolio evolves as AI agents and Model Context Protocol (MCP) clients become the primary callers.
Decide what gets prioritized over the next 6 to 12 months and what gets cut, then build the business case that wins leadership's backing.
Ground the plan in the competitive landscape, and factor in where an AI-first or AI-infused approach differentiates the portfolio, unlocks value, and accelerates time-to-market.
Plan and implement the short-term (3 to 6 months) roadmap alongside engineering, architects, and tech writers.
Own product direction for how large data volumes move through and are queried across the platform: Bulk API evolution, data synchronization across the unified platform, Data Loader modernization, and the SOQL query language.
Partner with Cloud teams on ingestion patterns and usage analytics.
Own the trust posture for the portfolio, including API authentication modernization, legacy feature retirements, API scope evolution, API version retirement, and breaking-change governance.
When an API security issue escalates, you are the product lead accountable for the response.
Connect with Enterprise API customers at Dreamforce, TrailblazerDX, World Tours, community events, and advisory conversations.
Serve as the trusted subject-matter expert who engages customers and partners directly to understand their unmet needs.
Deliver the full release go-to-market suite each cycle, including release notes, demos, and enablement content (e.g. blogs, podcasts, live streams).
Act as the main point of contact for feedback and escalations on this highly technical portfolio across customers, partners, sales, and customer success.
Turn what you hear into evidence.
Find the pattern across accounts, tell the loud request apart from the broad trend, and decide where the signal changes the roadmap and where it does not.