Sr. Principal, Product Manager - Agentic & Platform

We are seeking a Sr. Principal, Product Manager to own the agentic and platform capabilities of the Conduct platform. This is a senior individual-contributor role. You will set product direction and do the work directly. You will not manage a team. You will lead through technical depth, a high craft bar, and influence across product and engineering.

The mandate has two connected halves. First, define the API, MCP, and headless surfaces that let sophisticated customers and AI agents build on the platform rather than around it. Second, own the non-functional requirements, scale, performance, reliability, multi-tenancy, and security, that the largest regulated financial institutions require to move a deal through diligence. Both require a product leader who treats platform contracts and non-functional requirements as product decisions, not engineering handoffs.

You will own the product strategy, roadmap, and execution for this surface, partnering directly with Engineering, AI/ML, Data Science, Professional Services, and the customer-facing organizations to define what the platform is, who it serves, and how it wins.

What you'll do?

Platform and Agentic Product Strategy

-
Own the strategy and roadmap for Conduct’s agentic and platform capabilities: the API, MCP, and headless workflow surfaces that serve both human users and AI agents on a unified workflow layer and audit trail.

-
Define the API surface as product: alert queues, review actions, reason-code taxonomies, workflow configuration, and the programmatic contracts that agents call. These are product decisions, not engineering ones.

-
Build the extensibility model: how sophisticated customers and external or agentic systems build on the platform, including developer-facing documentation and the packaging that frames what is a subscription tier, what is usage-based, and what justifies a premium price point.

-
Partner with the AI/ML product team on the boundary between the intelligence layer and the workflow layer that agents call. Keep the workflow contract clean so agents call the Conduct workflow layer while the intelligence layer powers it from beneath.

Non-Functional Requirements and Platform Readiness

-
Own non-functional requirements as first-class product requirements: scale, performance, reliability, and the security posture that Tier 1 financial institutions require in diligence. Treat security, telemetry, and reliability as product surfaces.

-
Translate the diligence and regulatory-examination bar of the world's largest banks into a defensible non-functional roadmap. In a regulated compliance product, a gap in any of these carries real risk.