Staff Product Manager, Nexus at Temporal Technologies in Seattle, Washington

Job description

• Application
• We’re hiring a Staff Product Manager, Nexus to own the next phase of Temporal Nexus: landing the current product foundation, expanding adoption across strategic accounts, and defining the roadmap for Nexus as Temporal’s durable connectivity layer.
• This person will take over an active, technically deep product area with real customer usage and a fast-moving roadmap. The immediate work is to land the in-flight Nexus developer experience and operator-control work with quality. The longer-term mandate is to shape the next wave: Connector Ecosystem, Service Hub, and Agentic Communication Fabric.
• This is not a “write specs and wait” role. The PM will need to build trust quickly with engineering, customers, field teams, and GTM; understand the product hands-on; turn messy customer evidence into sequencing decisions; and create the narrative that helps Temporal, customers, and partners understand where Nexus is going.
• You want to build important infrastructure. You’re motivated by products that sit in the critical path for customers and developers. You want to work on something foundational, technically deep, and category-defining.
• You operate with ownership. You don’t measure your job by meetings, specs, or process completed. You measure it by customer outcomes, product adoption, team clarity, and whether the right work actually ships.
• You move fast without being reckless. Nexus sits in the reliability layer for mission-critical systems. You know when to push for speed, when to insist on rigor, and how to keep momentum without compromising customer trust.
• You’re resilient in ambiguity. You’re energized by unclear ownership, messy customer evidence, technical constraints, and hard sequencing calls. You don’t need a perfect roadmap handed to you — you help create one.
• You raise the bar for the people around you. You write clearly, invite feedback, give it directly, and help teams make better decisions. You make complex work easier for others to understand and execute.
• You put developers and customers first. You want to understand how real teams build distributed systems, where their current tools fail them, and what would make Temporal indispensable in their architecture.
• Nexus is past GA and entering breadth. Adoption is real, but the next challenge is expansion across more teams, accounts, and use cases.
• The foundation is landing now. Developer experience, connector foundations, and operator controls are the near-term unlocks.
• The next wave is strategically important. Connector Ecosystem, Service Hub, and Agentic Communication Fabric could define how Temporal participates in the modern AI and service-connectivity stack.
• You’ll shape an important product category. Nexus sits between durable execution, service-to-service communication, platform engineering, and AI systems.

Responsibilities

• Nexus product strategy and roadmap. Prioritize the work that makes Nexus the durable connectivity layer across teams, namespaces, services, and AI systems.
• Current execution. Drive completion of in-flight work such as the new Nexus developer experience, Standalone Nexus Operations, connector foundations, caller identity, rate limits, and payload encryption.
• Customer discovery and evidence. Stay close to design partners and strategic customers like Netflix, Duolingo, and Miro.
• Developer and operator experience. Balance SDK ergonomics, schema-first contracts, codegen, service discovery, security, visibility, and control-plane needs.
• Cross-functional launch and enablement. Make sure everyone in the company understands the problems Nexus solves and knows how to sell / deploy / support it.
• Success metrics. Define adoption and momentum measures: activated accounts, completed Nexus operations, shared-service usage, SDK coverage, design-partner progress, and field readiness.

Requirements

• Staff-level product judgment. 8+ years in product management or equivalent experience turning ambiguous and technical strategy into shipped outcomes.
• Strong technical depth. Ability to reason about distributed systems, workflow orchestration, service-to-service communication, APIs, SDKs, identity, and authorization.
• Developer-platform experience. Experience with infrastructure, platforms, integrations, APIs, SDKs, service mesh, API gateways, or cloud developer products.
• Customer and field orientation. Comfortable working directly with senior technical customers and enabling GTM teams on a complex product.
• Excellent writing and narrative skills. Able to create crisp strategy docs, roadmap narratives, launch materials, and decision memos.
• Execution discipline. Can inherit a complicated roadmap, clarify ownership, unblock decisions, and keep the team focused.
• Experience with Temporal, workflow orchestration, durable execution, service mesh, API gateways, or distributed systems
• Experience with schema registries, code generation, SDK design, or developer portals
• Experience with AI infrastructure, agent platforms, MCP/tool registries, or agentic systems
• Prior DevRel, Solutions Architecture, technical marketing, or partner-facing product experience

Skills

Required

• Product management
• Technical strategy
• Distributed systems
• Workflow orchestration
• Service-to-service communication
• APIs
• SDKs
• Identity
• Authorization
• Infrastructure
• Platforms
• Integrations

Preferred

• Temporal
• Durable execution
• Service mesh
• API gateways
• Schema registries
• Code generation
• SDK design
• Developer portals