Object storage strong consistency
Design the metadata/consistency layer of an object store that must offer strong read-after-write and strongly-consistent list operations across multiple availability zones. Constraints: a PUT must be immediately visible to any subsequent GET or LIST from any client, overwrites must not expose a stale or torn version, the bucket can hold a billion keys (so LIST must be paginated and efficient), and the bytes themselves are already durably stored elsewhere. Focus on the metadata layer.
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.
Clarify4:30 left
Estimate4:30 planned
Design13:30 planned
Deep dive10:30 planned
Failure7: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.