Design a Shared-Interest Connection App
Help members find people with shared interests and form mutual connections while privacy changes take effect on later requests.
Problem statement
For this exercise, assume members of a community opt into discovery and share interests. A member can edit their interests, see people with at least one shared interest, send a connection request, and view its current status. Only the recipient can explicitly accept a pending request.
Opposite requests refer to one member pair and do not automatically accept a connection.
For this exercise, assume either member can block the other, or opt out of discovery. A new request starting after a completed block or opt-out must respect that change, including cached suggestion pages, relationship reads, and command results. A block suppresses both directions.
Unblocking restores eligibility but does not itself accept a pending request. Stored relationship history may remain. Retries must not create duplicate effects.
Design the member journey, data and API contracts, a minimum architecture, and the paths that keep discovery and connection actions consistent with these rules.
What to build
- Members can edit interests and opt into or out of discovery.
- Eligible members can find people with shared interests without receiving blocked or opted-out profiles.
- Members can send a request, and the recipient can explicitly accept it once.
- Members can read current request and connection status when current privacy permits it.
- Members can block or unblock another member; later reads and actions apply both directions of blocking.
At scale
- For this exercise, assume one million profiles and one hundred thousand daily active members.
- For this exercise, assume peak traffic of five hundred suggestion reads and fifty profile writes per second.
- For this exercise, target one-second p95 suggestion reads; interest changes may take up to sixty seconds to affect suggestions.
- For this exercise, privacy changes acknowledged before a new request starts must be reflected in that request; candidate index lag does not relax this rule.