Eventual Consistency
Also written as Strong Consistency, Read-After-Write Consistency
A system where a change reaches every copy of the data soon, but not instantly — so for a moment, two users can see different answers.
Think of it like
A rumour spreading through an office. Everyone hears it within the hour, but not all at the same minute.
Junior or senior?
High signal.
Senior sounds like
Talks about what the user actually saw during that gap, such as posting a comment and not seeing it appear, and what they did about it.
Ask them
“Where did eventual consistency show up as something a user could notice, and how did you handle it?”
Sounds like real experience
Describes a concrete user-visible symptom — a profile edit that seemed not to save, a stale count — and a specific mitigation such as reading from the primary right after a write.
Probe further if
Can define the term but has no example of it causing a problem, which usually means they read about it rather than operated it.