Senior Principal Product Manager, Docker

• We are looking for someone who builds, not just plans. You should be comfortable prototyping, getting your hands dirty with early product iterations, and improvising when things don’t go as expected
• The right candidate has shipped developer tools or infrastructure products, understands how the agentic AI ecosystem is evolving, and thrives in the ambiguity of building something genuinely new
• Experience. 10+ years of product management experience, with at least 5 years on developer tools, infrastructure, or platform products
• Deep technical fluency. You can read an architecture diagram, understand container and VM runtimes, and have a working knowledge of how AI agents, LLMs, and protocol-level tool connectivity work. You don’t need to be a hypervisor engineer, but you need to hold your own with one
• Proven ability to ship 0-to-1 products. You have taken a product from idea through launch in a fast-moving environment. You know how to operate when there is no playbook
• Builder mentality. You prototype, you sketch architectures, you test early ideas with customers before the spec is done. You are a doer, not just a thinker
• Strong product sense and UX instincts. You care about the developer experience at a deep level — from API design to CLI ergonomics to error messages
• Strategic thinking with execution follow-through. You can set a multi-year vision and also write the spec for what ships next sprint
• Comfort with ambiguity. This space is new and moving fast. You thrive when the answer isn’t obvious and you have to go find it
• Excellent communication. You can write a crisp product brief, present to executives, and debate technical tradeoffs with engineers — all in the same day
• Experience growing and monetizing products at scale. You have been part of taking a product from early adoption to meaningful revenue, and you understand the pricing, packaging, and go-to-market decisions that make that happen

Desirable

• This is a 0-to-1 role. You will define the product strategy and own the roadmap for a new platform that sits at the intersection of AI, containers, and developer experience
• You will work with a small, high-velocity team spanning engineering, design, and go-to-market to figure out what to build, ship it, learn from it, and iterate
• The early signal is already in market — Docker Sandboxes is one of the fastest-growing new products in Docker’s history — and the opportunity ahead is much larger
• Own the product strategy. Define the vision, roadmap, and success metrics for Docker’s AI & Agent Platform. Make hard tradeoff decisions about what to build, what to defer, and what to cut
• Build from zero. This is a new platform. You will define the product from the ground up — writing the first specs, prototyping with engineering, validating with customers, and iterating rapidly based on what you learn
• Drive from conception through delivery. Write requirements, work with engineering to scope and prioritize, ship iteratively, and measure outcomes. You don’t hand off specs and wait — you are in the details
• Define how pieces of the agentic ecosystem fit together. Agents need secure execution, tool connectivity, model access, governance, and observability. You will define how these capabilities compose into a coherent platform — and where Docker’s boundaries are
• Think beyond developers. Agents are becoming essential for everyone who builds, deploys, and operates software. You will ensure the platform serves the full range of people who need agents to succeed — from individual developers to platform teams to enterprise operators
• Define the developer experience. Work with design and engineering to ensure that our AI products are intuitive, powerful, and meet people where they are — whether in the CLI, IDE, or CI pipeline
• Collaborate across Docker. You will work cross-functionally to ensure coherent product experiences and go-to-market alignment
• Influence technical direction. Partner with engineering leadership on architecture decisions. You don’t need to write the code, but you need to understand the technical tradeoffs and have informed opinions about them
• Represent the customer. Engage directly with developers, enterprises, and partners. Bring their voice into every product decision
• Overcome blockers. When something is in the way — a missing integration, an unclear market signal, a technical constraint — you figure out a path forward. You don’t wait for someone else to solve the problem