Full-Stack Software Engineer

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.

Objective 4: Raise engineering quality across both locations

Your tests and reviews catch defects before government testing does.

Documentation lets an engineer in the other location pick up your work without a handoff meeting.

The code you write is covered by automated tests that run in the delivery pipeline.

What You Bring

Minimum Qualifications

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

Preferred Skills

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.

WORKING CONDITIONS

All work takes place in secure facilities. Two positions are based in the National Capital Region and travel 50% of the time. One is based in Honolulu with the USPACOM-based development team.


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.

 

• Happy - Be Infectious. Happiness multiplies and creates a positive and connected environment where motivation and satisfaction have an outsized effect on everything we do.
• Helpful - Be Supportive. Being helpful is the foundation of teamwork, resulting in a supportive atmosphere where collaboration flourishes, and collective success is celebrated.
• Honest - Be Trustworthy. Honesty serves as our compass, ensuring transparent communication and ethical conduct, essential to who we are and the complex domains we support.
• Humble - Be Grounded. Success is not achieved alone, humility ensures a culture of mutual respect, encouraging open communication, and a willingness to learn from one another and take on any task.
• Hungry - Be Eager. Our hunger for excellence drives an insatiable appetite for innovation and continuous improvement, propelling us forward in the face of new and unprecedented challenges.
• Hustle - Be Driven. Hustle is reflected in our relentless work ethic, where we are each committed to going above and beyond to advance the mission and achieve success.