Search all jobs
Browse jobsSan Diego, CA › Senior Systems Engineer

Senior Systems Engineer

Fuse Integration · San Diego, California, United States · Posted Jun 3, 2026

Apply on company site   Track it in JobSkout

Who we are:

Fuse builds innovative communications, networking, and computing solutions that improve the sharing of information, video, text, and voice among operators distributed throughout the airborne, maritime, and ground environments.  We are a technology firm creating in-house software, network and hardware solutions that support our noble cause of advancing warfighter capabilities with elegant, user-focused communications, networks, and software systems.

About This Role

Fuse is seeking a Senior Systems Engineer to lead mission definition, architecture clarity, and integration risk reduction across complicated tactical communication systems. This role elevates systems engineering maturity and ensures predictable system behavior under operational stress.

Chief Engineer (ChEng) Designation

Depending on mission scope, system complexity, and organizational need, this role may be designated as a Chief Engineer (ChEng). When assigned, the ChEng is responsible for maintaining coherence across mission intent, architecture, integration strategy, technical risk posture, and delivery readiness throughout the Define–Design–De-risk–Deliver lifecycle. The ChEng serves as the technical authority for system readiness, mission effectiveness, and engineering execution, driving uncertainty reduction through modeling, simulation, experimentation, and progressive integration.

Key Responsibilities

Define

Establish and maintain Design Reference Missions (DRMs) that anchor mission intent and guide hypothesis formation

Translate customer intent into system-level behaviors

Identify mission-level risks and architectural uncertainties

Design

Lead system architecture definition across disciplines

Define critical interfaces and integration strategies

Conduct and lead trade studies to support architecture decisions

Frame Epics as architectural hypotheses, explicitly stating assumptions, mission impact, and risk posture

Ensure risks and opportunities are surfaced and managed at the architecture level rather than at execution detail

De-risk

Design and drive modeling and simulation strategies

Lead early integration experiments to reduce uncertainty

Ensure traceability from mission intent through validation

Own system-level risk posture and drive cross-discipline alignment to reduce integration uncertainty early in the lifecycle

Drive integration learning cycles that validate or invalidate architectural assumptions

Ensure Stories and integration events produce evidence tied directly to mission intent

Deliver

Establish objective delivery readiness criteria based on integration risk retirement rather than schedule milestones alone

Ensure integration and verification activities are aligned with mission threads

Ensure delivery readiness is based on validated system behavior under stress conditions, not artifact completion

Communicate confidence levels in system performance based on evidence generated through spiral iterations

Establish criteria for delivery readiness based on risk posture

Drive resolution of cross-discipline issues impacting system behavior

Ensure traceability from mission intent through formal validation

Communicate system risk posture to program and technical leadership

When designated as Chief Engineer (ChEng), serve as the technical authority for mission readiness, engineering execution, and cross-discipline architectural coherence across the system lifecycle

Apply on company site