Design Message Pinning - System Design | WinJob

Problem framing and interview goal

Designing message pinning sounds simple, but interviewers use it to test ordering, permissioning, fan-out, and state convergence across online and offline clients.

Core decision narrative

We treat a pin as an explicit domain event with actor, scope, and audit metadata.
We separate durable pin state from ephemeral websocket fan-out.
We enforce permission checks at command time and again at read-materialization time.
We use deterministic ordering keys to avoid divergent UI ordering across devices.

Deep-dive notes

Problem framing and interview goal insight 1: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 2: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 3: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 4: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 5: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 6: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 7: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 8: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 9: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 10: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 11: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 12: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 13: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 14: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 15: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 16: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 17: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 18: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 19: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 20: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 21: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 22: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 23: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 24: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 25: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 26: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 27: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 28: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 29: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 30: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 31: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 32: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 33: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 34: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 35: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 36: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 37: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 38: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 39: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 40: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 41: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 42: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 43: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 44: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 45: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 46: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 47: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 48: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 49: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 50: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 51: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 52: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 53: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 54: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 55: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 56: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 57: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 58: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 59: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 60: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 61: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 62: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 63: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 64: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 65: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 66: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 67: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 68: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 69: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 70: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 71: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 72: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 73: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 74: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 75: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 76: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 77: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 78: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 79: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 80: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 81: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 82: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 83: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 84: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 85: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 86: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 87: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 88: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 89: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 90: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 91: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 92: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 93: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 94: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 95: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 96: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 97: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 98: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 99: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 100: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 101: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 102: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 103: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 104: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 105: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 106: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 107: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 108: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 109: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.
Problem framing and interview goal insight 110: The service keeps pin state deterministic by using monotonic version numbers and channel-scoped conflict resolution rules.

Why interviewers care

Message Pinning interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

The failure that defines the design

The outage to narrate is the dangling pin. Someone pins an important message; later the author deletes or edits it; now the pin points at nothing, or at content that no longer says what it did when it was pinned — a highlighted message that misleads or breaks. The fix is the spine of the design: a pin is a reference to a message, never a copy, so rendering always resolves to current content, and referential integrity is enforced — when the referenced message is deleted the pin is repaired (auto-unpinned or shown as removed), and an edit is simply reflected. State pin-as-reference with referential repair up front, because the whole correctness question for pinning is what happens to the pin when the thing it points at changes underneath it.

Key Highlights