Interview scorecard template

Climate Data Scientist interview scorecard

Pre-screening scorecard for Climate Data Scientist candidates.

See AI scoring
software dataclimate modelingcmip6 era5geospatial mlquantum algorithms
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 proficiency

35% weight

Check fluency with climate datasets and tooling: CMIP6 or ERA5 reanalysis, xarray and Dask on netCDF or Zarr, plus PyTorch and a quantum SDK such as Qiskit or PennyLane.

Evidence to listen for

  • Command of the languages, frameworks, and data tools the role actually uses
  • Understands correctness, performance, and failure modes, not just syntax
  • Has opinions on testing and can justify them
  • Reads and reasons about code they did not write

Five-point scoring guide

1
Poor

Cannot work independently; fundamentals are missing.

2
Needs Improvement

Weak fundamentals; output needs heavy review.

3
Satisfactory

Competent for the role; needs guidance on complex or unfamiliar work.

4
Very Good

Strong practitioner; handles hard problems with little guidance.

5
Excellent

Names specific variables, grids and regridding choices, and describes hybrid quantum-classical or ML models they coded and benchmarked themselves.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe how they handle petabyte-scale gridded data: chunking strategy, cloud object storage costs, downscaling resolution choices, and where quantum annealing or variational circuits genuinely beat classical baselines.

Evidence to listen for

  • Reasons about scale, latency, cost, and failure before writing code
  • Names the trade-off they chose and what they gave up
  • Understands the data lifecycle end to end
  • Anticipates what breaks at ten times the volume

Five-point scoring guide

1
Poor

No thinking beyond the immediate task; no awareness of scale or failure.

2
Needs Improvement

Limited architectural awareness; struggles with design decisions.

3
Satisfactory

Works within an existing design; makes sound local decisions.

4
Very Good

Designs for scale and maintainability; articulates trade-offs clearly.

5
Excellent

Explains trade-offs with numbers on runtime, memory and cost, and admits candidly where quantum methods offered no advantage.

03
Evaluation factor

Evidence and rigour

25% weight

Test validation habits: bias correction, hindcast skill scores (CRPS, RMSE, Brier), ensemble spread, and how they separate internal variability from a forced climate signal.

Evidence to listen for

  • Validates results rather than trusting output
  • Knows how their work is measured and what a bad result looks like
  • Can describe a time their own analysis or model was wrong and how they caught it
  • Careful about data quality, leakage, and silent failure

Five-point scoring guide

1
Poor

Ships unvalidated work; no notion of how correctness is checked.

2
Needs Improvement

Validates superficially; misses obvious quality or leakage issues.

3
Satisfactory

Reasonable checks in place; rigour drops under time pressure.

4
Very Good

Validates thoroughly; can name a real error they caught in their own work.

5
Excellent

Quantifies uncertainty routinely, cites skill metrics against held-out years or stations, and distinguishes correlation from physically plausible mechanism.

04
Evaluation factor

Collaboration and communication

15% weight

Assess work with climate scientists, quantum hardware vendors and non-technical stakeholders: co-authored papers, IPCC or NGFS scenario briefings, notebooks or dashboards others actually used.

Evidence to listen for

  • Explains technical work to non-technical stakeholders
  • Gives and takes code or peer review constructively
  • Documents enough that the work survives their absence
  • Aligns with team process rather than working around it

Five-point scoring guide

1
Poor

Cannot work in a team; resistant to feedback.

2
Needs Improvement

Communication issues create rework; lone-wolf tendencies.

3
Satisfactory

Adequate team member; documentation and review participation are light.

4
Very Good

Communicates well; reliable reviewer and collaborator.

5
Excellent

Points to published or internal outputs used by domain scientists or policy teams, and translates circuit depth or model error into decision language.

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