SpacecraftSystemsEngineer

The work

Systems engineering is the discipline of the interfaces. Power, thermal, propulsion, comms, attitude control and payload each have specialists; the systems engineer owns the budgets they all draw on, the requirements they all trace to, and the failure modes that only appear where two subsystems meet. Most of the job is asking hard questions early, because there is no maintenance visit afterwards.

A typical day

• 01Hold the mass, power and data budgets, and say no when they are spent
• 02Trace requirements from the mission down to a connector pin
• 03Run failure analyses and decide what has to be redundant
• 04Chair the review where six specialists disagree

How people get in

• From a subsystem

  The usual route. Spend a few years deep in power or thermal, then move outward.

• Systems engineering masters

  A direct route, and stronger when it follows some hands-on experience.

How it unfolds

1. DegreeAerospace, electrical or systems engineering, usually with a masters somewhere.
2. Years 1-4Deep in one subsystem — power, thermal, comms — because you cannot own interfaces you have never built.
3. Years 5-9Systems: the budgets, the requirements, the failure analyses, and chairing the argument.
4. LaterChief engineer or mission architect.

Is there a job in it

The hard parts

You are responsible for everything and expert in nothing, which is uncomfortable for a long time. There is no maintenance visit after launch, so a question you did not ask early becomes a mission you cannot fix. Reviews are where careful work meets six specialists who all want something different.

What you would need

• Requirements and interface management
• Failure mode analysis
• Enough of every subsystem to ask the right question
• Written precision