Senior Engineer Mission Software & Operational Workflows, meoSphere

(Senior) Engineer Mission Software & Operational Workflows, meo Sphere

Requisition Number: 20103

Contract Type:
Permanent

Location(s):
Betzdorf, LU

Senior Engineer Mission Software & Operational Workflows, meo Sphere

The job responsibilities outlined in this document are not exhaustive and may evolve over time and be reviewed according to business needs.

SES is seeking a Mission Software & Operational Workflows Senior Engineer to define the mission-level software behavior, operational workflows, and user-facing architecture for mission and payload control systems supporting Pathfinder optical communications missions and the future meo Sphere constellation.

This role focuses on how mission operations are realized in software
—translating mission needs into workflows, automation logic, state behavior, and operator interactions
. The architect defines how operators, automation systems, and mission services interact to plan, execute, and monitor missions across spacecraft, payload, and ground systems.

The role does not replace or duplicate systems engineering
, but instead works alongside it—taking mission concepts and constraints and translating them into software‑operational design that can be implemented by GSMS and SCoE development teams.

The incumbent partners closely with the Software Systems & Implementation Architect to ensure mission workflows are implemented as scalable, automation‑ready services, using a prototype‑first and AI‑assisted development approach to validate concepts early.

• Translate mission CONOPS and stakeholder needs into software workflows, services, and operator interactions
• Define how mission planning, execution, monitoring, and analysis are implemented in GSMS software
• Define mission modes, states, and transitions as implemented in software systems
• Ensure mission concepts are expressed in a way that is directly implementable by development teams

• Mission planning and scheduling
• Command generation and execution
• Telemetry monitoring and analysis
• Anomaly detection and response
• Design human-in-the-loop vs automation boundaries within mission software
• Ensure workflows reflect real operational constraints (e.g., asynchronous TT&C, limited contact windows)
• Drive consistency and usability across GSMS user interfaces and operational tools

• Define how payload operations are executed and automated within mission software
• Develop workflows for optical communications (OGS passes, calibration, link setup, space‑to‑space links)
• Define software‑driven coordination between payload, spacecraft interfaces, and ground systems
• Ensure payload operations are expressed as repeatable, automatable software procedures and services

• Define mission‑level data flows, control flows, and state representations within GSMS
• Contribute to the design of the digital twin / state model from an operational software perspective
• Define how commands, telemetry, and derived state are used to drive mission workflows
• Ensure traceability between mission intent, software behavior, and telemetry verification

• Use AI‑assisted (“agentic”) development tools to rapidly prototype mission workflows and operational logic
• Translate mission scenarios, ICDs, and procedures into executable software prototypes
• Validate workflows through simulation, digital twin interaction, and early integration testing
• Promote a “code as requirements” approach
  , where working implementations validate operational design

• Serve as the primary interface between mission stakeholders and GSMS software teams
• Align mission workflows with payload teams, integration partners, and operations teams
• Ensure mission requirements are clearly defined in software terms (APIs, workflows, behaviours)
• Support integration planning and readiness from a mission software perspective
• Define software approaches for multi‑satellite mission coordination and fleet‑level operations
• Contribute to…