Responsibilities
- Own the roadmap for Pulumi Cloud's platform services, partnering with engineering leadership to sequence long-term architectural bets against near-term customer pull.
- Define what agent-ready means for a control plane — what an autonomous system needs to safely read config, obtain credentials it never sees, scope its own blast radius, and leave behind an audit trail a security team will accept.
- Drive the ESC roadmap: how configuration and secrets flow from source systems to every consumer, what atomicity and consistency guarantees we make, and how ESC becomes the default rather than an add-on.
- Own the trust boundary. Permissions models, RBAC granularity, and audit are where enterprise deals are won and lost, and where the requirements are least forgiving. Treat them as product, not compliance overhead.
- Shape the Registry and Components ecosystem — how teams find, publish, version, and trust reusable infrastructure, and what changes when the consumer is an agent rather than a person.
- Treat the API as a first-class product. Our OpenAPI surface, the Pulumi Service Provider, webhooks, and VCS integrations are how platform teams and agents extend Pulumi; their ergonomics deserve the same care as any UI.
- Balance the enterprise customers who need governance, isolation, and provable controls against the individual developers who made Pulumi worth adopting in the first place — without quietly making the product worse for either.
- Instrument what you ship, define the metrics that matter, and feed usage evidence straight back into roadmap decisions.
- Drive end-to-end delivery from idea to GA to adoption, working across Engineering, Design, Marketing, Sales, Support, and the open source community.
Requirements
- 7+ years in product management, engineering, or technical program management, with real time on platform, API, or infrastructure products.
- Taste in API and platform design — you have opinions about resource modeling, versioning, backward compatibility, error semantics, and what separates an API people build on from one they tolerate.
- Comfort in the security and identity domain: secrets handling, permissions models, tenancy, and audit. You don't need to have been a security PM, but you should find these problems interesting rather than tedious.
- Strong technical instincts and the ability to hold your own with senior engineers on architectural tradeoffs — consistency guarantees, failure modes, migration paths.
- A track record of ramping fast in unfamiliar technical domains and forming real opinions, not just synthesizing other people's.
- Demonstrated ability to ship high-quality products in ambiguous, complex problem spaces.
- Experience working cross-functionally with Sales, Marketing, and Support in a product-led growth environment.
- Excellent written and verbal communication. We work asynchronously and in writing; clear thinking on the page is the job.
- A commitment to building inclusive, collaborative teams.
Nice to Have
- Background in secrets management, identity providers, IAM, policy engines, or adjacent security infrastructure.
- Experience shipping products that agents or automated systems consume — MCP servers, tool-use surfaces, or machine-facing APIs.
- Familiarity with IaC tooling (Terraform, CloudFormation, Crossplane, CDK) and a point of view on what Pulumi does differently.
- Background in cloud infrastructure, DevOps, SRE, or platform engineering.
- Experience working with or contributing to open source projects and communities.
Work Arrangement
Remote (Worldwide) — Seattle, remote
