Large object S3-like store
Design the core write/read path of an S3-like object store focused on large objects: objects up to 5TB uploaded as multipart chunks over unreliable client connections, eleven-nines durability, strong read-after-write consistency for new objects, and high aggregate throughput. Ignore versioning/lifecycle — focus on how a multi-gigabyte object is durably written across the cluster and read back, and how the system stays consistent. How do you do it?
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify5:00 left
Estimate5:00 planned
Design15:00 planned
Deep dive12:00 planned
Failure8:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.