A portfolio is highly recommended — reviewers want to assess writing clarity, technical accuracy, and information architecture before scheduling interviews. Link to published documentation, sanitized samples, or a personal documentation site. API documentation samples are particularly valued for software company roles.

Reference your process for working with subject matter experts: SME interview techniques, API testing to verify documentation accuracy, documentation review cycles with engineering teams, or participation in sprint ceremonies. 'Embedded with 3 engineering squads on Agile sprints, producing documentation concurrent with feature development rather than post-release' shows modern collaborative documentation practice.

Docs-as-code involves managing documentation in version control (Git), writing in plain text formats (Markdown, reStructuredText), and deploying via CI/CD pipelines. It's increasingly standard practice at tech companies. If you've contributed to documentation repositories in Git, used static site generators like Docusaurus or MkDocs, or set up documentation CI/CD, that experience is worth highlighting explicitly.