Interview scorecard template

Digital Preservation Specialist interview scorecard

Pre-screening scorecard for Digital Preservation Specialist candidates.

See AI scoring
software dataarchivematicadigital preservationfixity checksoais
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 hands-on command of OAIS workflows: BagIt packaging, PREMIS and METS metadata, format identification with DROID or Siegfried, and validation via JHOVE or veraPDF.

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 ingest pipelines built in Archivematica, Preservica or custom scripts, and explains PREMIS event capture without prompting.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe storage architecture choices: number of replicas, geographic separation, tape versus object storage, fixity check cadence, and when they chose migration over emulation for at-risk formats.

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

Weighs cost per terabyte, bit-rot risk and access demand together, citing a real decision on obsolete formats like WordPerfect or QuickTime.

03
Evaluation factor

Evidence and rigour

25% weight

Test how they prove content is intact: checksum algorithms used, audit reports run, corruption events detected, and how repository health was evidenced against ISO 16363 or CoreTrustSeal.

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

Cites fixity failure rates, dates of detected corruption, and the restore path taken; treats audit evidence as routine, not aspirational.

04
Evaluation factor

Collaboration and communication

15% weight

Assess work with donors, curators, records managers and IT: negotiating deposit agreements, handling forensic disk images of legacy media, and explaining preservation risk to non-technical stakeholders.

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

Describes translating a floppy or hard drive accession into a preservation plan curators understood and funders approved.

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