Interview scorecard template

Spacecraft Systems Engineer interview scorecard

Evaluate Spacecraft Systems Engineer candidates across 4 weighted areas: technical depth, work that shipped, diagnosis under uncertainty, and working across the org. Technical depth leads at 35%, so probe command of subsystem budgets: mass, power, link margin, delta-v, thermal. Ask which standards they worked to (ECSS, GEVS, MIL-STD-1540) and how they sized. Use the rubric to compare role-specific evidence consistently.

See AI scoring
engineering applied scienceadcsrequirements budgetsspacecraft systemsthermal vacuum testing
TL;DR
For technical depth, look for evidence the candidate quotes real budget numbers and margin policy, explains coupling between power, thermal and duty cycle without hand-waving. For work that shipped, look for evidence the candidate names specific missions and orbits, describes artefacts they authored, and states what worked or failed on orbit. Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Technical depth

35% weight

Probe command of subsystem budgets: mass, power, link margin, delta-v, thermal. Ask which standards they worked to (ECSS, GEVS, MIL-STD-1540) and how they sized ADCS or EPS margins.

Evidence to listen for

  • Explains the physics or mechanism behind their work, not just the tooling
  • Names the standards, tolerances, and constraints they designed against
  • Can defend a design decision under follow-up questions
  • Distinguishes what they personally engineered from what the team delivered

Five-point scoring guide

1
Poor

Cannot explain the fundamentals of their own stated specialism.

2
Needs Improvement

Knows the vocabulary but not the underlying mechanism; struggles under follow-ups.

3
Satisfactory

Solid working knowledge for the role; depth thins out on edge cases.

4
Very Good

Strong command of the domain; explains trade-offs and defends decisions well.

5
Excellent

Quotes real budget numbers and margin policy, explains coupling between power, thermal and duty cycle without hand-waving.

02
Evaluation factor

Work that shipped

30% weight

Ask which spacecraft or payloads flew, their role from PDR through CDR to launch, and what they personally owned: ICDs, requirement trees, TVAC or vibration campaigns.

Evidence to listen for

  • Names specific programmes, parts, or systems that reached production or field use
  • States their own scope inside the project
  • Can give measured outcomes: yield, cycle time, cost, failure rate
  • Explains what went wrong and what they changed

Five-point scoring guide

1
Poor

No delivered work; experience is coursework, lab-only, or purely observational.

2
Needs Improvement

Contributed to projects but cannot say what shipped or what their part was.

3
Satisfactory

Has delivered real work; outcomes described without numbers.

4
Very Good

Names shipped work and their scope, with some measured results.

5
Excellent

Names specific missions and orbits, describes artefacts they authored, and states what worked or failed on orbit.

03
Evaluation factor

Diagnosis under uncertainty

20% weight

Test anomaly work: an unexplained telemetry trend, a failed hot soak, a reaction wheel or battery anomaly. Look for fault trees, testbed reproduction, and FMECA reasoning.

Evidence to listen for

  • Describes a real failure they chased to root cause
  • Shows a method: isolate variables, reproduce, measure, eliminate
  • Distinguishes correlation from cause
  • Says what they ruled out and why, not only what the answer turned out to be

Five-point scoring guide

1
Poor

No diagnostic method; guesses or escalates immediately.

2
Needs Improvement

Trial and error with no structure; cannot explain how they narrowed the cause.

3
Satisfactory

Reasonable method on familiar problems; less structured on novel ones.

4
Very Good

Clear systematic approach with a real root-cause story.

5
Excellent

Walks a real anomaly from telemetry symptom to root cause, showing hypotheses ruled out and corrective action verified.

04
Evaluation factor

Working across the org

15% weight

Check how they arbitrated between propulsion, avionics, software and ground segment teams, ran interface reviews, and negotiated requirement waivers with customers or launch providers.

Evidence to listen for

  • Explains technical constraints to non-technical stakeholders without condescension
  • Has negotiated scope, cost, or timeline with manufacturing, product, or suppliers
  • Documents decisions so others can act on them
  • Takes review feedback without defensiveness

Five-point scoring guide

1
Poor

Cannot communicate outside their specialism; dismissive of other functions.

2
Needs Improvement

Communication gaps cause rework; avoids stakeholder contact.

3
Satisfactory

Works adequately with other teams; documentation is thin.

4
Very Good

Communicates clearly across functions; reliable collaborator.

5
Excellent

Describes concrete interface disputes resolved with data, and shows credibility with both subsystem specialists and programme management.

Evidence-led prompts

Interview questions for a Spacecraft Systems Engineer

Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.

  1. 01

    Can you describe your experience with spacecraft subsystem design and integration?

  2. 02

    Describe your involvement in the launch and commissioning phases of a mission.

  3. 03

    Describe a challenging problem you faced in a previous programme and how you resolved it.

  4. 04

    How do you manage trade-offs between power, mass and performance?

  5. 05

    What methods do you use for spacecraft thermal control and management?

See the complete Spacecraft Systems Engineer question set
Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards