As asked
You inherit 600 pages of engineering documentation with stale examples, duplicate setup guides, and no ownership. What do you do in the first quarter?
Sample answer outline
Start with an inventory and risk ranking rather than trying to fix every page. Prioritise high-traffic, high-support, and high-risk docs such as setup, authentication, billing, and migration pages. Assign ownership, archive or redirect duplicates, add freshness checks, and put sample code into CI where possible. The candidate should define quality metrics such as successful task completion, support deflection, docs issue volume, and broken-link or snippet failures. Strong answers include governance that fits engineering reality, because a docs programme fails if it depends on heroic manual review forever.
Expect these follow-ups
- How do you decide which stale docs to delete?
- How do you get engineers to review docs without making it a tax?
- Which docs quality metric is easiest to game?