Evaluate Satellite 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 depth on spacecraft subsystems: ADCS actuator sizing, power budgets across eclipse, RF link budgets in S-band or X-band, and radiation-tolerant part selection. Use the rubric to compare role-specific evidence consistently.
For technical depth, look for evidence the candidate quotes real margins and numbers, explains subsystem coupling (power to thermal to duty cycle), and names standards such as ECSS or MIL-STD-1540. For work that shipped, look for evidence the candidate names flown or delivered spacecraft, their specific ownership, and on-orbit performance versus predicted budgets, including anomalies they later resolved.
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 depth on spacecraft subsystems: ADCS actuator sizing, power budgets across eclipse, RF link budgets in S-band or X-band, and radiation-tolerant part selection for LEO or GEO.
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 margins and numbers, explains subsystem coupling (power to thermal to duty cycle), and names standards such as ECSS or MIL-STD-1540.
02
Evaluation factor
Work that shipped
30% weight
Ask which missions they took through PDR, CDR, and launch: bus type, payload, orbit, their owned subsystem, and whether it operated on orbit as designed.
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 flown or delivered spacecraft, their specific ownership, and on-orbit performance versus predicted budgets, including anomalies they later resolved.
03
Evaluation factor
Diagnosis under uncertainty
20% weight
Test anomaly work: unexpected telemetry trends, thermal vacuum test failures, unexplained torque disturbances, or downlink degradation, and how they isolated cause with limited data.
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
Reconstructs faults from sparse telemetry, builds testable hypotheses on the flatsat or FlatSat twin, and states what they ruled out and why.
04
Evaluation factor
Working across the org
15% weight
Look for interface work with payload, propulsion, ground segment, and launch provider: managing ICDs, mass and power budget negotiations, and supplier reviews under schedule pressure.
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
Owns ICDs and budget allocations across teams, escalates margin erosion early, and cites decisions where they traded subsystem preference for mission success.
Evidence-led prompts
Interview questions for a Satellite Systems Engineer
Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.
01
Have you designed a satellite communication system? What was your role?
02
What types of satellite technology have you worked with?
03
Do you have experience with low-earth orbit constellations or similar modern platforms?
04
Can you discuss your experience with payload design for satellites?
05
Do you have experience with satellite signal processing?
