Digital Archive Preservation Engineer Interview Questions
Practise answering 5 interview questions for Digital Archive Preservation Engineer roles. Covers explaining format re-migration flags, single-node checksum-disagreement root-cause analysis, bit-level preservation vs. format migration trade-offs, and re-digitization judgment.
0 / 30 completed
1 / 30
The interviewer asks: "How would you explain to an archivist why the preservation system just flagged a batch of digitized reels for re-migration even though the files play back fine in the current viewer?" Which answer best demonstrates clear communication?
Option B explains that current playback success and long-term format-ecosystem viability are different signals, and that a shrinking pool of supporting tools is exactly the kind of risk a single playback check can’t surface, which is why re-migration is flagged proactively. The other options claim false certainty or misstate what the system actually evaluates.
2 / 30
The interviewer asks: "After a checksum-verification tool update, one storage node’s fixity reports started disagreeing with the master catalog’s recorded checksums, while every other node remained consistent. How do you investigate?" Which answer shows the most rigorous diagnostic thinking?
Option B checks what is different about the affected node’s file-format mix, reviews the update’s changelog for checksum-calculation changes, and independently recomputes a sample to localize whether the fault is in the update’s logic or the files themselves. The other options jump to a hardware conclusion, dismiss the master catalog outright, or wrongly rule out the update.
3 / 30
The interviewer asks: "What is the difference between bit-level preservation and format migration in a digital-archive strategy, and how do they work together?" Which answer is most technically precise?
Option B correctly separates bit-level preservation’s continuous integrity guarantee from format migration’s periodic, riskier conversion step, and explains why fixity checks around a migration are what confirm it didn’t introduce silent corruption. The other options invert the two concepts or invent a media-type restriction that does not exist.
4 / 30
The interviewer asks: "How do you decide whether a digitized item with a detected quality issue should trigger an automatic re-digitization request versus accepting the current scan into the archive?" Which answer best demonstrates sound engineering judgment?
Option B weighs the physical original’s ability to tolerate re-handling, the severity of the issue’s effect on legibility, and whether the item is unique before recommending re-digitization versus accepting the current scan. The other options ignore the real trade-off between preservation quality and added physical risk or staff time.
5 / 30
The interviewer asks: "Tell me about a time your archive’s automated metadata-extraction tool disagreed noticeably with an archivist’s manual cataloging on the same item. What was the outcome?" Which answer best follows a structured STAR approach with concrete detail?
Option B identifies a plausible root cause, an embedded scan-date property being mistaken for a creation date, verifies it against provenance documentation, finds the same failure elsewhere in the collection, and delivers a validated finding plus a preventive maintainer recommendation. The other options are vague or lack the technical specificity and verified result.
6 / 30
Reviewer: "This PR attempts to update the metadata for the 'Smith Collection' reels. However, the script is using a deprecated API endpoint for checksum calculation – it's returning inconsistent results compared to our master catalog. Can you explain why this wasn't caught during testing?"
This question tests your ability to interpret feedback from a code review. The correct answer highlights a common issue – developers sometimes miss deprecation notices or fail to fully test new integrations. The other options present incorrect assumptions about the process and potential justifications for the error.
7 / 30
"Sarah (Archivist): Okay, I've just received a notification from the preservation system indicating that reels 123-128 of the 'Project Phoenix' collection require immediate re-migration. The system is claiming significant data degradation based on statistical analysis. I'm not seeing any obvious issues with playback, but I need to understand this better."
This scenario focuses on communication within a team. The correct response involves gathering more data and seeking technical clarification – mirroring how an archivist would approach a potentially complex issue. The other options represent reactive or overly cautious actions without sufficient understanding.
8 / 30
PR Description: "Implemented a new script to automatically generate thumbnails for all digital assets in the 'National Geographic' archive. This improves accessibility and searchability. The script uses the libjpeg-turbo library for optimized image processing."
This tests your ability to write clear and concise PR descriptions. While technically correct, the provided description needs more context for someone who isn't a developer. It misses explaining *why* thumbnails are beneficial (accessibility, search) – key information for stakeholders.
9 / 30
"David (Engineer): Today I was troubleshooting an issue with the automated metadata extraction tool flagging discrepancies on several 'World War II' documents. The tool consistently identified different descriptions for key events compared to the archivist's manual cataloging. I've narrowed it down to a potential misinterpretation of date formats within the source materials – further investigation is needed."
This assesses your ability to communicate effectively during a standup update. David's response follows the STAR method (Situation, Task, Action, Result – implied), clearly outlining the problem, his investigation, and planned next steps. This is crucial for transparent communication with stakeholders.
10 / 30
API Response (from the preservation system): "{
"status": 'error',
"code": 409,
"message": 'Conflict: Metadata record already exists for this asset with a different version."
}
This question tests your ability to interpret an API response. The 409 Conflict status indicates that the system encountered a problem due to existing data – specifically a duplicate record. The correct interpretation highlights this and suggests further investigation is warranted.
11 / 30
Reviewer: "This PR attempts to update the metadata for the 'Smith Collection' reels. However, the script is using a deprecated API endpoint for checksum calculation – it's returning inconsistent results compared to our master catalog. Can you explain why this wasn't caught during testing?"
This question tests your ability to interpret feedback from a code review. The correct answer highlights a common issue – developers sometimes miss deprecation notices or fail to fully test new integrations. The other options present incorrect assumptions about the process and potential justifications for the error.
12 / 30
"Sarah (Archivist): Okay, I've just received a notification from the preservation system indicating that reels 123-128 of the 'Project Phoenix' collection require immediate re-migration. The system is claiming significant data degradation based on statistical analysis. I'm not seeing any obvious issues with playback, but I need to understand this better."
This scenario focuses on communication within a team. The correct response involves gathering more data and seeking technical clarification – mirroring how an archivist would approach a potentially complex issue. The other options represent reactive or overly cautious actions without sufficient understanding.
13 / 30
PR Description: "Implemented a new script to automatically generate thumbnails for all digital assets in the 'National Geographic' archive. This improves accessibility and searchability. The script uses the libjpeg-turbo library for optimized image processing."
This tests your ability to write clear and concise PR descriptions. While technically correct, the provided description needs more context for someone who isn't a developer. It misses explaining *why* thumbnails are beneficial (accessibility, search) – key information for stakeholders.
14 / 30
"David (Engineer): Today I was troubleshooting an issue with the automated metadata extraction tool flagging discrepancies on several 'World War II' documents. The tool consistently identified different descriptions for key events compared to the archivist's manual cataloging. I've narrowed it down to a potential misinterpretation of date formats within the source materials – further investigation is needed."
This assesses your ability to communicate effectively during a standup update. David's response follows the STAR method (Situation, Task, Action, Result – implied), clearly outlining the problem, his investigation, and planned next steps. This is crucial for transparent communication with stakeholders.
15 / 30
API Response (from the preservation system): "{
"status": 'error',
"code": 409,
"message": 'Conflict: Metadata record already exists for this asset with a different version."
}
This question tests your ability to interpret an API response. The 409 Conflict status indicates that the system encountered a problem due to existing data – specifically a duplicate record. The correct interpretation highlights this and suggests further investigation is warranted.
16 / 30
Reviewer: "This PR attempts to update the metadata for the 'Smith Collection' reels. However, the script is using a deprecated API endpoint for checksum calculation – it's returning inconsistent results compared to our master catalog. Can you explain why this wasn't caught during testing?"
This question tests your ability to interpret feedback from a code review. The correct answer highlights a common issue – developers sometimes miss deprecation notices or fail to fully test new integrations. The other options present incorrect assumptions about the process and potential justifications for the error.
17 / 30
"Sarah (Archivist): Okay, I've just received a notification from the preservation system indicating that reels 123-128 of the 'Project Phoenix' collection require immediate re-migration. The system is claiming significant data degradation based on statistical analysis. I'm not seeing any obvious issues with playback, but I need to understand this better."
This scenario focuses on communication within a team. The correct response involves gathering more data and seeking technical clarification – mirroring how an archivist would approach a potentially complex issue. The other options represent reactive or overly cautious actions without sufficient understanding.
18 / 30
PR Description: "Implemented a new script to automatically generate thumbnails for all digital assets in the 'National Geographic' archive. This improves accessibility and searchability. The script uses the libjpeg-turbo library for optimized image processing."
This tests your ability to write clear and concise PR descriptions. While technically correct, the provided description needs more context for someone who isn't a developer. It misses explaining *why* thumbnails are beneficial (accessibility, search) – key information for stakeholders.
19 / 30
"David (Engineer): Today I was troubleshooting an issue with the automated metadata extraction tool flagging discrepancies on several 'World War II' documents. The tool consistently identified different descriptions for key events compared to the archivist's manual cataloging. I've narrowed it down to a potential misinterpretation of date formats within the source materials – further investigation is needed."
This assesses your ability to communicate effectively during a standup update. David's response follows the STAR method (Situation, Task, Action, Result – implied), clearly outlining the problem, his investigation, and planned next steps. This is crucial for transparent communication with stakeholders.
20 / 30
API Response (from the preservation system): "{
"status": 'error',
"code": 409,
"message": 'Conflict: Metadata record already exists for this asset with a different version."
}
This question tests your ability to interpret an API response. The 409 Conflict status indicates that the system encountered a problem due to existing data – specifically a duplicate record. The correct interpretation highlights this and suggests further investigation is warranted.
21 / 30
Reviewer: "This PR attempts to update the metadata for the 'Smith Collection' reels. However, the script is using a deprecated API endpoint for checksum calculation – it's returning inconsistent results compared to our master catalog. Can you explain why this wasn't caught during testing?"
This question tests your ability to interpret feedback from a code review. The correct answer highlights a common issue – developers sometimes miss deprecation notices or fail to fully test new integrations. The other options present incorrect assumptions about the process and potential justifications for the error.
22 / 30
"Sarah (Archivist): Okay, I've just received a notification from the preservation system indicating that reels 123-128 of the 'Project Phoenix' collection require immediate re-migration. The system is claiming significant data degradation based on statistical analysis. I'm not seeing any obvious issues with playback, but I need to understand this better."
This scenario focuses on communication within a team. The correct response involves gathering more data and seeking technical clarification – mirroring how an archivist would approach a potentially complex issue. The other options represent reactive or overly cautious actions without sufficient understanding.
23 / 30
PR Description: "Implemented a new script to automatically generate thumbnails for all digital assets in the 'National Geographic' archive. This improves accessibility and searchability. The script uses the libjpeg-turbo library for optimized image processing."
This tests your ability to write clear and concise PR descriptions. While technically correct, the provided description needs more context for someone who isn't a developer. It misses explaining *why* thumbnails are beneficial (accessibility, search) – key information for stakeholders.
24 / 30
"David (Engineer): Today I was troubleshooting an issue with the automated metadata extraction tool flagging discrepancies on several 'World War II' documents. The tool consistently identified different descriptions for key events compared to the archivist's manual cataloging. I've narrowed it down to a potential misinterpretation of date formats within the source materials – further investigation is needed."
This assesses your ability to communicate effectively during a standup update. David's response follows the STAR method (Situation, Task, Action, Result – implied), clearly outlining the problem, his investigation, and planned next steps. This is crucial for transparent communication with stakeholders.
25 / 30
API Response (from the preservation system): "{
"status": 'error',
"code": 409,
"message": 'Conflict: Metadata record already exists for this asset with a different version."
}
This question tests your ability to interpret an API response. The 409 Conflict status indicates that the system encountered a problem due to existing data – specifically a duplicate record. The correct interpretation highlights this and suggests further investigation is warranted.
26 / 30
Reviewer: "This PR attempts to update the metadata for the 'Smith Collection' reels. However, the script is using a deprecated API endpoint for checksum calculation – it's returning inconsistent results compared to our master catalog. Can you explain why this wasn't caught during testing?"
This question tests your ability to interpret feedback from a code review. The correct answer highlights a common issue – developers sometimes miss deprecation notices or fail to fully test new integrations. The other options present incorrect assumptions about the process and potential justifications for the error.
27 / 30
"Sarah (Archivist): Okay, I've just received a notification from the preservation system indicating that reels 123-128 of the 'Project Phoenix' collection require immediate re-migration. The system is claiming significant data degradation based on statistical analysis. I'm not seeing any obvious issues with playback, but I need to understand this better."
This scenario focuses on communication within a team. The correct response involves gathering more data and seeking technical clarification – mirroring how an archivist would approach a potentially complex issue. The other options represent reactive or overly cautious actions without sufficient understanding.
28 / 30
PR Description: "Implemented a new script to automatically generate thumbnails for all digital assets in the 'National Geographic' archive. This improves accessibility and searchability. The script uses the libjpeg-turbo library for optimized image processing."
This tests your ability to write clear and concise PR descriptions. While technically correct, the provided description needs more context for someone who isn't a developer. It misses explaining *why* thumbnails are beneficial (accessibility, search) – key information for stakeholders.
29 / 30
"David (Engineer): Today I was troubleshooting an issue with the automated metadata extraction tool flagging discrepancies on several 'World War II' documents. The tool consistently identified different descriptions for key events compared to the archivist's manual cataloging. I've narrowed it down to a potential misinterpretation of date formats within the source materials – further investigation is needed."
This assesses your ability to communicate effectively during a standup update. David's response follows the STAR method (Situation, Task, Action, Result – implied), clearly outlining the problem, his investigation, and planned next steps. This is crucial for transparent communication with stakeholders.
30 / 30
API Response (from the preservation system): "{
"status": 'error',
"code": 409,
"message": 'Conflict: Metadata record already exists for this asset with a different version."
}
This question tests your ability to interpret an API response. The 409 Conflict status indicates that the system encountered a problem due to existing data – specifically a duplicate record. The correct interpretation highlights this and suggests further investigation is warranted.
What does "Digital Archive Preservation Engineer Interview Questions — coderslingo.com" cover?
Practise English for Digital Archive Preservation Engineer interviews. 5 exercises on format re-migration explanation, checksum-disagreement diagnosis, bit-preservation vs. migration trade-offs, and re-digitization judgment.
How many questions are in this interview set?
This set has 30 exercises, each with a full explanation.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do these exercises include model answers?
Yes. Each interview question gives you several possible responses and asks you to pick the one that communicates most clearly and completely — the explanation then breaks down exactly why that answer works, including the specific vocabulary a strong candidate would use.
What if I choose an answer that isn't the strongest one?
You'll see which option was correct and read a full explanation of why it's stronger than the alternatives, plus the key vocabulary and phrasing worth reusing in a real interview.
Can I retry the questions?
Yes — use the "Try again" button on the results screen to reset and go through the set again.
Is this the same as a real technical or behavioural interview?
No — it's focused practice for the language side of interviewing: recognising which phrasing sounds precise and confident versus vague, and knowing the vocabulary interviewers expect for this role. It won't replace mock interviews, but it builds the vocabulary you'll need in one.
Where can I find interview prep for other roles?
Browse the full Interview exercises hub for 170+ modules covering behavioural, technical, and system design rounds across dozens of IT roles, or check the "Next up" link below to continue.
Do I need an account, and is my progress saved?
No account is needed. Progress is tracked only for your current visit — reloading or leaving the page resets the counter.
Who writes these interview questions?
Every question is written by the CoderSlingo team based on real technical interview patterns for this role, then reviewed for accuracy and clarity.