Senior Technical Writer

Serve as the point of convergence for product and technology communication: Translate product and engineering decisions into clear, consumable documentation used across the company, including Support Center content and internal enablement materials.

Operate effectively in a dual workstream model: Manage a workload that is approximately 60% planned (proactive) within the product development pipeline and 40% unplanned (reactive) requests from Customer Support and Sales, maintaining prioritization, transparency, and throughput.

Own documentation scoping decisions: Evaluate new features and changes and decide the appropriate level and type of documentation required. Partner with PMs and Engineering, but do not rely on PMs to define documentation depth.

Drive early engagement in the product lifecycle: Proactively embed in discovery and delivery to avoid last-minute documentation work. Identify and escalate risk when documentation needs surface late (for example, changes coming in under three weeks).

Partner closely with Local Product and Engineering teams: Build strong working relationships to understand intent, technical constraints, and release timing, and to ensure documentation is accurate, supportable, and aligned with how the product will be used.

Align with and collaborate closely with a US-based Technical Writing team: Follow shared standards, templates, voice and tone, review practices, and tooling, and contribute to a consistent documentation experience across products.

Intake, track, and execute requests with rigor: Use a formal intake process (for example, a request form) to create and track work in Asana, ensuring stakeholders have clear status, scope, and delivery expectations.

Improve process adoption and documentation readiness: Help reinforce and operationalize documentation checkpoints in the release process (including NPI where applicable), ensuring documentation is treated as a deliverable, not an afterthought.

Enable downstream teams who depend on your output: Create content that can be effectively reused by Knowledge Management, Learning and Enablement, Operations, Marketing, and Training, recognizing that technical writing is a critical dependency for broader organizational readiness.

Experience: 5+ years of experience in technical writing, product documentation, or a related discipline, ideally supporting software products.

Documentation judgment: Demonstrated ability to scope documentation appropriately for a feature or change, including knowing when “lightweight” is sufficient versus when deeper conceptual, procedural, or troubleshooting coverage is required.

Cross-functional collaboration: Proven ability to work closely with Product Managers and Engineers, clarify ambiguous requirements, and drive to accurate, shippable documentation under time constraints.

Strong execution and prioritization: Comfortable balancing planned roadmap work with frequent reactive requests, and able to set expectations, negotiate scope, and communicate tradeoffs.

Writing craft: Ability to write clear, concise, user-centered documentation with strong information architecture, consistent tone, and high attention to detail.

Tooling: Working proficiency with Asana (or similar work management tools) and common documentation workflows. (If your environment includes a specific CMS, this can be added explicitly.)

Process orientation: Comfort working with defined intake and tracking processes and improving them over time through retrospectives and stakeholder feedback.

Communication: Strong written and verbal communication, including the ability to collaborate asynchronously with a US-based team across time zones.

Experience contributing to Support Center / knowledge base content and operational documentation used by Customer Support and Sales.

Familiarity with product development processes such as NPI or equivalent release gating, and experience improving adoption of documentation checkpoints.

Experience writing for workflow-heavy B2B products or technical audiences.

Knowledge of content reuse approaches (modular writing, single-sourcing, templates) and lightweight governance practices.

You will partner daily with India-based Product and Engineering to capture accurate technical details and align documentation with delivery timelines.

You will align weekly with a US Technical Writing team, participating in regular editorial reviews, prioritization discussions, and standards alignment to ensure consistency.

You will use a structured intake process (request form) and track execution in Asana to manage both planned pipeline work and reactive requests.