opengreenhousea16z
Staff Product Manager, Developer Lifecycle & Tooling
Temporal Technologies
LocationUnited States - Remote Opportunity, United States
WorkplaceFull
Last observed2026-06-23 22:50:29.480619
Job ida16z-temporal-technologies:greenhouse:5124670007
About Us Temporal is an open source programming model that can simplify code, make applications more reliable, and help developers focus on the important things like delivering features faster. We are on a mission to be the reliable foundation of every developer’s toolbox, and are building the team that will make that happen. Our values guide us —they are present in how we show up, make decisions, and work together to make an impact. We’re curious, driven, collaborative, genuine and humble. Temporal is growing and we are looking for those who share our values, challenge 'standard' thinking, and want to influence our future. If you have a passion for improving the developer experience, building world-class open-source software and communities, and want to be a part of our amazing team, we'd love to hear from you! About the role Developers should have a clear path from writing their first workflow to safely evolving their hundredth in production. Today, that path still requires too much setup, deep Temporal expertise, and manual validation. We’re hiring a Staff Product Manager, Developer Lifecycle & Tooling, to own the strategy and roadmap for a coherent developer lifecycle: getting started, local development, testing and replay, deploy safety, code evolution, and the CLI experience. You’ll partner with the product portfolio lead on platform priorities and with engineering and SDK leads to turn strategy into tooling that works across Temporal’s supported SDKs and production workflows. In the first year, success means faster setup, more production-realistic local development, trusted testing and replay, earlier detection of unsafe code changes, and a more coherent CLI experience. What you’ll do Own the product strategy and roadmap for Temporal’s developer lifecycle and tooling charter Define developer experience goals for onboarding, local development, testing, replay, code evolution, deploy safety, and CLI workflows, then measure progress against them Translate customer, field, support, and open-source community signals into tooling bets that make Temporal easier to start with, test, debug, evolve, and deploy Partner deeply with engineering and SDK teams to ship tooling across the CLI, local development environment, testing infrastructure, replay workflows, and deploy safety tools Make opinionated product calls about where Temporal should provide built-in tooling, where we should integrate with existing developer workflows, and where documentation, templates, or examples are the right answer Shape a coherent cross-SDK experience across Go, Java, TypeScript, Python, .NET, and other supported languages without blocking language-specific ergonomics Define the external story for Temporal’s developer lifecycle through positioning, documentation, examples, launch narratives, and close partnership with Developer Relations, Marketing, and field teams Ship improvements with the templates, migration guidance, examples, and adoption support developers need to use them successfully What we’re looking for 8+ years of product management experience, with significant time on developer tools, SDKs, CLIs, testing infrastructure, CI/CD, or developer platforms Experience turning ambiguous developer workflow problems into clear strategy, roadmap, success measures, and shipped outcomes Strong technical fluency in software delivery workflows, testing, CI/CD, SDKs, CLIs, local development, or distributed systems High standards for developer experience across CLIs, SDKs, APIs, documentation, examples, onboarding paths, and production workflows Ability to translate emerging developer workflows, including AI-assisted coding and agentic tools, into requirements for CLIs, testing, deploy safety, and documentation Ability to balance open-source developer experience, Temporal Cloud adoption, and enterprise production needs Strong product storytelling for technical audiences, with the ability to explain not just what changed, but how developers should use it a
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.