Chief Systems Engineer

E-Space•Saratoga, CA

13h•Onsite

About The Position

The Chief Systems Engineer (CSE) holds the highest technical authority in the Space Systems Organization below the CTO. This is the single point of accountability for spacecraft system architecture, all Interface Control Documents, the Verification & Validation Plan, Requirements Compliance closure, and the system-level AI&T campaign. With Space Systems Electrical Engineering (SSEE) as an organic fifth function, the CSE also holds sole authority over the spacecraft-level electrical architecture and the electrical ICD framework to which every hardware VP and Semiconductor Development designs. The scope extends beyond the spacecraft — the CSE owns the program digital thread connecting requirements through design, verification, as-built records, and on-orbit telemetry.

Requirements

15+ years progressive systems engineering experience in the space industry, with at least one flight project carried from SRR through on-orbit operations.
Constellation program experience — direct accountability for spacecraft-level architecture, cross-vehicle interface management, or system-level verification across a multi-satellite fleet.
ICD and design review leadership — direct responsibility for requirements traceability and verification closure; presented and defended technical baselines at formal design reviews (SRR, PDR, CDR, QR) before a standing review board.
Digital communications background — demonstrated background in RF link design, phased array systems, modem/waveform, or OSI Layer 1–2 protocol architecture.
Prior subsystem depth — hands-on subsystem leadership (payload, bus, or ground) before transitioning to systems engineering.
Team leadership — demonstrated record of building and developing multi-discipline systems engineering teams, including recruiting and retaining Principal Engineers.
U.S. persons (U.S. citizens, lawful permanent residents, and individuals granted asylum or refugee status).
Candidates must demonstrate the ability to make and defend binding technical decisions under uncertainty — including accepting residual risk with documented rationale — and to hold a technical position under schedule or cost pressure.
Experience presenting to and defending technical baselines before external review boards is required.

Nice To Haves

Candidates must demonstrate the ability to make and defend binding technical decisions under uncertainty — including accepting residual risk with documented rationale — and to hold a technical position under schedule or cost pressure.
Experience presenting to and defending technical baselines before external review boards is required.

Responsibilities

System architecture — requirements decomposition, allocation to subsystem budgets, ICD development and baseline control, and trade space management across mass, power, pointing, and cost.
Verification & Validation — V&V plan development, TPM definition and tracking, requirements compliance matrix management, environmental test planning (TVAC, vibration/acoustic, EMI/EMC), and test data disposition.
Electrical systems — spacecraft-level power distribution, grounding and shielding, EMI/EMC (MIL-STD-461 or equivalent), signal integrity, and connector/harness standards; sufficient depth to own the electrical ICD framework and evaluate design compliance across all subsystems.
Integration & Test — AI&T campaign planning and execution, FlatSat and HIL facility operations, environmental test readiness review process, and anomaly investigation and disposition.
Configuration management — configuration baseline control, CCB process administration, and engineering change order management across both engineering and production phases.
Digital thread / MBSE — connecting requirements, design artifacts, verification evidence, and as-built records in a traceable data architecture; working familiarity with MBSE tools (DOORS NG, Cameo, SysML) and digital thread architectures.
Make and defend binding technical decisions under uncertainty — including accepting residual risk with documented rationale — and to hold a technical position under schedule or cost pressure.
Presenting to and defending technical baselines before external review boards.