SENIOR PRODUCT OWNER

Coreforce•Baton Rouge, LA

2d•Remote

About The Position

Coreforce is an innovative SaaS company providing digital solutions for frontline professionals. Our products, body cameras, in-car videos, mobile routers, and digital evidence systems, help public safety officers and first responders save lives, strengthen community trust, and enhance accountability. Join Coreforce and use your product management skills to support innovative technology that strengthens communities.

Requirements

5+ years of product ownership or product management experience in B2B SaaS, with a meaningful portion in regulated, mission-critical, or government-facing software.
Working knowledge of NIBRS - federal UCR/NIBRS requirements and at least one state-level incident-reporting program (e.g., I-NIBRS, TIBRS, CIBRS, PA-NIBRS).
Demonstrated ownership of a backlog across multiple release cycles, including writing acceptance criteria, running refinement, and leading Agile ceremonies with engineering.
Hands-on fluency with AI tools for product work - using AI to draft and refine user stories, generate mockups and prototypes, and build proof-of-concept applications that accelerate discovery and validation.
Strong written and verbal communication - you can brief a sales leader, a customer agency head, and a senior engineer in the same afternoon and be credible to all three.
Comfort operating in a hybrid Agile environment where ceremony varies by team; you bring structure without being dogmatic about framework.
Willingness and ability to travel occasionally (approximately 5-10%) to customer agencies, internal offices, and industry conferences (e.g., IACP, APCO, NSA, ACA).
Ability to pass a background check sufficient to work with CJIS-regulated data and customer environments.

Nice To Haves

Deep NIBRS and state-program experience
CI/CD and continuous delivery experience
CJIS / FedRAMP / StateRAMP / GovRAMP experience
Integrations and API product experience
Legacy-to-SaaS migration experience: UX partnership sensibility

Responsibilities

Own the backlog for platform and integration capabilities across CAD, RMS, and JMS.
Write clear, testable user stories and acceptance criteria grounded in officer, dispatcher, and corrections workflows.
Lead Agile ceremonies for your teams - including backlog refinement, sprint planning, sprint review, and retrospectives - and conduct daily standups with engineering.
Make trade-off decisions in the moment - scope, sequencing, technical debt, and defect prioritization - and communicate those decisions clearly to stakeholders.
Track and communicate delivery against committed dates, particularly for overdue commitments and customer-specific obligations.
Own NIBRS as a product surface.
Maintain deep working knowledge of the FBI UCR Program's NIBRS specification, data elements, segment structures, edit checks, and submission requirements.
Translate specification changes into concrete backlog items, with the goal that RMS customers can submit clean, accepted NIBRS data on first pass.
Own state-level incident reporting requirements alongside federal NIBRS.
Track variations across our customer footprint and ensure product capabilities keep pace.
Partner with state UCR/SIBRS program offices as needed to clarify requirements, anticipate rule changes, and represent Coreforce credibly in technical discussions.
Support agency-level NIBRS certification by ensuring our tooling produces data that passes state and federal edit checks, and by giving implementation and customer success teams the documentation and diagnostics they need when submissions are rejected.
Anticipate the roadmap by tracking FBI CJIS Division communications, state program bulletins, and industry working groups so that NIBRS-related changes enter the backlog ahead of customer pressure, not after it.
Conduct discovery directly with law enforcement, dispatch, and corrections customers.
Translate operational realities - officer safety, glanceability on an MDT, CJIS constraints, shift-change workflows - into product requirements engineers can build against.
Build a durable feedback loop with implementation, support, and customer success so that field signal reaches the backlog without distortion.
Own launch readiness and customer-visible rollout.
Own feature-flag strategy for your area: when a capability is safe to merge, who sees it at each stage, and the criteria for progressive rollout from internal to beta agencies to general availability.
Define launch readiness for each customer-visible capability - including acceptance, documentation, enablement for implementation and support, and communication to customer agencies - so that what ships is ready to be used, not just technically deployed.
Own the external rollout narrative in partnership with marketing, customer success, and sales: what customers see in a given window, what they need to do, and how success is measured.
Partner with sales and pre-sales to support deals, respond to RFP requirements, and contribute to competitive win/loss analysis.
Use AI tooling fluently as part of your day-to-day product work.
Shorten the discovery-to-validation loop by building lightweight POCs yourself - or with AI assistance - so customer and stakeholder feedback lands on something concrete rather than a slide.
Apply judgment, not just velocity when using AI: you know when AI-generated artifacts are ready to share, when they need human rework, and how to keep sensitive customer and CJIS-regulated content out of tools that should not see it.
Maintain current intelligence on competing CAD, RMS, JMS, and ecosystem platforms.
Translate that intelligence into concrete roadmap recommendations, not slideware.
Contribute to portfolio strategy on packaging, pricing inputs, and differentiation - particularly in areas touching DEMS, BWC integration, connected devices, and state/federal network modernization.
Support security and compliance roadmap items including GovRAMP, StateRAMP, FedRAMP, and CJIS-aligned initiatives.