The opportunity
You'll own the path from commit to running production software on Render: the build system, the deploy experience, and the primitives that make delivery composable, including reusable build artifacts, multi-service deployment, deployment pipelines, and infrastructure as code. In…
What you'll do
Shape build and deploy experiences that feel simple from hundred-line: prototypes to architectures with hundreds of services, and work seamlessly whether the thing shipping code is a person or an AI agent.
Own the build and deploy system end to end. Set the roadmap and own the: outcomes: build and deploy speed, deploy success rate, and time to diagnose a failure.
Define and ship foundational primitives such as reusable build artifacts and: application-level deployment, rather than accumulating one-off features.
Drive build and deploy performance work: caching, incremental builds, monorepo workflows, and build compute options for workloads that need more capacity.
Make failures fast to diagnose: failure classification, surfacing root cause at the point of failure rather than buried in logs, and the metrics that tell us whether debuggability is improving.
Talk to customers constantly, translate what you hear into patterns across: the customer base, and decide what to build now, later, or not at all.
What they're looking for
- You have 6+ years of product management experience, with time spent on: developer tools, infrastructure, or platform products.
- You have significant depth in the delivery domain: CI/CD, build systems and caching, containers and registries, deploy strategies (canary, blue-green, rollbacks, health checks, zero-downtime deploys), and infrastructure as code. You can hold your own in an architecture conversation and tell a load-bearing technical constraint from a preference.
- You set direction that holds up over multiple quarters, drive alignment: across engineering, design, and go-to-market without owning those teams, and raise the bar for how product work gets done around you.
- You think in primitives and platforms. When a customer asks for a one-off: fix, you look for the reusable capability underneath it.
- You're comfortable with ambiguity and limited data. You form opinions from: customer conversations, analytics, and technical constraints, and you can defend a prioritization under capacity limits.
- You communicate clearly with everyone from a platform engineer evaluating: your build system to a CTO asking about competitor benchmarks, and you know how to say no while preserving trust.
- You obsess over developer experience and hold a high bar for speed,: reliability, and legibility in the tools you ship.
