Principal Product Operations Manager
Product Operations exists to give product teams the systems, data, and processes they need to plan, prioritize, and deliver well — the same way Sales Ops supports Sales or DevOps supports Engineering. This role sits at the center of that discipline, owning four things: the tools and systems product teams plan and work in, the reporting and analytics that give everyone visibility into what’s happening, the process that makes planning and delivery repeatable instead of reinvented pod by pod, and the ongoing work of keeping strategy and execution connected as priorities shift.
We run Product Operations as a hybrid centralized/embedded model: some Product Ops work sits centrally and serves every product team consistently, while other Product Ops work sits embedded inside individual product lines, close to their day-to-day priorities. This role sits in the centralized hub — you’re the shared systems, process, and reporting engine that every embedded product manager and product ops partner relies on, rather than being dedicated to any single product line.
We’re a small team, so this role is intentionally broad. At larger companies, “owns the tools,” “owns the reporting,” and “owns the process” are sometimes split into two or three separate roles. Here, one person does all of it, with the flexibility to shift emphasis as priorities and team size change over time.