Senior Staff Inbound Product Manager, ServiceNow SDK -Platform Agentic Build Lifecycle Team

ServiceNow is an AI control tower for business reinvention, providing an AI platform that connects AI, data, and workflows for enterprises. The Senior Staff Inbound Product Manager will own the multi-year strategy and roadmap for the ServiceNow SDK and Fluent APIs, shaping them into a developer platform and operational foundation for human and autonomous AI-agent application development. The role involves defining product direction, packaging and governance, cross-functional alignment, and executive-level technical strategy.

Responsibilities:

• Own the multi-year product strategy and roadmap for the ServiceNow SDK and Fluent APIs: the CLI, the TypeScript DSL, the credentialed instance client, and the packaging model that together define how metadata gets authored, built, and installed
• Define the SDK's evolution from an authoring substrate to an operational one so that an agent, autonomous or human-driven, can reason about what already exists before it changes anything
• Set product direction for AI-agent consumption of the SDK as a first-class use case, not a side effect of good documentation
• Own the packaging and governance path from authored TypeScript to a deployed, audited change
• Partner with teams owning other SDLC products and their stakeholders so that every SDK-driven authoring path, whether the developer is a person in VS Code or an agent driving the CLI, still terminates in a governed, auditable artifact while maintaining the native-git developer experience
• Represent SDK and Fluent strategy to senior stakeholders
• Set the technical and strategic bar for Staff-level PMs across the developer platform portfolio. Operate independently across ambiguous scope, and bring other PMs along on judgment calls rather than needing them handed down
• Model an AI-first way of working for the team. Use agentic coding tools, Claude Code or equivalent, directly in daily work: prototype against the SDK and Fluent yourself, read and write the TypeScript your product produces, and bring firsthand experience building with the same tools your external developers and agents use

Requirements:

• Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry
• 12+ years of product management experience, including several years owning a developer platform, SDK, CLI, or API/language surface at enterprise scale, with a track record of setting technical strategy independently at Staff or Sr. Staff scope rather than executing a roadmap someone else defined
• Working fluency in TypeScript and genuine hands-on comfort reading and writing code, plus direct, regular personal use of AI coding agents such as Claude Code, Cursor, or Windsurf in your own workflow, not just familiarity with them as a market category
• Experience owning or closely partnering on compiler, DSL, or static-analysis tooling. Understands build-time type checking, the tradeoffs between declarative and imperative configuration models, and why 'errors caught at build time' is a product feature, not an implementation detail
• Deep experience with developer-facing package and artifact ecosystems, npm-style registries, semver, dependency resolution, CLI design, ideally having shipped and evolved a CLI or SDK used by an external developer community or in open source
• Working knowledge of agent tool-use protocols, including Model Context Protocol, and experience building product surfaces explicitly for AI-agent consumption, documentation and schemas as agent context, skill files, structured API references, in addition to human-readable docs
• Proven ability to build and defend an executive-level strategic case, and to navigate cross-business-unit governance and ownership disputes at the VP and SVP level, driving alignment across genuinely contested organizational boundaries without formal authority
• Experience with enterprise change-management or release-governance systems and the tradeoffs between developer velocity and auditability, ideally including systems that gate deployment through a controlled artifact, such as a change set model
• Comfort operating in an open-source or open-ecosystem context, with an understanding of what makes external developers, system integrators, and partners adopt a new API surface instead of routing around it
• Exceptional written and verbal communication, able to translate deep technical tradeoffs, typed APIs, static analysis, agent protocol design, into a strategy that lands with engineers and with executive stakeholders in the same conversation