API Documentation, Continuous Improvement, Customer/Client Research, Document Management, Documentation, Documentation Review, Documentation Standards, Editing, Frequently Asked Questions (FAQ), Information Architecture, Knowledge Base, Machine Tool, Metadata, Online Help, Operational Support, Product Engineering, Quality Management, Release Notes, Requirements Management, Standard Operating Procedures (SOP), Style Guide, Support Documentation, Taxonomies, Technical Writing, Time Management, Usability Engineering, User Documentation, Writing Skills
Pay rate range - $50/hr. to $57/hr.
Hybrid - 2-3 Days in Office
Job Description
Role Summary
The Technical Writer is responsible for planning, writing, editing, and maintaining clear, accurate, and user-focused documentation for technical and non-technical audiences.
This role partners with product, engineering, operations, and support teams to translate complex concepts into concise documentation that improves usability, adoption, and operational excellence.
Key Responsibilities
Produce and maintain high-quality technical documentation (e.g., user guides, online help, release notes, API documentation, SOPs, FAQs, knowledge base articles).
Gather requirements and source information by partnering with SMEs (engineering, product, security, operations, support) through interviews, document reviews, and tool walkthroughs.
Translate complex technical workflows into step-by-step instructions, diagrams, and reference content appropriate for target audiences.
Establish and follow documentation standards, templates, and style guidelines to ensure consistency across deliverables.
Edit and revise content for clarity, accuracy, accessibility, readability, and brand/style compliance.
Manage documentation versioning, publishing, and lifecycle maintenance; retire outdated content and ensure timely updates aligned to releases.
Create information architecture plans (navigation, taxonomy, metadata/tagging) to improve content discoverability.
Collaborate with teams to embed documentation into delivery processes (e.g., definition of done, release readiness).
Track documentation requests, priorities, and status; communicate milestones and risks to stakeholders.
Support documentation tooling and continuous improvement (e.g., content audits, analytics, user feedback loops).
What Success Looks Like (Examples)
Documentation is accurate, discoverable, and consistently formatted across teams.
Release notes and procedural docs are delivered on time and aligned to product releases.
Support tickets and repetitive questions decrease due to improved self-service content.
Stakeholders trust documentation as the "single source of truth.”
I
Intelliswift Software Inc