Nibrs Jobs (NOW HIRING)

About the CAD / RMS / JMS Division

Coreforce's CAD / RMS / JMS Division delivers mission-critical public safety software - Computer-Aided Dispatch (CAD), Records Management (RMS), and Jail Management (JMS) - to law enforcement, corrections, and communications agencies across the United States. Our products sit at the center of 911 response, officer safety, and criminal justice workflows. Product decisions in this division affect how quickly officers receive information in the field, how accurately records move through the justice chain, and how reliably agencies meet state and federal compliance obligations.

Role Overview

We are hiring a Senior Product Owner to own the platform and integrations surface of our CAD, RMS, and JMS portfolio, with particular emphasis on National Incident-Based Reporting System (NIBRS) compliance. This role is cross-cutting: rather than owning a single application, you will be responsible for the shared capabilities that connect our products to one another, to state and national law enforcement networks (TLETS, LEADS, NCIC, Nlets, and similar), to state-level incident-reporting programs, to the FBI's NIBRS submission requirements, and to the broader public safety ecosystem.

You will operate as a senior individual contributor reporting to the Director of Product Management. You will own the backlog for your area end to end, partner directly with engineering, UX, sales, implementation, and customer agencies, and contribute materially to the roadmap and competitive positioning of the division's portfolio. Product Ownership at Coreforce is treated as a career discipline in its own right, not a waystation to Product Management. We are looking for someone who wants to deepen their mastery of this craft - the backlog, the discovery work, the release cadence, the customer relationships - over years, and who will grow in scope, influence, and compensation as they do.

Key ResponsibilitiesBacklog Ownership & Agile Delivery

• 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. Our teams operate in a hybrid Agile model; adapt your approach to each team's norms while maintaining consistent ceremony quality and delivery predictability.
• 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.

NIBRS & Incident Reporting Compliance

• 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. Every state that operates its own incident-reporting program (Indiana I-NIBRS, Texas TIBRS, California CIBRS, Pennsylvania PA-NIBRS, and others) layers its own data elements, validation rules, and submission cadence on top of the federal standard. Track these 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.

Customer & Agency Discovery

• Conduct discovery directly with law enforcement, dispatch, and corrections customers. Ride-alongs, dispatch-center sits, and jail walkthroughs are part of the job, not optional color.
• 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.

Launch Readiness & Customer Rollout

Coreforce runs a continuous integration and continuous delivery (CI/CD) model. Code flows to production on an ongoing cadence rather than through scheduled release trains, so the Product Owner's role is to own launch readiness and customer-visible rollout - not to coordinate release packaging.

• 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.

AI-Assisted Product Development

• Use AI tooling fluently as part of your day-to-day product work. We expect our Product Owners to actively use AI to draft and refine user stories and acceptance criteria, produce UI mockups and interactive prototypes, and stand up working proof-of-concept applications to pressure-test ideas before engineering commits to them.
• 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.

Competitive Analysis & Roadmap Input

• 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.

Required Qualifications

• 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). You can read a NIBRS specification, reason about segment/data-element changes, and have a point of view on how compliance work should be sequenced against customer impact.
• 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.

Strongly Preferred Qualifications

Candidates with public safety domain experience will be given strong preference; candidates from adjacent GovTech (courts, corrections, emergency management, federal/state compliance-heavy SaaS) will also be seriously considered. We specifically value the following:

• Deep NIBRS and state-program experience: you have led product work through a federal NIBRS transition, a state IBRS certification, or an ongoing compliance cadence with a state UCR program office; you understand where specifications are ambiguous and how agencies actually get submissions accepted.
• CI/CD and continuous delivery experience: you have operated in a true continuous-delivery environment and are comfortable with feature flags, progressive rollout, and launch-readiness practices appropriate to a shop that ships every day rather than on a release train.
• CJIS / FedRAMP / StateRAMP / GovRAMP experience: you have worked within, or taken a product through, one or more of these compliance regimes and understand how security certification timelines interact with roadmap commitments.
• Integrations and API product experience: you have owned integration surfaces at the product level - ideally including connections to state or national law enforcement networks such as TLETS, LEADS, NCIC, or Nlets, or analogous regulated data exchanges.
• Legacy-to-SaaS migration experience: you have shepherded customers off on-premise or legacy platforms onto modern SaaS, including the pricing, data migration, and trust-rebuilding work that entails.
• UX partnership sensibility: you have worked closely with designers on officer-facing, dispatcher-facing, or other high-stakes operational UIs where glanceability, error cost, and cognitive load matter more than visual polish.

Success Metrics - First 12 Months

• First 90 days: Developed a working understanding of the CAD, RMS, and JMS portfolios; established relationships with engineering leads, key customers, and cross-functional peers; taken ownership of the platform/integrations backlog with a documented prioritization framework.
• 6 months: Delivered at least one meaningful platform or integration release on committed dates; stood up a repeatable discovery cadence with at least three reference agencies; contributed substantively to at least one competitive or packaging decision; established a working inventory of NIBRS and state incident-reporting obligations across the customer base.
• 12 months: Recognized across the division as the authoritative owner of the platform, integrations, and NIBRS compliance surface; measurable improvement in delivery predictability, first-pass NIBRS submission acceptance for RMS customers, and customer-reported satisfaction on integrations; clear contribution to at least one compliance milestone (e.g., GovRAMP, CJIS-related, or a state IBRS certification) and one ecosystem partnership.

What We Offer

• A senior seat at the table in a division undergoing active strategic investment - with visibility to senior leadership across the business.
• Work that matters: the software you own will be used by officers, dispatchers, and corrections staff in live operational environments.
• A defined Product Owner career track. We invest in Product Owners as a distinct discipline, with growth in scope, influence, and compensation over time - not a mandatory jump into Product Management to advance.

Competitive base salary, performance-based incentive compensation, comprehensive benefits, and remote-first flexibility.