Senior Technical Writer

Key Responsibilities

• Own the help center. Plan, write, and maintain help center articles, troubleshooting guides, and how-to content for complex platform features, from processing and workflow automation to review, link analysis, and deployment.
• Write release notes and user guides. Turn every product release into clear, accurate release notes, and keep user guides current — the canonical record of what changed and how to use it.
• Produce support and enablement docs. Create the internal knowledge articles, runbooks, and enablement material that support engineers, customer success, and partners rely on to resolve complex cases — and that feeds downstream training, sales, and marketing content.
• Write with AI. Use AI tools (Claude, GPT, Copilot, or similar) throughout your workflow — drafting, restructuring, summarizing release notes into articles — while owning accuracy, voice, and technical correctness of every published word.
• Write for AI. Structure content, taxonomy, and metadata so AI support agents and retrieval systems answer from it accurately — self-contained articles, clean headings, unambiguous terminology, one question answered per article.
• Build AI documentation workflows. Set up and improve pipelines such as docs-as-code publishing, AI-assisted review and style checks, and content-gap detection from support tickets and AI-agent miss reports.
• Partner deeply. Work with product managers, engineers, and support leads to extract how features actually work, and turn sprawling technical detail into content a stressed user can follow.
• Measure and improve. Treat the docs as a product with measurable results. Track ticket deflection, article performance, search success, and AI-agent answer quality; report on how your content moves those numbers; and use the data to decide what to write, fix, or retire next. Great documentation here shows up in the metrics — lower support load, faster time-to-resolution, and self-service that actually resolves.

Skills, Knowledge and Expertise

• 5–8 years working with complex enterprise software — as a technical writer, or in engineering, product management, or support roles with a strong writing record. We actively welcome people who moved into writing from technical careers; show us the writing.
• Demonstrated, hands-on use of AI in your writing practice — you can show how AI changed your throughput and quality, not just that you've tried it.
• Experience structuring knowledge bases for AI consumption or self-service deflection (e.g., optimizing content for Zendesk AI, Intercom Fin, or an in-house RAG system).
• Docs-as-code fluency: Markdown, Git, static site generators or modern KB platforms, and comfort working in engineering workflows.
• Strong information architecture: taxonomy, content models, structured authoring, and single-sourcing.
• The ability to learn genuinely difficult domains fast and interview subject-matter experts effectively. An outcome mindset: you judge your own work by whether users succeed, not by whether the page shipped.
• A love and knack for language. You get real satisfaction from expressing complex ideas in easy concepts — plain, precise prose that cuts jargon without cutting accuracy.

Desired Expertise :

As we expand our global team and extend our skills and expertise, we are unified as one Nuix team guided by our shared values. Nuix Vision

• Finding Truth in a Digital World.

Nuix Mission Statement

Nuix Values

**Nuix is an Equal Opportunity Employer**