Technical Writer

Neo; Bengaluru; On-site; INR 600,000 - 900,000; Full time

Job summary

Neo seeks a documentation engineer to turn PRDs and product context into precise, scalable documentation. You will design automation that generates first-draft docs from structured inputs and refine them for accuracy. This hands-on role blends strong writing judgment with an automation mindset, not a pure writing or pure engineering job.

You will work with PMs and engineers to fill gaps, maintain documentation workflows, and continuously improve tooling as products evolve.

Qualifications

• Clear writing with the ability to read specs and translate into user guides, API docs, and runbooks.
• Design and build documentation automations to generate first-draft docs from structured inputs.
• Maintain and improve automation as products and doc formats evolve.
• Edit and fact-check AI-generated drafts against source material for accuracy.

Responsibilities

• Read PRDs and specs and translate into clear technical documentation: user guides, release notes, API docs, internal runbooks.
• Design and build documentation automations: skill files, prompt templates, scripts for AI-driven first drafts.
• Maintain and evolve automation as products and docs change.
• Edit and fact-check AI drafts against source material for accuracy and reliability.
• Organize docs in workspace tools and keep information architecture accessible.
• Collaborate with PMs and engineers to fill gaps and ensure detail sufficiency for docs.
• Push continuous improvements in documentation methodology and tooling.

Skills

Strong written communication

Technical fluency

Hands-on use of AI

Project management tools

Systems and process curiosity

Ambiguity tolerance

Education

CS/Engineering background

Tools

Confluence

Jira

Notion

Job description

About Neo

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.

About Job

We want someone whose job is turning PRDs and product context into documentation — and building the automation that makes that scale.

You are someone who reads a spec closely, understands what a user or engineer actually needs to know, and writes it clearly. But you don't stop at writing docs one at a time: you build repeatable workflows — skill files, prompt templates, structured inputs — that let AI tools generate consistent first drafts from PRDs, tickets, and changelogs, which you then refine and own.

This is a hands-on, build-the-system role. It's not a pure writing job where you manually draft every page, and it's not a pure engineering job either — it's the combination: strong writing judgment paired with an automation mindset.

Responsibilities

• Read PRDs and engineering specs and translate them into clear technical documentation — user guides, release notes, API docs, internal runbooks.


• Design and build documentation automations: skill files, prompt templates, and scripts that let AI tools generate consistent first-draft docs from structured inputs.


• Maintain and improve those automations over time as our product and doc formats evolve.


• Edit and fact-check AI-generated drafts against source material — you're accountable for accuracy, not just fluency.


• Organize documentation in our workspace tools and keep information architecture clean and findable.


• Partner closely with PMs and engineers to fill documentation gaps and flag when a PRD lacks the detail needed to write accurate docs.


• Continuously push on documentation methodology and tooling as our products evolve.
  

Skills

• Strong written communication — this is a writing-first role; verbal fluency alone won't cut it.


• Technical fluency: able to read a PRD or API spec and understand it well enough to explain it accurately.


• Hands-on use of AI: real experience using AI assistants for actual work, with a clear sense of what \"skills\"/prompts/context files are and how to build with them.


• Working understanding of project management and workspace tools (Confluence, Jira, Notion, or similar).


• Genuine curiosity about systems and process — an instinct to automate the repeatable parts of a workflow.


• Comfortable with ambiguity and moving quickly.
  

Experience & Qualification

• Around 1–2 years of experience in technical writing, content engineering, developer relations, QA, or a similar technical-adjacent role. Strong internship experience counts.


• Exposure to product development or working alongside a product/engineering team.


• A background in computer science/engineering, or another field (journalism, English, technical support) paired with demonstrated technical comprehension — no specific degree required.
  

Equal Opportunity

Neo is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We encourage applicants from all backgrounds, cultures, and communities to apply and believe that a diverse workforce is key to our success.