Walk me through your engineering background + programme experience.

What it tests: Story arc - engineering training, systems engineering exposure, safety-critical work, programme dynamics.

Tell me about a programme or system you've worked on.

What it tests: Programme + SE thinking - requirements + integration + V&V + outcome.

What it tests: Authentic alignment - mission, complexity, programme scale, decade-thinking.

What it tests: Specificity. Generic answers fail.

What it tests: Real homework - programme, capability, culture - not name-drop.

What it tests: Industry literacy - programme stage, competitive picture, recent events.

What it tests: Engineering org maturity - SE function authority, AS9100, EVM, IPT structure.

What it tests: SE V-model fluency - requirements + ICDs + traceability + integration + V&V.

Systems + integration + V&V engineers at primes + tier-1 suppliers + space (traditional + new space).

Can the candidate apply systems engineering V-model discipline - requirements + decomposition + ICDs + integration + V&V?
Do they understand safety-of-flight / safety-critical engineering - DO-178C, DO-254, MIL-STD-882, hazard analysis?
Are they fluent in DoD acquisition + EVM + IPT structure + DCMA oversight (if defense)?
Can they execute configuration management + change control in long-life programmes (decades)?
Do they navigate cross-domain integration - electronics / mechanical / software / control / mission?
Are they comfortable with ITAR / export + security clearances + the constraints they impose?
Long-game fit - tech lead / chief systems engineer / programme tech authority trajectory?

Walk me through your engineering background + programme experience.
What it tests: Story arc - engineering training, systems engineering exposure, safety-critical work, programme dynamics.
Tell me about a programme or system you've worked on.
What it tests: Programme + SE thinking - requirements + integration + V&V + outcome.
Why aerospace + defense vs other engineering paths?
What it tests: Authentic alignment - mission, complexity, programme scale, decade-thinking.
Why this domain - aviation / space / missiles / sensors?
What it tests: Specificity. Generic answers fail.
Why this firm?
What it tests: Real homework - programme, capability, culture - not name-drop.
What's your read on our programme portfolio?
What it tests: Industry literacy - programme stage, competitive picture, recent events.
Tell me what you understand about our engineering culture + SE practice.
What it tests: Engineering org maturity - SE function authority, AS9100, EVM, IPT structure.
Walk me through a requirements + integration case.
What it tests: SE V-model fluency - requirements + ICDs + traceability + integration + V&V.

Systems engineering discipline

Requirements + traceability: Documented system requirements traceable from stakeholder need through V&V test - bi-directional traceability matrix.
Interface Control Documents (ICDs): Defines interfaces between system + external systems + subsystems - mechanical, electrical, data, environmental.
Verification vs Validation: Verification = did we build it right (vs requirements). Validation = did we build the right thing (vs need).
Technology + Manufacturing Readiness Levels (TRL / MRL): DoD + civil space agency scales of technology + manufacturing maturity (1-9).

Safety-of-flight + airworthiness

Airworthiness authority: FAA for civil; military airworthiness boards for DoD (each service has its own technical authority).
DO-178C software DAL: Design Assurance Level A (catastrophic) -> E (no effect); higher levels require more rigor + documentation.
MIL-STD-882 hazard analysis: DoD standard system safety process - PHA + SHA + SSHA + OSHA + Health Hazard Assessment.
Failure mode analysis (FMEA / FTA / FMECA): FMEA + FMECA = bottom-up failure mode analysis. FTA = top-down deductive analysis.

DoD acquisition + EVM

DoD acquisition phases: Materiel Solution Analysis -> Technology Maturation + Risk Reduction -> Engineering + Manufacturing Development -> Production + Deployment -> Operations + Support.
IPT (Integrated Product Team): Cross-functional team owning a product area - engineering + manufacturing + logistics + contracts + customer.
DCMA + DCAA oversight: DCMA = Defense Contract Management Agency (programme oversight + EVM). DCAA = Defense Contract Audit Agency (cost + accounting audit).
KPP + KSA + Threshold + Objective: Key Performance Parameter + Key System Attribute = critical capabilities; Threshold = minimum acceptable, Objective = desired.

Configuration + change management

Configuration baseline: Functional + Allocated + Product baselines - the controlled configuration at programme milestones.
ECN + ECP: Engineering Change Notice / Proposal - the controlled process to modify a baseline.
FRACAS (Failure Reporting + Analysis + Corrective Action): Closed-loop process for capturing field + test failures + driving root-cause + corrective action.
Obsolescence + DMSMS: Diminishing Manufacturing Sources + Material Shortages - planning for component obsolescence in long-life systems.

You're SE lead for a new subsystem on a fielded aircraft. Walk through your requirements + integration + V&V approach.
Late in development, integration testing reveals a previously unanalysed hazard - a single-point failure could cause loss of flight control authority. Walk through your safety response.
Your programme is 6 months behind schedule. EVM SPI is 0.82, CPI 0.91. PMO + customer ask for recovery plan. Walk through your approach.

Programme portfolio + phase - commercial / military / space mix, LRIP / FRP / sustainment
Engineering org + SE authority - functional vs IPT, chief engineer model
Safety + airworthiness posture - FAA / EASA / military airworthiness authority engagement
Configuration + quality systems - AS9100, EVM-certified, DCMA / FAA audit history
ITAR + clearance level - programme classification + access expectations

Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.