Why pre-screen digital librarians before the panel interview
This role sits between library practice and systems administration, and candidates arrive weighted heavily to one side. Resumes list the same platforms and the same standards either way. A short screen surfaces which half they are strong in, and it surfaces the work that quietly decides whether a collection survives: preservation formats, checksums, and whether anyone can still open the files in ten years.
What actually matters when screening Digital Librarian candidates
- 01
Execution and reliability
Check the collections and systems they have managed, plus metadata standards, cataloguing, and digital preservation practice.
- 02
Improving the process
Test whether they improved discovery: taxonomy work, migration, or retrieval that measurably got better.
- 03
Judgement and autonomy
Assess how they handle access, copyright, and licensing questions where the correct answer is unclear.
- 04
Communication
Judge how they help researchers who cannot find something and do not know how to describe what they want.
Pre-screening questions to ask Digital Librarian 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.
Daily practice
3 questions01What experience do you have with electronic resource management systems?
Listen forNamed systems they worked in daily, the size of the collection, and what they personally owned: ingest, licensing records, access troubleshooting or renewals.
Names systems they have only seen demonstrated, or cannot say how large a collection they actually handled.
02Can you describe your familiarity with metadata standards, and which you have applied?
Listen forStandards tied to collections: Dublin Core, MODS, METS or MARC, with a reason for the choice and an example of a crosswalk that lost something.
Recites standard names as definitions, with no example of applying one to a real collection.
03How do you approach the task of digitising various forms of media?
Listen forCapture settings tied to the material, a stated master and access copy strategy, and awareness of what a rushed scan costs when the original is fragile.
One workflow applied to everything, or no distinction between a preservation master and a delivery copy.
Keeping it intact
3 questions04How do you manage digital preservation efforts?
Listen forFixity checks on a schedule, format migration planning, geographically separate copies, and a specific instance where a check caught a corrupted file.
Describes preservation as backups on a server, with no fixity checking and no format obsolescence plan.
05Describe your experience with digital content licensing and copyright issues.
Listen forJudgement calls they made themselves: orphan works, embargoes, rights statements applied to a collection, and where they drew the line before escalating to counsel.
Escalates every rights question, or has published material without checking what the licence actually permitted.
06How do you handle technical issues that arise with digital resources?
Listen forA diagnosis path they own before escalating: reproducing the problem, checking logs or proxy configuration, and a concrete access failure they resolved themselves.
Forwards every problem to IT, or cannot describe a single issue they diagnosed without help.
Access and discovery
3 questions07What strategies do you use to enhance the discoverability of digital resources?
Listen forConcrete work: controlled vocabularies, harvesting endpoints, discovery layer configuration, and evidence from search logs about what users failed to find.
Assumes uploading to the repository makes material findable, or has never looked at how users actually search the collection.
08Can you describe a project where you improved access to digital collections?
Listen forA before and after with a measure attached: usage figures, request volume, or time to fulfil a research request, plus what they traded to get it.
Describes a project with no measure of whether access improved, or credit for work someone else led.
09What methods do you use to evaluate the usability of digital collections?
Listen forReal evaluation with users: task-based testing, reference desk observations, or accessibility checks against a standard rather than assumptions about researchers.
Evaluates usability by personal judgement, or treats accessibility as something the vendor interface handles.
Working with others
3 questions10Do you have experience collaborating with IT departments on digital library projects?
Listen forA specific project with the boundary named: who owned servers, who owned metadata, and a disagreement about scope or security they worked through.
Describes IT as unresponsive with no account of their own part, or has never worked on a joint project.
11What is your approach to managing and implementing digital cataloguing projects?
Listen forPlanning with a stated throughput, quality checks on a sample rather than everything, and how they handled backlog when the schedule slipped.
No plan beyond working through the backlog, or quality control that consists of checking their own records.
12How do you handle the integration of new technologies into a digital library system?
Listen forA staged approach: pilot on a subset, migration path for existing records, and a decision they made to reject a tool that did not fit.
Adopts new tools because they are current, with no migration plan for the records already in the system.
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.
Execution and reliability
35%5Has managed real collections to recognised metadata and preservation standards, in systems you would recognise.
Improving the process
25%5Has run a migration or taxonomy change that measurably improved retrieval, not just tidied records.
Judgement and autonomy
25%5Handles copyright and access ambiguity with a documented, defensible position and knows when to escalate.
Communication
15%5Draws out what a researcher actually needs and teaches them to search, rather than just retrieving one item.
Library-side and systems-side candidates describe this role identically on paper. A one-way video screen lets you hear where a candidate is actually strong before you assemble a panel across two departments.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a digital librarian take?
Ten to fifteen minutes across eight to ten questions, answered async. Enough to place them on the library-practice to systems spectrum and confirm hands-on repository work before a panel of librarians and IT staff spends an hour on it.
Should the screen test metadata knowledge directly?
Ask which standards they have applied and to what, rather than asking for definitions. Naming Dublin Core is easy. Explaining why a collection needed MODS instead, or where a crosswalk lost information, is the part that shows practice.
Evaluating answers
What is the strongest signal when screening a digital librarian?
A specific preservation problem: an obsolete format, a failed checksum, a migration that lost metadata. Practitioners have all lived through one and can describe what they recovered. Candidates without repository experience describe preservation as backups.
How do I weigh library qualifications against technical skill?
Decide first which gap your team can cover. If you have systems support, weight cataloguing judgement and licensing. If you do not, weight the questions on technical issues and integration, because that person will be alone with the repository.
























