Why pre-screen propulsion engineers before the technical loop
Propulsion punishes the gap between analysis and hardware more than most disciplines. A design can be correct in simulation and destroy itself on a stand because of an injector instability, a thermal path nobody modelled, or a contaminated propellant feed. Engineers who have stood behind a test have seen this, and they design with margin and instrumentation in mind. A short screen asks about a test that went wrong, which simulation-only experience does not produce.
What actually matters when screening Rocketry Propulsion Engineer candidates
- 01
Technical depth
Probe depth in cycle analysis, injector and regen channel design, combustion stability, and tools they name: NASA CEA, RPA, Fluent, Cantera, plus chamber sizing and c-star efficiency math.
- 02
Work that shipped
Ask which engines or stages they took to hot fire: thrust class, propellant combination, test stand, burn duration, and their specific ownership of hardware versus analysis.
- 03
Diagnosis under uncertainty
Test how they chased anomalies: hard starts, chugging, injector burn-through, valve chatter. Look for use of high-speed data, strain and pressure traces, and post-test teardown findings.
- 04
Working across the org
Assess how they worked with structures, avionics, GSE, and test operations on TVC interfaces, propellant loading procedures, and range or FAA safety documentation.
Pre-screening questions to ask Rocketry Propulsion Engineer candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Combustion and thermal
3 questions01Have you designed or developed combustion devices such as thrust chambers or injectors?
Listen forSpecific hardware with the design drivers named, including combustion stability and how it was assessed rather than assumed.
Combustion hardware described at concept level, or no awareness of instability as a design risk.
02What is your experience with thermal analysis and heat transfer in engines?
Listen forCooling approach tied to a real design, with wall temperatures predicted and then compared against measured test data.
Thermal predictions reported with no test correlation, or cooling treated as a downstream detail.
03Do you have experience with cryogenic propellants?
Listen forPractical handling with chill-down, material embrittlement and boil-off addressed, rather than cryogenics discussed in principle.
Cryogenic experience claimed with no handling detail, or no awareness of material behaviour at those temperatures.
Hardware that fired
3 questions04Do you have hands-on experience with engine assembly and testing?
Listen forTime on a stand with their own role stated, including instrumentation they specified and what they wished they had measured.
Testing experience that turns out to be reviewing data afterwards, with no presence during operations.
05Can you explain the propulsion systems or engines you have worked on?
Listen forNamed systems with thrust class and propellant combination, plus what they personally owned within the design.
Programme described in the first person throughout, with no scope of their own identified.
06Can you describe your experience with experimental testing of engines?
Listen forTest campaigns with objectives set in advance, and what a test revealed that the analysis had not predicted.
Tests run to confirm expectations only, or no test whose result contradicted the model.
Anomaly from telemetry
3 questions07Have you handled troubleshooting of engine malfunctions?
Listen forAn anomaly investigation with the telemetry available named, hypotheses ruled out in order, and the confirmed cause.
Anomalies attributed without evidence, or an investigation closed when the symptom stopped recurring.
08Do you have experience performing failure modes and effects analysis?
Listen forAn analysis that changed a design or added instrumentation, rather than a document produced to satisfy a review.
Failure analysis described as a completed form, with no design consequence that followed.
09How do you approach modelling and simulation of engine behaviour?
Listen forModels validated against test data with their limits stated, and a case where the model was confidently wrong.
Simulation output presented as result, or no correlation between predicted and measured performance.
Working with test
3 questions10How familiar are you with propulsion safety standards and range requirements?
Listen forSpecific requirements that changed a design or a procedure, such as separation distances or pressure system rules.
Standards recited with no consequence, or safety treated entirely as the test team's responsibility.
11Do you have experience working within multi-disciplinary engineering teams?
Listen forDirect work with structures, avionics and manufacturing, with a conflict such as mass against margin and how it resolved.
Works within propulsion only, or describes manufacturing as failing to build to the drawing.
12Can you describe your approach to material selection for engine components?
Listen forMaterials chosen for a property under the actual environment, with manufacturability and lead time considered alongside performance.
Materials selected on strength alone, or no consideration of how the part would actually be made.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical depth
35%5Talks fluently about mixture ratio trades, film cooling margins, and acoustic modes, citing real chamber pressures and measured c-star efficiencies.
Work that shipped
30%5Names engines that fired, with thrust, propellants, cumulative test seconds, and a clear boundary of what they personally designed or ran.
Diagnosis under uncertainty
20%5Reconstructs a failure from transducer data and hardware evidence, states the root cause, and describes the design change that closed it.
Working across the org
15%5Describes negotiating real interface conflicts across teams and writing procedures that test operators and safety reviewers actually accepted.
A design can be correct in simulation and destroy itself on the stand. A one-way video screen asks about the test that went wrong.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a propulsion engineer take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish whether their work reached hardware, confirm test stand experience, and hear one anomaly investigation before a technical loop.
What should the screen establish beyond analysis skill?
Whether anything they designed was built and fired. Analysis capability is common and assessable later. Hot fire experience, and what they learned when the data disagreed with the model, is the scarcer and more predictive thing.
Evaluating answers
What is the strongest signal when screening a propulsion engineer?
A test that failed and what they concluded. Engineers with stand time describe the telemetry they had, what they ruled out, and the point their first theory collapsed. Simulation-only candidates describe designs that always performed as predicted.
How do I judge safety answers here?
Ask what a hazard analysis changed. Propellant handling, pressure systems and stand operations carry real consequences, and an engineer who has worked around them can name a design or procedural change that came from an assessment rather than a document.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
