Product Operations Manager: Practice & Enablement
Product Operations Manager: Practice & Enablement
Overview
EDS runs the infrastructure behind off-duty and extra duty programs for ~250 law enforcement agencies nationwide. We are scaling our product team from a handful of people into a real product organization, and we are doing it AI-first: throughput comes from better systems, tooling, and automation, not just more headcount. This role builds the operating system that team runs on. You will not own roadmaps or define features. You will own how product flows through EDS: the cadences, the tooling, the data, and the feedback loops that keep PMs building and leadership informed. If you have built the operating layer for a growing product team and you like making everyone around you more effective, read on.
What You'll Own
The product team's operating rhythm: planning cadences, roadmap reviews, and OKR cycles that run on schedule without anyone chasing them
The product tech stack: Jira and Confluence today, Pendo for analytics, and a dedicated product management tool as the team scales
Consistent access for every PM to usage data, dashboards, and research insights, so no one is blocked waiting on numbers
The intake and prioritization process across the team: you run the mechanics and keep the data honest, PMs and product leadership make the calls
Cross-functional dependency tracking between product, engineering, design, and go-to-market as those handoffs grow
PM onboarding and the team's standard ways of working: templates, definitions of done, and the playbooks that get a new hire productive fast
What You'll Build in Year One
A structured feedback pipeline that turns stakeholder signals, customer feedback, NPS, and support tickets into roadmap-ready input (this matters: most signal reaches product through account managers and sales, not directly from officers or customers)
A documented operating rhythm: cadence calendar, roadmap review format, and OKR process the whole team runs against
A single source of truth for product data: Pendo dashboards and usage views that PMs and leadership trust and use without asking
A reporting layer that keeps leadership current on roadmap progress without PMs spending their week building status decks
A PM onboarding kit that gets a new product manager shipping in weeks, not months
What We're Looking For
5+ years in product operations, product management, or a closely related discipline running the operating layer for a product team
Advanced Jira and Confluence administration: you have set these tools up and optimized them, not just used them
Experience standing up planning cadences, roadmap reviews, and OKR or equivalent goal processes
Strong with product analytics and reporting: you can build dashboards and turn raw usage and feedback data into structured, decision-ready input
Comfort operating where signal is mediated: most user feedback at EDS comes through account managers and sales, not end users
A bias for systems over heroics: you reduce friction so other people move faster
Strong written communication: you will produce newsletters, changelogs, and stakeholder reporting that people actually read
Candidates residing in North Carolina or Texas are preferred
What Makes You Stand Out
Built the product operating system for a team scaling from a few PMs into a real organization
Used gen AI to automate reporting, synthesize feedback, or cut the admin load on a product team
Background in tech-enabled services, workforce management, field services, or public safety: software that supports human service delivery, not pure SaaS
Experience coordinating user research logistics (recruiting, scheduling, repository) in the absence of a dedicated researcher
Familiarity with PE-backed operating discipline and board-level reporting cadences
Why EDS
You will not be buried in ticket hygiene. You will build the practice a growing product team runs on. We have real revenue, real agencies, and a roadmap with teeth, and we are scaling the team to match. The systems you build will decide how fast we can move and how clearly leadership sees what is coming. It is a high-leverage role on a small, senior team, where the work you do shows up in everyone else's output.
Overview
EDS runs the infrastructure behind off-duty and extra duty programs for ~250 law enforcement agencies nationwide. We are scaling our product team from a handful of people into a real product organization, and we are doing it AI-first: throughput comes from better systems, tooling, and automation, not just more headcount. This role builds the operating system that team runs on. You will not own roadmaps or define features. You will own how product flows through EDS: the cadences, the tooling, the data, and the feedback loops that keep PMs building and leadership informed. If you have built the operating layer for a growing product team and you like making everyone around you more effective, read on.
What You'll Own
The product team's operating rhythm: planning cadences, roadmap reviews, and OKR cycles that run on schedule without anyone chasing them
The product tech stack: Jira and Confluence today, Pendo for analytics, and a dedicated product management tool as the team scales
Consistent access for every PM to usage data, dashboards, and research insights, so no one is blocked waiting on numbers
The intake and prioritization process across the team: you run the mechanics and keep the data honest, PMs and product leadership make the calls
Cross-functional dependency tracking between product, engineering, design, and go-to-market as those handoffs grow
PM onboarding and the team's standard ways of working: templates, definitions of done, and the playbooks that get a new hire productive fast
What You'll Build in Year One
A structured feedback pipeline that turns stakeholder signals, customer feedback, NPS, and support tickets into roadmap-ready input (this matters: most signal reaches product through account managers and sales, not directly from officers or customers)
A documented operating rhythm: cadence calendar, roadmap review format, and OKR process the whole team runs against
A single source of truth for product data: Pendo dashboards and usage views that PMs and leadership trust and use without asking
A reporting layer that keeps leadership current on roadmap progress without PMs spending their week building status decks
A PM onboarding kit that gets a new product manager shipping in weeks, not months
What We're Looking For
5+ years in product operations, product management, or a closely related discipline running the operating layer for a product team
Advanced Jira and Confluence administration: you have set these tools up and optimized them, not just used them
Experience standing up planning cadences, roadmap reviews, and OKR or equivalent goal processes
Strong with product analytics and reporting: you can build dashboards and turn raw usage and feedback data into structured, decision-ready input
Comfort operating where signal is mediated: most user feedback at EDS comes through account managers and sales, not end users
A bias for systems over heroics: you reduce friction so other people move faster
Strong written communication: you will produce newsletters, changelogs, and stakeholder reporting that people actually read
Candidates residing in North Carolina or Texas are preferred
What Makes You Stand Out
Built the product operating system for a team scaling from a few PMs into a real organization
Used gen AI to automate reporting, synthesize feedback, or cut the admin load on a product team
Background in tech-enabled services, workforce management, field services, or public safety: software that supports human service delivery, not pure SaaS
Experience coordinating user research logistics (recruiting, scheduling, repository) in the absence of a dedicated researcher
Familiarity with PE-backed operating discipline and board-level reporting cadences
Why EDS
You will not be buried in ticket hygiene. You will build the practice a growing product team runs on. We have real revenue, real agencies, and a roadmap with teeth, and we are scaling the team to match. The systems you build will decide how fast we can move and how clearly leadership sees what is coming. It is a high-leverage role on a small, senior team, where the work you do shows up in everyone else's output.