Principal Technical Writer

Role Overview

As Principal Technical Writer, you will work with customer-facing technical teams to design and deliver product information that enables enterprise customers to self-implement and self-support. You'll understand business operations goals, identify jobs-to-be-done, develop AI frameworks, and write documentation and enablement materials that enterprise customers need to succeed.

What You Will Do

Remove obstacles to self-implementation and self-support for complex customer businesses by designing and writing cross-cutting enablement documentation. Write for enterprise customer technical leadership and support teams, producing implementation guides, architecture overviews, integration patterns, and best practices.

Why It Might Be a Fit

8+ years of technical writing experience for enterprise products, with demonstrated ownership of major documentation domains or platforms. Deep expertise in developer documentation: REST APIs, OpenAPI/Swagger, authentication protocols, integration patterns, webhooks, data models.

Requirements

• 8+ years of technical writing experience for enterprise products
• Deep expertise in developer documentation: REST APIs, OpenAPI/Swagger, authentication protocols, integration patterns, webhooks, data models
• Experience writing for technical decision-makers (engineering leaders, CTOs, enterprise architects) and complex implementation scenarios
• Proven ability to design cross-cutting documentation strategies that solve problems affecting multiple audiences (developers, integrators, support teams, customers)
• Hands-on experience with AI documentation tools or demonstrated ability to evaluate AI-generated content for accuracy, completeness, and usefulness
• Strong technical fluency: comfortable testing APIs, writing code examples, understanding system architecture, and partnering with engineering teams as a technical peer
• Demonstrated expertise in information architecture for complex product ecosystems—designing maintainable documentation structures
• Strong systems thinking: ability to balance short-term documentation delivery with long-term architectural integrity and scalability
• Excellent stakeholder management and ability to influence product development teams to include product information and communication as part of the definition of done

Benefits

• Competitive compensation and benefits programs
• Cash compensation (overtime, bonus/commissions if eligible)
• Equity
• Benefits

Originally posted on Himalayas