Senior Software Architect; Technical Lead

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.

1960

Senior Software Architect (Technical Lead)

Honolulu, HI | On-site

TS/SCI eligibility required

None

Target Effect Pairing (TEP) is a capability for USPACOM Joint Fires, built on the Maven Smart System, that gives commanders AI recommendations they can trace, explain, andaudit, while every inherently governmental decision stays with a human. Part of the team building it sits in Honolulu, near the users ther the software fits how targeteers actually work gets decided there as much as anywhere.

You lead engineering for the Honolulu team. The program's Lead Software Architect, based in the National Capital Region, owns the overall architecture and has final technical authority. You turn that architecture into working software in Honolulu: you make the design calls within it, review code, and keep the Honolulu engineers, the Senior UX Designer, and the Product Manager/Fires SMEs building one product with the team in the National Capital Region.

This is a hands-on lead role. The work spans two locations, some integration work waits on government decisions, and everything happens in secure facilities.

• Honolulu engineers build to the same interfaces, data models, and standards as the National Capital Region team, with no local variant.
• Design decisions made in Honolulu are written down, and the Lead Software Architect rarely has to revisit them.
• Code from both locations integrates without a cleanup sprint.

• Feedback from operators reaches the backlog with a technical approach and an estimate attached.
• UX designs get built as designed, or the tradeoff is agreed with the designer before code is written.
• Questions about operational intent go to the Fires SMEs early, so they don't show up later as defects.

• Releases from the Honolulu team deploy in the secure environment without late rework.
• Every recommendation the software produces can be traced to its inputs and logic, so an audit doesn't require new work.
• Recompute is fast enough that operators can change an input and see the updated recommendation inside their own workflow.

• Code review catches problems before integration, and defects found in government testing decline over time.
• Honolulu engineers make sound design decisions without escalating each one.
• Engineers you helped hire and onboard are productive within their first month.

• Proven ability to drive progress and create clarity in fast moving, ambiguous environments. Ability to maintain required TS/SCI access.

• You have led an engineering team building distributed, event-driven, or microservice systems, and stayed hands-on while doing it.
• You have worked inside an architecture someone else owns and improved it through interface control documents, API contracts, or shared data models.
• Yo…