Spacecraft Production-Readiness Architecture Director — Satellite Systems

The mandate

Engineering has flown successful prototypes, but each spacecraft still depends on late design interpretation, engineer-owned rework and manually reconciled test evidence. Supplier changes arrive after kits are staged, software baselines move during environmental test and launch slots mask unfinished configuration. The company needs a production system that respects mission assurance while moving from singular builds to a controlled constellation cadence.

The deliverable is a Spacecraft Production-Readiness Architecture covering configuration maturity, build release, supplier gates, shortage substitution, non-conformance, software-hardware alignment, test evidence, launch handoff, capacity and escalation. It will define what must be repeatable, which mission differences remain engineered and how deviations enter a controlled technical decision rather than the factory’s informal recovery queue.

Milestone one at week five accepts three-build genealogy and loss analysis; week ten closes product-and-process maturity. Supplier and configuration gates land at week sixteen, the integrated control model at week twenty-one and two site plans at week twenty-seven. Four build simulations conclude by week thirty-six; the accepted architecture and implementation backlog close at week forty.

Acceptance requires client teams to release, build, test and hand off a blinded spacecraft scenario containing late component change, software mismatch, failed environmental test and launch-date movement. The COO and Chief Engineer sign only when technical authority remains intact, every configuration is reconstructable, escape and rework risks are visible, and schedule recovery does not rely on consultant judgement.

The client supplies designs, bills of material, configuration histories, test records, non-conformance data, supplier commitments, launch assumptions, capacity, cost and empowered engineering-and-production owners. Excluded services include spacecraft design, airworthiness or launch certification, supplier selection, software development, live build command, quality release, programme guarantee, facility engineering and implementation of planning or configuration systems.

Why this is external work

Prototype heroes are also accountable for current missions and cannot neutrally decide which interventions should disappear at scale. An external industrialisation leader can connect production evidence with engineering intent, expose hidden dependence and facilitate hard maturity choices without becoming chief engineer, mission assurer or programme operator.

What you will own

• Reconstruct three spacecraft builds across design maturity, configuration change, shortages, rework, test failure and launch consequence.
• Define release evidence for hardware, software, work instructions, tooling, suppliers, test assets and trained labour.
• Separate repeatable production decisions from legitimate mission-specific engineering decisions and authority.
• Design supplier-change, substitution, non-conformance and configuration controls with explicit clocks and technical owners.
• Build capacity and cadence models that include environmental test, specialist review, rework and launch-interface constraints.
• Rehearse late component, software mismatch, failed test, configuration escape and launch movement.
• Deliver the architecture, maturity matrix, control model, site roadmaps, simulation evidence and funded backlog.

Candidate qualifications

• Industrialised spacecraft, avionics or similarly configuration-intensive aerospace products beyond prototype production at repeatable cadence.
• Joined engineering authority, configuration management, factory execution, software baseline and test evidence coherently.
• Designed maturity and release gates that exposed production risk without converting technical review into bureaucracy.
• Managed constrained suppliers, substitutions and non-conformance while preserving full unit-level product genealogy.
• Understood environmental testing, mission assurance and launch interfaces without claiming certification authority.
• Transferred production architecture through a client-led blinded build containing multiple interacting technical and supplier failures.

Non-negotiables

• Can lead ten laboratories and four Los Angeles-governed simulations within ten months.
• Direct aerospace industrialisation beyond prototype is required; generic factory scaling is insufficient.
• Will disclose launch providers, satellite firms, defence clients, component suppliers and investors.
• Will not design spacecraft, release product, certify missions, select suppliers or command live builds.

1. 49 words maximum. Describe a prototype intervention that had to be eliminated before repeatable aerospace production.
2. 49 words maximum. How would you prove hardware and software configuration remained aligned through failed testing?
3. 49 words maximum. Which three build histories are essential before defining maturity gates?