Senior Technical Writer

Neo; Bengaluru; On-site; INR 1,200,000 - 2,400,000; Full time

Job summary

Neo seeks a Senior Technical Writer to take ownership of how Neo's products explain themselves—through feature docs, user guides, knowledge base articles, FAQs, release notes, and other technical publications.

This hands-on IC role combines editorial judgment with an automation mindset, building skill files and templates so AI can generate consistent drafts, grounded in a codified Neo tone and style.

Qualifications

• 5+ years writing technical documentation.
• 1–2+ years owning editorial standards for a team.
• Experience partnering with product and engineering teams.
• Computer science background.
• Nice to have: experience contributing to or maintaining an open source project.
• Nice to have: a public writing track record on technical or documentation topics.

Responsibilities

• Read PRDs and engineering specs closely, and translate them into clear, concise documentation - user guides, knowledge base articles - organized with clean, findable information architecture
• Define and maintain Neo's documentation style guide, voice, and tone; and hold every contributor to it
• Own end‑to‑end documentation quality (completeness, accuracy, consistency, tone) across every Neo product, and report on documentation health (coverage, freshness, usage) on an ongoing basis
• Flag issues with the underlying feature, not just the docs, when something won't serve users well or a spec lacks the detail needed for accurate documentation; partner closely with PMs and engineers to close those gaps and stay aligned with the release roadmap
• Set direction for Neo's AI-powered documentation automation - skill files, prompt templates, scripts - deciding what to automate and how it should scale; maintain and evolve these systems as products and doc formats change

Skills

Technical writing

AI/documentation automation

Strong written communication

Project management

Systems thinking

Education

Computer science background

Tools

Jira

Linear

Notion

Job description

AI is the most significant shift in how work gets done since the advent of the Internet — yet most organizations fail to capture its value. Neo is changing that.

Founded by Bhavin Turakhia — Co-Founder of Zeta, Radix, and Titan — Neo is building an integrated, AI-first suite of products that capture work, centralize context, and make AI a first-class participant in every workflow:

• Friday — AI Assistant, co-worker and agent platform, pre-integrated into Tasket, Studio, Drive and 1000+ SaaS platforms.
• Tasket — A radically reimagined, AI-native, work management platform that centralizes context and makes AI delegation seamless for all work.
• Studio — AI-native suite for co-creating docs, spreadsheets and diagrams collaboratively with humans and agents.
• Scribe — AI assistant for meetings that goes beyond note-taking and actually does your work while on the call.

About the role

Neo is seeking a Senior Technical Writer to join our Product Documentation team and take ownership of how Neo's products explain themselves - through feature docs, user guides, knowledge base articles, FAQs, release notes, and any other technical writing we publish for the outside world.

At Neo, documentation isn't a support function bolted onto the product - it's a product surface in its own right, and a community asset that accelerates adoption by helping people learn and trust Neo. We run docs-as-code and docs-as-a-product: writing lives in Git, ships through review like any other product change, and is held to a real quality bar, built in close partnership with Product and Engineering.

You read specs closely enough to catch what they leave out, understand what a user actually needs to know, and write it clearly. You don't stop at drafting one page at a time, you build the systems behind it: the skill files and prompt templates that let AI tools generate consistent first drafts from PRDs and tickets, grounded in a tone and style you've codified so every draft, human or AI, sounds like Neo.

This is a hands‑on, build‑the‑system individual contributor role that calls for a combination of strong editorial judgment and an automation mindset.

Responsibilities

Write & organize

• Read PRDs and engineering specs closely, and translate them into clear, concise documentation - user guides, knowledge base articles - organized with clean, findable information architecture

Set the standard

• Define and maintain Neo's documentation style guide, voice, and tone; and hold every contributor to it
• Own end‑to‑end documentation quality (completeness, accuracy, consistency, tone) across every Neo product, and report on documentation health (coverage, freshness, usage) on an ongoing basis

Partner & advocate

• Flag issues with the underlying feature, not just the docs, when something won't serve users well or a spec lacks the detail needed for accurate documentation; partner closely with PMs and engineers to close those gaps and stay aligned with the release roadmap

Build the system

• Set direction for Neo's AI-powered documentation automation - skill files, prompt templates, scripts - deciding what to automate and how it should scale; maintain and evolve these systems as products and doc formats change

Skills

• Technical fluency to read, question, and explain PRDs and API specifications directly with engineers and PMs, understand and document Neo's APIs and MCP tools, and ensure the accuracy of every customer-facing doc that depends on them
• Strong written communication - this is a writing-first role requiring the editorial judgment to set the bar for others, plus experience defining or maintaining a style guide, voice/tone standard, or review process, and the instinct to know when something's ready to publish
• Strong project‑management instincts - able to plan, prioritize, and carry a complex documentation project to an accurate, polished finish, with working knowledge of tools like Jira, Linear, or Notion
• Hands‑on experience with AI - not just prompting in the moment, but building the reusable system behind it (skill files, prompt templates, context files) so AI can produce consistent, on‑brand first drafts without constant re‑prompting
• Systems‑thinking mindset - with automation instincts, able to design processes that scale as the team and product surface grow

Experience

• 5+ years writing technical documentation, with a solid understanding of version control and experience managing documentation systems
• 1–2+ years owning editorial standards or leading a documentation function for a team - ideally at a B2B SaaS or product company
• Track record partnering with product and engineering teams to close documentation gaps and improve PRD quality
• Computer science/ background
• Nice to have: experience contributing to or maintaining an open source project
• Nice to have: a public writing track record on technical or documentation topics - a blog, newsletter, or bylined guest posts