About the role
You keep a person's information usable and recoverable for years, which is a longer horizon than most storage work assumes. The failure mode that matters most here is quiet: backups that look successful and fail on restore, and migrations that lose something nobody notices for months.
The work
Design durable encrypted storage, snapshots, integrity checks, schema migration and conflict handling. Separate personal records from derived indexes and disposable caches. Work with cryptography and privacy engineers on backup keys, retention, deletion and restore behavior.
What good looks like
In your first 90 days, demonstrate recovery from a damaged database and an interrupted upgrade, with documented recovery-point and recovery-time results.
Evidence we look for
Bring experience with databases, filesystems or synchronization systems. Understand crash consistency, compaction, migration and how apparently successful backups can fail during restoration.
What we need to see
- Experience with databases, filesystems, or synchronisation systems at a level below the API
- You understand crash consistency, compaction, and migration, and have been burned by at least one
- You know how an apparently successful backup fails during restoration, because you have seen it
- You test recovery rather than assuming it
Nice to have
- Conflict resolution or CRDTs for multi-device sync
- Encrypted-at-rest storage where the user holds the key
- You have run a data migration with no acceptable loss
The exercise
Design a restore workflow that cannot silently reintroduce a previously deleted personal record.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.