A 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

Objective 2: Turn targeting doctrine and decision authority into requirements the team can build and test

Objective 3: By month six, prove that recommendations hold up before a commander sees them

Objective 4: By the end of year one, make operator feedback what steers the product

What You Bring

Minimum Qualifications

Preferred Skills

WORKING CONDITIONS

All work takes place in secure facilities. One position sits with the development team in Honolulu. One sits in the National Capital Region and travels 50% of the time.

Environmental Conditions

Work is primarily performed in professional office, Government, and technical development environments. This position requires regular on-site collaboration in the San Diego area, including work with Government and development stakeholders at or in support of NIWC-Pacific. Periodic travel may be required to support operational stakeholders and other mission activities. Work may occur in secure facilities with restrictions on personal electronic devices and remote connectivity.

Strength Demands

Sedentary to light physical demands associated with professional office and technical work environments. Occasional movement or transport of laptops, documents, and other standard work materials may be required.

Physical Requirements

Regular use of computers and standard office equipment; ability to participate in meetings, technical working sessions, and collaborative development activities for extended periods; ability to communicate effectively in person and through approved electronic means; and ability to travel as required.