Principal Product Manager - Developer Platforms & AI Ecosystems

Axon Axon · Enterprise · Office, WA · 2012 Sensors - DEMS

Principal Product Manager to define and own the strategy and roadmap for Axon's developer ecosystem, focusing on exposing the Evidence.com platform to third-party tools, AI agents, and agency integrations through APIs and an AI agent protocol layer. This role involves building the Partner API program, defining the MCP server and client strategies for AI agent interaction, and scaling the developer experience.

What you'd actually do

  1. Define and own the multi-year platform strategy for Evidence.com's developer ecosystem — how the evidence repository is exposed to third-party tools, AI agents, and agency-built integrations through APIs and an emerging AI agent protocol layer.
  2. Build and maintain the roadmap for the Partner API program, including tiered access levels, versioning, usage-based pricing, and the evidentiary integrity standards (chain of custody, audit logging, PII handling) that any integration must meet.
  3. Own the MCP server roadmap: define the set of discrete, permissioned, callable tools that expose Evidence.com's capabilities to AI agents, working with engineering on schema design and with legal and compliance to bound what is expressible.
  4. Define the MCP client strategy: how Evidence.com ingests context from external systems — RMS, CAD, court management — at query time, without requiring pre-built integrations for every agency's technology stack.
  5. Build and scale the developer experience: portal, sandbox, documentation, and the partner certification program that governs who can build on the platform and under what conditions.

Skills

Required

  • 10+ years of product management experience, with a meaningful portion building developer-facing products — APIs, SDKs, developer portals, integration platforms, or two-sided ecosystems where third-party builders are a primary customer.
  • Strong technical fluency: able to read API specs, participate substantively in schema design discussions, and hold your own in architecture and security reviews — without needing to write production code.
  • Demonstrated ability to define strategy in environments where the standard or category is still forming; energized by the absence of a playbook rather than relying on benchmarking what already exists.
  • Proven track record of building trust and driving decisions across engineering, legal, security, and go-to-market stakeholders — particularly when those stakeholders are in genuine tension with each other.
  • Excellent written and verbal communication; able to operate as an external-facing representative of the platform with partners and ecosystem participants.
  • Strong knowledge of API security patterns, access control models, and compliance requirements in enterprise or regulated industries.

Nice to have

  • Flexibility to travel

What the JD emphasized

  • AI agent integration layer
  • AI agent protocol layer
  • AI agents operating inside agency workflows
  • any compatible AI tool an agency deploys to retrieve evidence
  • MCP server roadmap: define the set of discrete, permissioned, callable tools that expose Evidence.com's capabilities to AI agents
  • MCP client strategy: how Evidence.com ingests context from external systems
  • strategic ambiguity
  • organizational consequence
  • Principal-level judgment and seniority
  • evidence repository is exposed to third-party tools, AI agents, and agency-built integrations
  • evidentiary integrity standards (chain of custody, audit logging, PII handling)
  • permissioned, auditable interface
  • define the set of discrete, permissioned, callable tools that expose Evidence.com's capabilities to AI agents
  • define the MCP client strategy: how Evidence.com ingests context from external systems — RMS, CAD, court management — at query time, without requiring pre-built integrations for every agency's technology stack.
  • partner certification program that governs who can build on the platform and under what conditions.
  • Strong knowledge of API security patterns, access control models, and compliance requirements in enterprise or regulated industries.

Other signals

  • AI agent integration layer
  • AI agents operating inside agency workflows
  • any compatible AI tool an agency deploys to retrieve evidence
  • MCP server roadmap: define the set of discrete, permissioned, callable tools that expose Evidence.com's capabilities to AI agents
  • MCP client strategy: how Evidence.com ingests context from external systems