Space Systems Engineer (Regular) – Mission Concepts

Quick Facts

Systems Engineer focused on mission concepts and feasibility studies for space projects.

Description

Lead systems engineering efforts that convert customer needs into successful space missions, including early lifecycle steps during proposal phases. Perform mission concept trade-off analyses (e.g., orbital/rendezvous trade-offs, delta-V, coverage/revisit, link budget, power budget, payload sizing), translate customer needs into system-level requirements with iterative refinement, and prepare technical documentation aligned to ECSS. Support partner/supplier consortia and communicate technical and commercial proposals to both technical and non-technical audiences.

Responsibilities

• Lead systems engineering efforts in space projects focusing on early steps of the system lifecycle, including proposal phase activities.
• Perform mission concept trade-off analyses: orbital/rendezvous trade-offs, delta-V, coverage/revisit, link budget, power budget, payload sizing.
• Identify and name customer needs and transform them into requirements.
• Translate customer requirements into system-level requirements; iterate with customers to refine needs.
• Prepare and oversee technical documentation.
• Support building consortia of partners/suppliers to deliver missions based on identified mission concepts.
• Present and communicate technical and commercial proposals to both technical and non-technical audiences.

Requirements

• Background in systems engineering, aerospace engineering, electrical/mechanical engineering, or related disciplines.
• At least 3 years of relevant space-industry experience.
• Experience contributing to proposals, technical management, or customer engagement.
• Fundamental technical understanding: electronics, mechanics, thermal control, software (including FPGA), orbital mechanics.
• Basic mission-analysis familiarity: coverage, link budgets, orbital constraints.
• Strong understanding of requirements management, interface control, architectural modeling, and V-model development.
• Hands-on experience defining and managing requirements using DOORS-like requirements management tools.
• Experience creating technical documentation according to ECSS.
• Troubleshooting and problem-solving skills.
• Ability to work effectively under pressure.
• Very good English speaking and writing.
• Strong communication skills bridging technical and non-technical domains.

Benefits

Not specified in the provided text.