Full-Stack Software Engineer
- Compensation
- Not disclosed
- Location
- Washington, D.C.
- Work setup
- Onsite
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- Not specified
- Category
- Fullstack
- Posted
Skills
Must have
- Proven ability to drive progress and create clarity in fast moving, ambiguous environments. Ability to maintain required TS/SCI access.
Nice to have
- You have built and shipped full-stack applications in production, with back-end services in Go, Java, or Python.
- You have built microservices or message-driven systems that held up under real load.
- You have built data-dense interfaces in React and TypeScript that people relied on to compare options.
- You have built geospatial visualizations with CesiumJS, Mapbox, or similar.
- You have worked with workflow or agent orchestration frameworks.
- You have tuned performance and can point to the measured result.
- You have built from a designer's work and pushed back constructively when something wouldn't work.
- Experience in secure or classified DoW environments, or with Maven Smart System, is a plus.
Full description
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 LikeObjective 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.