Design Internal Q&A Forum - System Design | WinJob

Problem Statement: Internal Q&A Forum

An internal Q&A forum is the company's Stack Overflow: employees post questions, peers submit answers, votes surface quality, and one accepted answer becomes canonical knowledge. Interviews test whether you treat it as multi-tenant knowledge with space ACLs, idempotent voting, and search that never leaks confidential tags—not a public forum behind VPN. Stack Overflow for Teams, Tribe, and Discourse all share the same hot paths: write question → fanout notifications → aggregate votes → rank feed → index for search.

Dominant failure modes are vote counter hot keys on viral threads, accepted-answer races when two moderators act concurrently, and search ACL drift after org changes. Separate the authoritative thread store (Postgres) from vote aggregates (Redis/Cassandra) and search derivatives (OpenSearch) fed by transactional outbox. Reads are 12:1 versus writes; spikes follow incident response or product launches.

Engineering notes (problem-statement-internal-q-a-forum)

Propagate company_id from JWT on every write and search filter.
Persist votes with idempotency keys before incrementing Redis counter deltas.
Commit accept-answer in one transaction; emit outbox only after commit.
Run deny-leak canaries after space ACL or HRIS group bulk sync.
Degrade notification fanout and WS events before dropping vote ingestion.

javaOne Dark Pro

1 public final class ForumGuard1 {
2   public boolean canPost(String companyId, String spaceId, Set<String> groups, String requiredRole) {
3     if (companyId == null || spaceId == null || groups == null) return false;
4     return groups.contains(requiredRole) || groups.contains("forum-moderator");
5   }
6 }

pythonOne Dark Pro

1 def vote_idempotency_key(voter_id: str, target_type: str, target_id: str, client_key: str) -> str:
2     import hashlib
3     payload = f"{voter_id}:{target_type}:{target_id}:{client_key}"
4     return hashlib.sha256(payload.encode()).hexdigest()[:24]

typescriptOne Dark Pro

1 export interface ForumQuestionRow {
2   companyId: string;
3   spaceId: string;
4   questionId: string;
5   acceptedAnswerId: string | null;
6   scoreCache: number;
7   aclSnapshotVersion: string;
8   focus: "problem-statement-internal-q-a-forum";
9 }

Why interviewers care

Internal Q&A Forum interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Problem Statement: Internal Q&A Forum that proves you understand real outages, not happy-path diagrams.

Key Highlights

•sec-001: understanding — Problem Statement: Internal Q&A Forum anchors idempotent votes, accept transaction, and ACL-safe search.
•Postgres thread rows are authoritative; Redis counters and OpenSearch are derived views.
•Under load, shed notify/WS before vote ingestion for Problem Statement: Internal Q&A Forum.

1	public final class ForumGuard1 {
2	public boolean canPost(String companyId, String spaceId, Set<String> groups, String requiredRole) {
3	if (companyId == null \|\| spaceId == null \|\| groups == null) return false;
4	return groups.contains(requiredRole) \|\| groups.contains("forum-moderator");
5	}
6	}

1	def vote_idempotency_key(voter_id: str, target_type: str, target_id: str, client_key: str) -> str:
2	import hashlib
3	payload = f"{voter_id}:{target_type}:{target_id}:{client_key}"
4	return hashlib.sha256(payload.encode()).hexdigest()[:24]

1	export interface ForumQuestionRow {
2	companyId: string;
3	spaceId: string;
4	questionId: string;
5	acceptedAnswerId: string \| null;
6	scoreCache: number;
7	aclSnapshotVersion: string;
8	focus: "problem-statement-internal-q-a-forum";
9	}

Problem Statement: Internal Q&A Forum

Engineering notes (problem-statement-internal-q-a-forum)

Why interviewers care

Interview checkpoint

Key Highlights

Section Rescue Kit