What You'll Do

• Own inbound product direction for your area. Research emerging agentic AI capabilities, attacker techniques, and adjacent standards (MCP, A2A, OWASP agentic-security guidance, agent identity frameworks) to determine what MARS for Agents should build next across the agent registry, Claude integration, Microsoft Copilot integration, MCP Server, MCP Proxy, and LLM proxy.
• Turn signal into engineering-ready requirements. Translate market, customer, and competitive input into clear PRDs, user stories, and acceptance criteria — using LLM-based tools to synthesize call notes, support tickets, standards documents, and usage data into prioritization insight, while retaining full accountability for the judgment calls and the accuracy of what you write.
• Own and groom the backlog. Make day-to-day prioritization calls across your surfaces within the strategic guardrails set by the Head of Product, and partner directly with engineering through the full build cycle: refinement, in-sprint questions, review, and release.
• Validate before you specify. Use AI coding assistants, MCP clients, and agent runtimes hands-on to prototype and stress-test proposed behavior — so requirements are grounded in how agents actually behave, not just how they are documented to behave. Define success metrics for what you ship and track them post-release.
• Enable the field. Brief technical support and solutions engineering on new and existing capabilities, and maintain current capability documentation for your area that clearly separates documented and shipping facts from planned work and open questions, so the field never over-promises. Be the trusted authority on what your part of MARS does today, what is coming, and what it deliberately does not do yet.
• Engage customers, sales, and marketing. Join customer and prospect conversations periodically to gather requirements, pressure-test positioning, and support technical evaluations; support the sales team with technical Q&A, competitive objection-handling, and input on proposals and decks; and work with product marketing on messaging, positioning, and launch content.
• Run competitive analysis that changes decisions. Continuously track competitors relevant to MARS for Agents — network/SSE-SASE incumbents (Palo Alto Networks, Zscaler, Cloudflare, Netskope), agent-identity and IAM players (Okta, CyberArk), MCP gateway vendors, and emerging agent-security pure-plays — and maintain a clear point of view on where MARS leads, where it currently trails, and what capabilities are commoditizing. Feed those findings directly into requirements, positioning, and roadmap prioritization.

Functional Competencies

Required:

• 6–10+ years of product management or product owner experience, ideally in B2B SaaS, enterprise infrastructure, or security software, including a track record of owning a complex, technical product area end to end.
• Demonstrated ability to write clear, engineering-ready requirements (PRDs, user stories, acceptance criteria) and to own a backlog end to end for a technically complex product surface.
• Comfort operating with a high degree of autonomy. This role receives strategic direction rather than daily instruction, and the person in it should be able to take a goal and drive it through research, requirements, engineering partnership, and launch across multiple related surfaces at once — with the support of a collaborative product and engineering team.
• Comfort operating at high velocity. Our engineering organization runs agile at a fast cadence, and this role also helps bring the process and rigor needed to make the product scalable, so both muscles matter.
• Solid working knowledge of AI agent technology: how LLMs and AI agents operate, the difference between autonomous and human-in-the-loop (hybrid) agents, tool and function calling, and — specifically — the MCP (Model Context Protocol) ecosystem (servers, clients, tool calls) at a depth sufficient to write requirements for an MCP Server and an MCP Proxy, not just discuss them conceptually.
• Real cybersecurity background, with working familiarity in areas such as identity and access management, proxy and gateway architectures (forward proxy, reverse proxy, secure web gateway / SSE / SASE), and content or traffic inspection. Deep specialization in every area is not required, but enough fluency to engage credibly with engineering and with technical customers is.
• Hands-on, regular personal use of AI tools — for example, Claude, ChatGPT, Claude Code / Cowork, GitHub Copilot, or similar — including some exposure to how they use MCP or other tool-calling integrations.
• Strong written communication, since the role produces a steady stream of specs, FAQs, and internal enablement material.

Preferred / Nice to Have:

• Working knowledge of the Microsoft 365 Copilot ecosystem: M365 Copilot, Copilot Studio agents, and Microsoft's Entra/Azure agent identity plane — enough to scope and write requirements for a two-way integration in which MARS augments Microsoft's own agent governance rather than competing with it.
• Prior product ownership of an identity or registry system, a proxy or gateway product, or an API/integration platform.
• Direct experience with MCP, LLM/agent tool-calling architectures, or building integrations with Claude or other frontier model providers.
• Familiarity with OWASP frameworks, including emerging OWASP guidance for agentic AI security.
• Experience directly supporting a technical sales motion — SE enablement, competitive battlecards, customer discovery calls.
• Experience at a company scaling a new product line or product category from early traction.
• Experience using AI-assisted research or analysis tooling as part of a regular product workflow — for example, synthesizing customer feedback at volume, or building lightweight prototypes to validate requirements.
• Bachelor's degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience.

Menlo Mindsets

The Menlo Mindsets serve as our strategic operating system, directly linking our daily behaviors to the business results we need to achieve by defining exactly "how" we do our work. By establishing this clear, shared standard, they empower our most successful employees to consistently drive the innovation and accountability required for our long-term success.

Proactive Leadership — I do not settle for the status quo. I take ownership, make informed decisions, and proactively communicate to drive results while empowering others to do the same.

What it looks like in this role: You receive strategic direction, not a task list — and you are expected to decide what your surfaces should build next, act on it, and keep the Head of Product and your partners informed as you go.

**Straight Talk — I share honestly and transparently, actively seeking diverse perspectives while encouraging the same