About this role
As a Staff Mission Architect at Impulse , you will define the mission-level logic that guides our future systems before any vehicle architecture is conceived. This role begins where customer inputs are vague or incomplete — broad mission challenges, loosely defined operational goals, partial technical desirements, or emerging government concepts needing structure. You will transform these uncertainties into quantitative, defensible mission requirements that shape early pursuits and enable disciplined architecture development. You are the bridge between Business Development and Program Management/Engineering. Business Development brings customer ambitions; you convert them into mission-level requirements; Advanced Mission Concepts Engineers (AMCEs) then develop conceptual system solutions; and Program Management later matures these into full products. You ensure every mission has a clearly articulated analytical foundation before systems design begins. This role includes direct engagement with U.S. Government customers and program offices, and travel up to approximately 25%. Lead mission-level analysis across payloads, constellations, ground systems, C2, cyber, and operational context to define mission success criteria and performance thresholds Convert vague customer desires into quantitative “small-r” requirements that guide downstream conceptual design Develop and employ mission-level modeling and simulation tools for things such as coverage analysis, NIIRS scoring, gap times, latency modeling, mission availability, constellation behavior, and resilience assessments Produce derived requirements for mission elements such as sensitivity, ΔV envelopes, timeline constraints, communications/latency performance, revisit and coverage metrics, and payload-specific performance parameters Partner with AMCEs to evaluate conceptual solutions against mission requirements; assess mission impact of engineering-driven tradeoffs, cost reductions, replenishment strategies, or performance adjustments Act as the mission architecting lead during early capture phases — shaping mission definitions, requirement frameworks, evaluation criteria, and success metrics before vehicle or system concept formulation Support Business Development by generating mission-analysis content for white papers, BAAs, RFIs, challenge submissions, and requirements-shaping discussions with government customers and FFRDC/UARC partners Conduct red-team-style assessments to identify mission weaknesses, operational risks, adversary constraints, and system-of-systems considerations that influence requirement prioritization Ensure mission architectures incorporate realistic operational constraints such as ground station availability, crosslink integration, cyber/hardening implications, adversary counters, and resilience needs Build reusable mission-analysis models and tools so requirements development compounds rather than restarts with each pursuit Work with industry and government partners on analysis frameworks, tools, scenarios, and execution of mission analyses