Systems Integration Engineer

A target and effect pairing recommendation is only as good as the data under it. Target Effect Pairing (TEP), built on the Maven Smart System for USPACOM Joint Fires, draws from systems it does not own, including command and control systems and a simulation engine, at more than one classification level. Commanders need to trace, explain, and audit every recommendation, which means every input has to show where it came from.

You build TEP's external integrations and data services: schemas, REST and gRPC interfaces, MCP servers, ETL and streaming pipelines, record linkage, data lineage, and handling for data at multiple classification levels. You work with the Lead Software Architect, who owns the interface control documents and canonical data model, and with the full-stack engineers who build on your services.

Two integration tracks, the simulation engine and the operational systems, each wait on government approvals that move independently. Expect to prepare work before the access exists to finish it.

What Success Looks Like

Objective 1: In the first 90 days, get the first external data flowing through a defined interface

• The schema and interface are agreed with the Lead Software Architect and match the canonical data model.
• The pipeline runs in the program environment, with lineage recorded from the source.
• Every government approval each integration track depends on is listed, with its status and owner.

Objective 2: Deliver both integration tracks as government approvals arrive

• When access opens, the integration connects quickly because the interface, test data, and tests were ready in advance.
• A delay on one track does not stall the other.
• Interface changes from external systems are caught before they break anything downstream.

Objective 3: Make the data behind every recommendation traceable

• Lineage from source system to recommendation can be shown to an auditor on request.
• Record linkage results carry measured confidence, and errors are visible rather than silent.
• MCP servers and APIs are documented well enough that other engineers and agents use them without asking you.

Objective 4: Handle data across classification levels without spills or rework

• Multi-classification data handling passes security review the first time.
• Data stays correctly marked at every step through the pipeline.
• Wherever data crosses a classification boundary, the handling is documented clearly enough for a security reviewer to follow it.

What You Bring

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

Preferred Skills

• You have designed schemas in Protobuf, JSON Schema, or Avro that several teams built against.
• You have built REST or gRPC services, and MCP servers if you have had the chance.
• You have run ETL and streaming pipelines in production.
• You have implemented record linkage or data lineage and can explain how you measured whether it was right.
• You have handled data at multiple classification levels in DoW environments.
• You have integrated with systems you did not control, under a government approval process.
• Experience integrating with Maven Smart System or command and control systems is a plus.

WORKING CONDITIONS

All work takes place in secure facilities. This position is based 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.