74. Design synchronization for field inspectors who edit the same inspection offline on different devices.
HardSystem design
Technical
Show model answer
Clarify what may be edited concurrently, the cost of losing a change and how long devices can remain offline. Give records stable identities and versioned changes. Simple last-write-wins may be acceptable for a preference but unsafe for conflicting inspection findings.
Choose field-level merging or an explicit conflict workflow for consequential data, and retain an audit trail appropriate to the task. Explain deletion, attachments, authentication expiry and partial synchronization. Validate with duplicate uploads, clock differences and a device reconnecting after the record was closed.
What interviewers listen for
- Define conflict semantics
- Stable identity and versions
- Partial-sync recovery
- Offline edge cases