A documentation site is a living field guide. Readers may change the binding, language sheet, or travel pack, but the bookmark must still point to the same concept.
The interview is not only about rendering Markdown. It is about content identity, stable URLs, edition-safe search, tested examples, internationalization, offline delivery, release coordination, and a reading surface that remains dependable during constant product change.
Clarify the publishing contract
Ask who authors content, which product versions remain supported, how translations are produced, whether code can execute in the browser, how often pages change, how large the corpus is, which pages need offline access, and what search freshness readers expect after a deploy.
Measure successful search-to-page navigation, zero-result rate by version and locale, stale-link rate, anchor survival, code-copy success, example test failures, translation coverage, offline-pack completion, cache mismatch recovery, Core Web Vitals, accessibility defects, and rollback time.
The public interview prompt
Design a documentation website for a developer platform. It must support multiple product versions and languages, fast full-text search, syntax-highlighted code samples, stable deep links, SEO, and optional offline reading.
Explain:
- canonical content identity, versioned and localized routes, redirects, durable headings, and URL history;
- authoring, validation, translation, code-sample testing, build manifests, publication, and rollback;
- static or server rendering, navigation hydration, search indexing, result ranking, and edition filtering;
- code tabs, copy and run behavior, wrapping, focus, annotations, and accessible language changes;
- service-worker lifecycle, explicit offline packs, cache budgets, freshness, quota, and deletion;
- analytics, privacy, abuse controls, performance budgets, observability, testing, and staged rollout.
What the premium solution covers
The complete solution treats documentation as immutable editions connected by a durable concept graph. A field-guide binder animation makes version, locale, search, and offline identity visible. A translator's type case, executable-sample flight case, and offline expedition satchel explain the hardest subsystems without repeating the visual forms used by neighboring guides. A deterministic lab turns corpus shape and release cadence into build, search, and cache budgets.