About the job
Exciting opportunity for a Principal Product Manager to lead the core platform for Adobe CX Enterprise. Own agentic agent loops, tool protocols, and developer surface, driving innovation in AI-driven enterprise solutions. Collaborate with engineering and research teams to shape the future of agent development and enterprise trust & safety.
Responsibilities
Own the runtime agentic core loop and the contracts around it — tool protocols (MCP, A2A), skills, knowledge grounding, and the enterprise trust & safety guarantees.
Define how agents are evaluated, overridden, and improved in production. The override and feedback loop is the moat; you'll design it.
Drive the developer surface for both Agent Developers (who define skills) and Agentic App Developers (who compose them). Docs, CLI, local dev/prod parity, the works.
Work with the team on architectural calls on what we build vs. adopts from the open ecosystem. Hold the line on control plane ownership (auth, entitlements, governance) without reinventing what the ecosystem already does well.
Partner with Applied Science and ML Eng on agent quality benchmarks that actually predict customer outcomes — not vanity evals.
Work directly with the engineering leads, design, and field teams across the org. Translate between research, engineering, and GTM without losing precision.
Qualifications
Minimum
7+ years in PM, with real depth in AI platforms, developer tools, or infra products. Application PMs who haven't shipped platform contracts won't be a fit.
You can speak fluently about MCP, skills, harness patterns, agent loops, tool use, context engineering, and evaluation. You've built or extended something in this space — not just read about it.
You've used Claude Code, Cursor, or equivalent agentic dev environments seriously enough to have informed opinions about what they get right and wrong.
You think in contracts and interfaces. You understand why ABI stability matters, why plugin/marketplace/tool terminology needs precision, and why "just use the model" is rarely the answer at the platform layer.
You can hold a position with engineering leads and back it with technical reasoning, and you can change your mind when the argument is better.
You write tersely. You strip adjectives. You calibrate by audience — exec memo, eng spec, customer doc — without losing the through-line.
Preferred
CS or engineering background strongly preferred. Hands-on coding ability is a plus, not a requirement, but you should be able to read a skill manifest or an MCP server and know what it does.