Technical Documentation Writer

What You'll Do8

• Score AI-written documentation on technical accuracy, structure and readability, then justify each rating against recognized documentation practice.
• Compare competing model outputs for the same documentation task and label which one serves a developer or end user better.
• Write reference-grade examples of API references, task-based how-to guides and release notes that models can learn from.
• Produce sample user documentation and manuals that show correct structure, terminology and formatting choices.
• Flag factual errors, broken steps or misleading claims in generated docs and record what went wrong.
• Rank model responses in batches and keep judgments consistent across similar tasks and prompts.
• Apply docs-as-code conventions such as Markdown formatting and version control habits when you author your demonstrations.
• Document your reasoning so reviewers and researchers can see why a response earned its label.

Requirements8

• Two or more years writing technical documentation in a professional setting.
• A portfolio of docs you owned end to end, whether API references, guides, manuals or release notes.
• Track record of translating complex systems into accurate, readable instructions.
• Steady judgment when comparing outputs, since labeling must stay consistent across tasks.
• Comfort working on your own schedule without a manager checking in daily.
• Preferred: background in software, API or developer documentation.
• Preferred: hands-on experience with Markdown, Git and static site generators.
• Preferred: STC certification or a technical degree.

Who Should Apply

Technical writers with at least two years of documentation work and a portfolio of API references, guides or release notes they owned. You should enjoy picking apart how a system gets explained and hold a high bar for accuracy. Developers who write docs as part of their job may also fit.

Salary Insight