Staff Product Manager, Developer Lifecycle & Tooling

Temporal · Enterprise · United States · Product Management

Staff Product Manager for Temporal, focusing on developer lifecycle and tooling. This role will own the CLI, testing framework, deploy safety tooling, and local development environment, with a significant focus on how these tools integrate with and support AI agent orchestration and AI-assisted development. The product manager will define strategy and make key product decisions in ambiguous areas related to testing, deployment safety, and the evolution of developer tooling in the context of AI.

What you'd actually do

  1. Define and drive the strategy for developer tooling across Temporal's platform - not just ship features, but make opinionated bets on how developers should test, debug, and deploy durable applications
  2. Own the testing story end-to-end: make the strategic call on test infrastructure direction, define canonical patterns, and drive toward tests that developers actually trust
  3. Own the deploy safety story: determine the right approach for pre-deploy compatibility checking and drive it from concept to shipped product
  4. Unify the CLI into one coherent tool - for humans and AI agents - and define what the CLI becomes as AI-assisted development accelerates
  5. Collapse the getting-started experience so new developers reach a working project in minutes with production-realistic patterns

Skills

Required

  • 8+ years of product management experience
  • significant time on developer tools, SDKs, CLIs, or developer infrastructure
  • defined and driven a tooling strategy
  • made opinionated bets about how developers should work and shipped them
  • made build-vs-buy or keep-vs-deprecate decisions on developer-facing infrastructure
  • can articulate the tradeoffs years later
  • can hold a coherent vision across multiple tools that ship on different timelines to different language ecosystems
  • comfortable operating in ambiguity
  • write clearly, decide quickly, and change your mind when the evidence says to
  • partnered with engineering leadership, not just engineering teams
  • influence technical direction, not just product requirements
  • understand the difference between developer tooling and production operations, and you set that boundary clearly

Nice to have

  • personally built or contributed to a CLI, testing framework, CI pipeline, or developer tool
  • Experience with distributed systems, workflow engines, or durable execution concepts
  • worked on cross-language or cross-platform developer tools
  • Familiarity with the competitive landscape: Restate, Inngest, Durable Objects, Step Functions

What the JD emphasized

  • own the developer lifecycle
  • own the CLI
  • own the testing framework
  • own the deploy safety tooling
  • own the local development environment
  • own the getting-started experience
  • define Temporal's testing strategy
  • define deploy safety approach
  • define the developer tooling vision
  • high-ambiguity role
  • opinionated bets
  • tests that developers actually trust
  • drive it from concept to shipped product
  • Unify the CLI into one coherent tool
  • define what the CLI becomes as AI-assisted development accelerates
  • Collapse the getting-started experience
  • partner directly with engineering leadership
  • shape team priorities and technical direction
  • developer tooling
  • SDKs
  • CLIs
  • developer infrastructure
  • defined and driven a tooling strategy
  • made opinionated bets about how developers should work and shipped them
  • made build-vs-buy or keep-vs-deprecate decisions on developer-facing infrastructure
  • hold a coherent vision across multiple tools
  • comfortable operating in ambiguity
  • biggest questions in this role don't have obvious answers yet
  • partnered with engineering leadership
  • influence technical direction
  • difference between developer tooling and production operations
  • set that boundary clearly

Other signals

  • AI agent orchestration
  • AI-assisted development