Senior Product Manager, Integrations

Roadmap and Prioritization

You'll define what Maven integrates with, which systems we support, at what depth, and in what order.

Underlying Integration Platform

You'll own the underlying integration platform, including tooling, frameworks, and patterns that let Maven ship new integrations faster over time and let customers extend the platform themselves.

Depth vs. Breadth Tradeoffs

You'll own the depth versus breadth tradeoffs, such as a read-only Salesforce connector versus full read/write integration with custom object support.

Enterprise Customer Engagement

You'll be in the room when customers describe their stack, translating those descriptions into integration requirements that engineering can build against.

Actions and Tool Use

You'll own how actions are defined, tested, and made safe at enterprise scale, ensuring that Maven's agents can perform the necessary tasks within customer systems.

Partner Ecosystem Strategy

You'll develop the strategy for which platforms warrant formal partnerships, which stay in our own build queue, and how we approach marketplace listings on Salesforce AppExchange, Zendesk Marketplace, and similar channels.

Cross-functional Partnership

You'll work closely with GTM to convert integration depth into enterprise wins, and with customer success to turn integration issues into product improvements rather than support tickets.

Qualifications

• 5-7+ years of product management experience, with meaningful time on integrations, APIs, developer platforms, or iPaaS products.
• Direct experience with the systems Maven agents touch: CRMs (Salesforce, HubSpot), ticketing (Zendesk, ServiceNow, Freshdesk), knowledge bases (Confluence, Notion, Guru), commerce (Shopify, Stripe), and identity (Okta, Auth0).
• Familiarity with technical building blocks: REST and GraphQL APIs, webhooks, OAuth, rate limits, event streams, and the failure modes that come with each.
• Experience operating in both startup and scaled environments, knowing when to build in-house versus when to buy or partner.
• Ability to extract requirements from messy customer conversations and turn them into Product Requirement Documents (PRDs).
• Problem-solving mindset, not just a project management focus.
• Enthusiasm for AI, LLMs, and autonomous agents, with a clear point of view on how integrations change when the caller is an agent instead of a human developer.
• Strong communication skills, able to hold your own with engineering while also translating for enterprise stakeholders and GTM.