Senior Agentic Technical Writer

Our Mission

At Redwood, we empower our customers with lights-out automation for their mission-critical business processes.

About Us

Redwood Software is the leading orchestration platform for the autonomous enterprise, driving business transformation at the lowest total cost of ownership. Redwood empowers organizations to intelligently automate and orchestrate mission-critical business and IT processes across complex ERP, hybrid cloud, data and emerging agentic AI systems. Through its SaaS-first automation fabric, with AI embedded across the automation lifecycle, Redwood accelerates the path to autonomous operations. Backed by 30 years of experience and trusted by more than 50% of the Fortune 50, Redwood helps organizations unlock human potential to focus on innovation, growth and what's next.

Core Values

One Team. One Redwood

Make Your Own Weather

Obsess over Customer Success

Work the Problem

Be Curious

Own the Outcome

Respect Each Other

Your Impact

Redwood is rebuilding how documentation gets made. Content lives in Git as Markdown, ships through CI/CD, is reviewed by pull request next to product code, and is increasingly drafted by AI agents working from the product requirements, the code, and a structured content model. We are retiring our legacy authoring tool and moving every writer to this way of working.

You will be a senior writer who builds and runs that pipeline. You decide what an agent drafts and what a human must validate, you build the checks that catch failures, and you set the quality bar for AI-generated documentation. You also become a deep subject matter expert on Redwood's products and on the service orchestration and automation platform (SOAP) market they compete in, and you put what you learn back into the content model so every agent and writer inherits it.

This is a senior individual contributor role. You own a program, not a document set: the documentation pipeline and the content for a product area. You choose the approach on new work, guide more junior writers day to day, and have a significant say in documentation decisions for the business area. Not a people manager role.

Build and Run the Agentic Documentation Pipeline

Design, build, and operate AI-assisted and agentic workflows that draft new content and update existing pages from product requirements, merged code, API specifications, Jira tickets, and release information.

Define the handoffs: what the agent drafts, what the writer validates, how failures are detected, and how provenance is recorded. Publish the accuracy and review standards the team follows.

Own the content model and context layer that agents read: structure, terminology, glossary, style rules, reusable components, and product knowledge, so output is consistent and machine-readable for customers, partners, and AI assistants.

Build automated quality gates in CI: style and terminology linting, link checks, code sample and API reference validation, and an evaluation set that measures draft quality as models and prompts change.

Detect drift: flag documentation that no longer matches the product after a code or API change.

Measure the pipeline and report results: cycle time from release to published content, coverage, accuracy defects, reviewer edit effort, and cost per page.

Keep an honest model of where agents fail on Redwood content, and move the human-AI boundary as models improve.

Docs as Code

Own the Git workflow, Markdown/MDX authoring, build, and CI/CD publishing for your product area, with pull-request review alongside engineering.

Lead migration of legacy content into structured, versioned Markdown, including information architecture, redirects, search, and versioning.

Embed documentation in the delivery lifecycle: docs as a release gate, updates triggered by code and API changes, and documentation work that starts when the product definition is approved, in parallel with engineering rather than after it.

Produce OpenAPI-driven API reference and developer guides to the standard expected of a platform product.

Become the Subject Matter Expert on the Product and SOAP

Install, configure, and use the product yourself, and test new features before you document them.

Build working knowledge of how customers use orchestration across ERP, cloud, data, and IT operations, and how competing platforms position and document themselves. Use it to write content that explains how to apply the product to a business need, not only how to click through it.

Partner with product, engineering, support, and customer success to understand complex systems. Raise it early when a feature is hard to document, because that usually means it is hard to use.

Capture what you learn in the content model, so product knowledge compounds in the system and not only in your head.

Lead Through Craft

Teach other writers docs-as-code and agentic drafting through pairing, templates, review checklists, and onboarding material.

Review AI-generated and human-written content to one consistent bar.

Work with a distributed team across time zones, with clear written handoffs.

YOUR EXPERIENCE

8+ years of professional experience (6+ with a master's degree) in technical writing, documentation engineering, developer experience, or technical content for software. Open item: see the open items at the end of this document.

Docs as code in production, which you can show: a documentation repository or platform you built, migrated to, or ran, using Git, Markdown/MDX (or AsciiDoc or reStructuredText), a static site generator or docs platform (for example Mintlify, Docusaurus, MkDocs, Hugo), CI/CD publishing, and pull-request review. You can state the size of the content estate and who contributed.

An AI-assisted documentation pipeline in production. You can describe a specific workflow where AI drafts or updates content from a source such as a code diff, ticket, or API spec; what you validate before publishing; how the tool fails; and how your approach changed in the past six months. You can show the prompts, skills, or agent configuration and the checks around them.

Automated quality checks in CI that you set up, such as a prose linter (Vale or similar), link checking, code sample testing, or spec validation.

Shipped documentation for a technically complex product, and an example of getting to credible documentation in an unfamiliar, dense domain. Describe the process, not only the outcome.

Comfort reading code, API specifications, pull requests, and Jira to verify what you write, and running the product yourself.

Judgment about the trade-off between speed and accuracy in content that customers rely on for mission-critical systems.

Clear writing, and the ability to explain complex technical concepts to technical and business audiences.

Strongly Preferred

Agentic documentation: agents that act on a repository, such as opening pull requests, updating docs on merge, running checks, or looping on review feedback, with human approval gates and evaluations you designed. Experience with tool use or MCP is a plus.

Lead experience: you owned a documentation program, served as the technical lead for a group of writers, or guided other writers' work without a management title.

Content modeling and structured content: taxonomy, reusable components, or migration from a legacy authoring tool or DITA-style content to Markdown.

API documentation with OpenAPI and developer portals.

Enterprise software in automation, ERP, integration, data pipelines, ITSM, or workload automation, or direct familiarity with the SOAP market.

Documentation analytics used to decide what to write, fix, or retire.

Not Required

A long career under the title "technical writer."

Experience with MadCap Flare or any specific legacy authoring tool.

A machine learning background.

What We Will Ask You to Show

A walkthrough of an AI-assisted or agentic documenta