Full-Stack Software Engineer

About the role

About Agile Defense

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 #:

Job Title for Careers Page: Full-Stack Software Engineer

Location: National Capital Region (2 positions) | Honolulu, HI (1 position) | On-site

Clearance Level: TS/SCI eligibility required

Required Certification(s): None

Summary Target Effect Pairing (TEP) gives USPACOM Joint Fires AI recommendations, through the Maven Smart System, that commanders can trace, explain, and audit. Those recommendations are only useful if operators can compare options and see the reasoning in time to act on it. That puts weight on both ends of the stack: services that recompute quickly when inputs change, and interfaces that present dense comparisons and geography clearly.

You build across both. On the back end that means microservices, message-driven architecture, and workflow and agent orchestration. On the front end it means React and TypeScript interfaces, including geospatial views. You implement the Senior UX Designer's workflow designs and work with the program's architects, the Systems Integration Engineer, and the Product Manager/Fires SMEs.

The team works in two locations, requirements are still taking shape, and all work happens in secure facilities.

What Success Looks Like

Objective 1: In the first 90 days, ship a feature end to end in the program's environment

- Your code is reviewed, merged, and deployed in the secure environment.

- You can explain the operational workflow behind the feature to a Fires SME in their terms.

- You know where the program's architecture and interfaces constrain your work, and you build within them.

Objective 2: Build services that recompute fast enough for operators to explore options

- When an operator changes an input, the updated recommendation arrives inside their workflow rather than after it.

- Performance is measured, and regressions are caught before release.

- Each orchestration step leaves a record that can be traced during an audit.

Objective 3: Build interfaces that let operators compare recommendations and see the reasoning

- Comparative and geospatial views match the design, and usability testing confirms operators can read them.

- From the interface, an operator can trace any recommendation to the inputs and logic behind it.

- Changes requested after operator feedback ship in the next increment.