Design a tamper-evident video chain-of-custody audit system
AxonSoftware Engineer · Technical ScreenLast updated
Design a tamper-evident video chain-of-custody audit system evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
Design a scalable, tamper-evident audit logging system for video evidence that preserves an accurate chain of custody. The system must record all actions (upload, view, redact/delete sensitive data, transcribe), never lose an event, and support legal discovery. Specify:
- functional and non-functional requirements;
- architecture and storage choices (e.g., append-only log, replication, WORM/immutable storage);
- event schema, ordering, idempotency, and delivery guarantees (exactly-once vs at-least-once);
- integrity mechanisms (hash chaining/Merkle trees, digital signatures), encryption and key management, and access controls;
- scalability, partitioning, and backpressure handling;
- APIs and query patterns for auditors and investigators;
- retention policies, legal hold, and compliance considerations;
- monitoring, audit-of-the-auditor, and disaster recovery;
- cost/latency trade-offs and capacity planning;
- testing, verification, and rollout plan.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.