- Chainguard secures the software supply chain, and we’re standing up a new team to build a new product inside it
- Agents now write a large and growing share of the world’s code, and they inherited a CI system designed for humans who push a few times a day. Write, push, wait in a queue, reinstall the same toolchain, scrape the logs, try again. Agents iterate far more often than people do, so they feel every minute of that, and the workarounds they’ve grown are worse than the thing they’re working around. We don’t think the fix is a faster version of the CI you already have. We think CI gets rebuilt for agents, and that’s what we’re doing
- The product isn’t launched, so a job post is the wrong place for the details. What we can tell you now: the team is small, the hard technical pieces already run in production inside Chainguard, and you’d be driving the product direction
- Strategy and roadmap. Own the vision, strategy, and roadmap for the product. Decide what we build first, what comes next, and what we’re not going to do
- 0→1 product work. Take this from a system that works for us to a product customers buy and use. Bring structure to problems that don’t have any yet, make the tradeoff calls, and get things in front of users before they feel finished
- How agents actually build software. Go deep on how developers and their agents write, test, review, and ship code today, including the parts nobody blogs about. Most of what’s written about agentic development is aspirational. You’ll work from what people really do
- Design partners. Find the teams whose agent fleets are big enough to hurt, get the product into their hands early, and turn what they tell you into priorities
- Developer experience. Adoption is the whole game here. Own how the product gets tried, configured, and lived with, so a team can move onto it without running a migration project
- Launch. Positioning, naming, docs, the pricing model, and the story, with Product Marketing and the rest of Product. You’re also the person who says when it’s ready
- Cross-functional leadership. Partner with Engineering, Experience, Product Marketing, and other Product leaders, and keep a small team pointed at the same thing while the space shifts underneath it
Benefits
- Equity/stock options
- Unlimited PTO
- Remote work with flexible coworking and team meetup opportunities
- Home office and internet stipend
- 100% health/dental/vision insurance coverage for you and your family
5+ years of product management experience on developer-facing, infrastructure, security, or similarly technical productsYou write well. We make decisions in documents hereYou don’t need to be a GitHub Actions expert. We’re not building a better Actions, and years of workflow YAML isn’t the experience we’re hiring for. Knowing where it breaks isExperience taking a technical product from an early idea through launch and iterationComfort with a deeply technical engineering team. You can hold your own in a design discussion and disagree with an engineer about a tradeoffYou can operate on your own in a fast-moving area with no established playbookYou’ve built agent tools. Something agents use, or something people use to build with agents: a coding agent, an agent framework or harness, MCP servers, eval systems, or developer tooling meant to be driven by a model instead of a person. This is the requirement that matters most to usYou talk to developers directly and often, and you can tell the difference between technology people find interesting and a product they’ll actually adoptJudgment about what to leave out. A new product dies from doing too much as easily as from doing too littleYou know CI from the inside. Builds, tests, caches, runners, artifacts, merge gates, and the specific reasons pipelines end up slow, flaky, and expensive. You should have opinions about whyExperience with developer platforms, build systems, remote execution, or hosted development environmentsYou’ve run coding agents in production at real volume, or built the systems that keep them from breaking thingsExperience with containers, Kubernetes, registries, or other cloud-native infrastructureExperience with products that serve individual developers and large enterprises at the same timeYou’ve built security products for developers, and you know how fast a developer abandons one that gets in the wayYou’ve owned your own team’s CI at some point and hated it
#J-18808-Ljbffr