Engineer training programmes
Sovereign space capacity depends on engineers who can make decisions, not just operate systems. This page covers the curriculum, timelines and embedded-placement models that turn graduate cohorts into spacecraft engineers.
The gap between a degree and a spacecraft decision
Most countries that commission their first national satellite already have aerospace graduates. The problem is that a degree in aeronautical engineering, or even in electronics, does not prepare someone to make a system-level trade between propellant mass and mission lifetime, or to sign off an AIT non-conformance report at three in the morning before a launch window. That judgement comes from supervised practice on real hardware under real schedule pressure.
Engineer training programmes exist to close that gap deliberately, rather than hoping it closes on its own after a decade of watching foreign contractors do the interesting work. The distinction matters: a government that procures a satellite without embedding its own engineers in the build learns almost nothing transferable. One that structures the contract around capacity-building gets a programme and a workforce.
What the curriculum actually covers, and in what order
A well-structured programme runs in three broad phases. The first, typically six to twelve months, is systems engineering fundamentals: requirements decomposition, interface control documents, mass and power budgets, FMEA, and the discipline of writing a requirement that can actually be verified. This phase is classroom-heavy but should be anchored to the specific mission architecture from day one, not to generic textbook examples.
The second phase is subsystem depth. Trainees are assigned to specific subsystems during the build: attitude determination and control, power electronics, communications, structure and thermal, or software depending on the cohort's background and the programme's staffing gaps. This is where embedded placement with the prime contractor or integration partner becomes indispensable. Watching an experienced engineer debug an ADCS anomaly in a thermal-vacuum chamber is worth roughly a semester of lectures on the same topic.
The third phase covers AIT: assembly, integration and test. Trainees participate in functional testing, environmental test campaigns (vibration, thermal-vacuum, EMC), and the formal review sequence from PDR through CDR to launch readiness. By the end, a trainee who has completed all three phases can read and contribute to a test procedure, interpret a data sheet against a requirement, and escalate a genuine anomaly rather than explain it away. That is the minimum viable spacecraft engineer.
Realistic timelines: what five years can and cannot produce
A graduate with a relevant engineering degree, embedded full-time in a build programme, can reach competent subsystem engineer level in roughly two to three years. Lead engineer on a subsystem takes four to six years of continuous practice. Programme-level systems engineering authority, the person who can arbitrate a trade between two subsystems and be right, typically takes eight to twelve years and usually requires having lived through at least one anomaly investigation.
These numbers are not pessimistic; they reflect what the European Space Agency's Young Graduate Trainee scheme, NASA's co-op programme, and JAXA's documented graduate pathways all show in practice. A government that expects to hand a satellite programme to a fully indigenous team within three years of starting from scratch will be disappointed. One that plans for a ten-year capacity arc, with foreign expertise stepping back progressively rather than all at once, can genuinely get there.
The implication for programme structure is that the first national satellite is not just a satellite. It is the training environment for the engineers who will design the second one without external help.
Where this model fails, and why it sometimes fails quietly
The most common failure mode is not technical. It is contractual. If the prime contractor is not explicitly required to embed trainees in meaningful roles, they will not. The commercial incentive runs the other way: a foreign engineer who already knows the answer is faster than one who is learning it. Training has to be written into the statement of work with specific deliverables, not left to goodwill.
The second failure mode is retention. A government that invests three years in training a spacecraft engineer and then pays them a civil-service salary that is a fraction of what a commercial operator would offer will lose them. This is not a space problem; it is a public-sector compensation problem that space programmes inherit. Structured career pathways, security of tenure, and the genuine prestige of working on a national programme can partially offset salary gaps, but only partially.
A third risk is curriculum drift. Programmes that train engineers on a specific satellite bus and then retire that bus leave those engineers with skills that do not transfer cleanly to the next generation of hardware. The curriculum should weight transferable methods (systems engineering process, test philosophy, anomaly investigation) more heavily than platform-specific procedures.
Structuring the placement to protect what is being built
Embedded placements raise an obvious tension: trainees need access to design details to learn, but those details may be export-controlled or commercially sensitive. This has to be resolved before the programme starts, not during it. The placement agreement should specify which documentation trainees can access, which they can copy, and under what conditions they can discuss what they have learned with third parties. Getting this wrong does not just create legal exposure; it can cause a foreign government or partner to withdraw cooperation mid-programme.
The most effective model Satellize has used is a tiered access structure agreed at contract signature, with audit rights held by the client government. Trainees get full access to the subsystems they are assigned to, read access to adjacent subsystem ICDs, and a defined escalation path when they need to understand something outside their tier. This keeps learning broad enough to develop systems thinking while keeping sensitive IP boundaries visible to everyone.
Engineering parameters
| Minimum cohort size (effective) | 4 to 6 engineers per programme; smaller cohorts lack peer review and succession depth |
| Graduate-to-subsystem-engineer timeline | 2 to 3 years full-time embedded; longer if placement is part-time or interrupted |
| Graduate-to-lead-engineer timeline | 4 to 6 years; requires at least one full mission cycle including anomaly resolution |
| Curriculum phases | 3: systems engineering fundamentals, subsystem depth (embedded), AIT and formal reviews |
| Recommended classroom-to-practical ratio | Roughly 30:70 by hours after the first six months; earlier phases are more classroom-heavy |
| Export control pre-clearance lead time | 3 to 9 months depending on jurisdiction and hardware classification; must precede placement start |
| Transferable skills vs platform-specific skills (target weighting) | At least 60% transferable (SE process, test philosophy, FMEA) to preserve value across bus generations |
| Formal review milestones trainees should witness | Minimum: PDR, CDR, test readiness review, launch readiness review; delta-CDR where applicable |
One contract, one accountable engineer
Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Review our training scope with your team.