Enterprise search is a permissioned reading room. It borrows evidence from systems it does not own, keeps every result attached to its source and revision, and verifies that the current reader may still open it.
A company wiki, cloud drive, ticket system, and chat archive do not share one identity model, one freshness clock, or one ranking scale. Putting their text into the same list is the easy part. The hard part is making that list useful without leaking a title, excerpt, author, or existence through a stale permission copy.
The frontend therefore needs an evidence contract before it needs a polished search box.
Clarify the knowledge boundary before drawing the architecture
Ask which sources are searchable, whether the product indexes content or calls sources live, how quickly edits and permission revocations must appear, and whether titles themselves are sensitive. Define supported filters, result types, preview depth, source-opening behavior, ranking stability, audit requirements, and the meaning of “all sources searched.”
Measure first permission-filtered evidence, completed-source coverage, stale-access withdrawals, preview authorization time, result usefulness, keyboard travel, cache isolation, and connector failure. A single search-latency percentile cannot describe a federation.
The public interview prompt
Design a browser-based enterprise knowledge search that retrieves documents, wiki pages, tickets, and messages from several company systems.
Explain:
- draft and committed query state, filters, URL history, suggestions, and cancellation;
- tenant, principal, group projection, item ACL, connector, index, and preview boundaries;
- indexed retrieval, live federation, schema normalization, deduplication, ranking, and pagination;
- source identity, source revision, provenance, freshness, and partial-source coverage;
- revocation, source outages, throttling, stale snippets, missing previews, and retries;
- keyboard and screen-reader behavior, status messages, safe excerpts, and source navigation;
- caching, privacy, telemetry, performance budgets, testing, and staged rollout.
What the premium solution covers
The full solution stages federation as a permissioned research library. A reading-room animation routes one query into source alcoves, a permission aperture separates discoverability from preview access, a wall of source clocks makes freshness disagreement visible, and an evidence folio shows how normalization preserves provenance. A deterministic lab connects source fan-out, group expansion, excerpt size, connector delay, and ACL age to user-visible pressure.