Why pre-screen astronomers before the research interview
Author lists in this field can run to hundreds of names, and a publication record tells you very little about what someone did. The other issue is statistical: much of the interesting work sits near the detection threshold, where analysis choices decide whether a signal is real. Astronomers worth hiring are candid about a result that weakened under scrutiny. A short screen asks for their own contribution and for a detection that did not hold.
What actually matters when screening Astronomer candidates
- 01
Theoretical command
Check command of the subfield they claim: stellar populations, exoplanet transits, radio interferometry, cosmological parameters. Ask which models or codes underpin their conclusions and where those break down.
- 02
From theory to hardware or code
Probe actual reduction and analysis work: CASA, IRAF, astropy, DrizzlePac, MCMC fitting, pipeline code on GitHub, instrument commissioning or detector characterisation they did hands-on.
- 03
Research judgement
Assess how they choose targets and defend time: successful HST, JWST, ALMA, VLT or NRAO proposals, survey strategy trade-offs, when they abandoned a null result.
- 04
Explaining it to non-specialists
Look for evidence of translating results outward: press releases, planetarium or public talks, undergraduate supervision, briefing funders or observatory directors without collapsing into jargon.
Pre-screening questions to ask Astronomer 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.
Their own contribution
3 questions01Can you describe your experience with observational and theoretical astrophysics?
Listen forA clear specialism with an honest statement of where they rely on collaborators.
Breadth claimed across both with depth in neither, or subfields listed with no work behind them.
02Have you led or contributed to research projects? Please provide details.
Listen forTheir specific role stated, distinguishing analysis they performed from work by the wider collaboration.
Collaboration achievements presented as personal, or no project where they can name their own contribution.
03Have you written or contributed to research papers? Please share the details.
Listen forFirst-author work distinguished from collaboration papers, with what they wrote and analysed on each.
Publication counts quoted with no role described, or membership author lists presented as authorship.
Instruments and limits
3 questions04Have you worked with telescopes? Which ones, and what was your role?
Listen forProposals written and observations taken, with what the instrument could not do for their science.
Archival data only where the role needs observing, or instruments named with no hands-on time.
05Do you have experience with overnight or extended observation sessions?
Listen forRealistic account of observing runs including weather losses and decisions made about scarce time.
No observing experience where the role requires it, or no awareness of how much time is lost.
06Explain your experience designing and conducting observations or models.
Listen forObservations designed around a specific question with the required sensitivity worked out in advance.
Data collected and then searched for a result, or no consideration of what sensitivity the question needs.
Statistics on marginal data
4 questions07How do you handle and analyse astronomical data?
Listen forSystematic effects handled explicitly in the analysis, including calibration and instrumental artefacts alongside statistical noise.
Only statistical uncertainty discussed, or pipeline output analysed without checking calibration.
08Do you have experience with spectroscopic data analysis?
Listen forReduction steps understood with the effect of each on the final measurement, not just running a pipeline.
Reduced spectra used with no understanding of the reduction, or line measurements with no uncertainty.
09Can you elaborate on your experience with statistics and data modelling?
Listen forCareful handling of marginal detections, including trials factors and a result they declined to claim.
Significance quoted without accounting for how many things were tested, or no result they have withdrawn.
10Are you familiar with the programming languages used in astronomy?
Listen forAnalysis code they wrote themselves, versioned and reproducible rather than run interactively once.
Analysis performed in undocumented sessions, or code that cannot regenerate a published figure.
Explaining the result
2 questions11Do you have experience giving educational talks or presentations about astronomy?
Listen forPublic talks given with uncertainty conveyed honestly rather than simplified into confident claims.
Outreach that overstates certainty, or no experience explaining work outside the field.
12Have you taught astronomy courses? If so, describe your experience.
Listen forTeaching with a sense of where students consistently struggle, and what they changed as a result.
Teaching described only as material delivered, or no reflection on what students found hard.
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.
Theoretical command
35%5Names specific formalisms and their limits, distinguishes model assumptions from observed quantities, cites papers that changed their own thinking.
From theory to hardware or code
30%5Walks through a pipeline they built or debugged, from raw frames to calibrated photometry, with version-controlled code others reuse.
Research judgement
20%5Shows awarded telescope time with a clear science case, and explains a project they killed once the signal-to-noise made it unwinnable.
Explaining it to non-specialists
15%5Explains a result such as a redshift measurement or transit depth in plain terms while keeping the uncertainty honest.
Author lists run to hundreds of names and say nothing about who did the analysis. A one-way video screen asks what was actually theirs.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for an astronomer take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish their own contribution to published work, test their data and statistical practice, and hear their observing experience.
How should I read a long publication list?
As evidence of collaboration membership rather than contribution. Ask specifically what they did on two papers: which analysis was theirs, what they wrote, and whether they led anything.
Evaluating answers
What is the strongest signal when screening an astronomer?
A result that did not survive further analysis. Careful researchers have one, and describe how it was tested and abandoned. Anyone whose detections all held up has either been lucky or has not looked hard.
How do I judge their data practice?
Ask what systematic effects they had to handle. Real answers name calibration, instrumental artefacts or selection effects. Anyone who describes only statistical uncertainty has not worked with real observations.
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
