Product Manager/Fires SME
Listed on 2026-11-01
-
Business
AI Business & Operations, AI Evaluation
At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next.
Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests.
Requisition #:1959
Job Title: Product Manager/Fires SME
Clearance Level:TS/SCI eligibility required
Required Certification(s):None
About Agile Defense LocationLocation:Honolulu, HI | National Capital Region | On-site
SummaryA commander looking at a recommended target and effect pairing asks two questions: why this, and why now? Target Effect Pairing (TEP) is a capability for USPACOM Joint Fires, built on the Maven Smart System, that answers both with AI recommendations a targeting staff can trace, explain, and audit. It speeds up capabilities analysis and the commander's decision and force assignment, while every inherently governmental decision stays with a human.
Engineers can build the software. They can't tell on their own whether it reflects how joint targeting is really done.
That judgment is yours. You bring operational targeting experience and the working habits of a product manager, and you turn joint targeting doctrine, JFE and JTCB workflows, and target development standards into requirements, user stories, and acceptance criteria. You work with a Senior UX Designer, software engineers and architects, and a Technical Program Manager who owns backlog priority and government acceptance.
You own whether what gets built is operationally right.
Requirements are still forming, and much of the team has never worked in targeting. The recommendations this capability produces will also be independently assessed for quality, so output that merely looks reasonable won't hold up.
What Success Looks Like Objective 1:In the first 90 days, give the team an accurate picture of how USPACOM targeting runs today
- Government targeteers review your map of the current workflow, from target development through nomination, approval, and assessment, and confirm it is accurate
- Engineers and designers can say where each JFE or JTCB decision happens, and who holds the authority for it, without coming to you first
- Where the command's practice departs from doctrine, the gap is written down along with which one the product follows and why
Turn targeting doctrine and decision authority into requirements the team can build and test
- Engineers build from your user stories and acceptance criteria without a rework cycle over operational intent
- Every inherently governmental decision point appears in the requirements, with the human approval it needs spelled out
- Feature requests reach the backlog framed as the operational problem behind them, not only as the feature someone asked for
- The Technical Program Manager gets priority recommendations grounded in operational value, with the reasoning visible
By month six, prove that recommendations hold up before a commander sees them
- Representative scenarios and acceptance criteria test whether a pairing recommendation is complete, relevant, and defensible
- Each recommendation answers why this and why now, with its assumptions and limits stated plainly enough for a targeteer to challenge
- Operational problems show up in your scenarios first, rather than in government evaluation
By the end of year one, make operator feedback what steers the product
- Demonstrations with targeteers, JFE and JTCB staff, and J32 operators produce…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).