Technical Content Writer

CryptoMize; New Delhi; On-site; INR 900,000 - 1,200,000; Full time

Job summary

CryptoMize in Delhi seeks a Technical Content Writer to own the documentation for the intelligence platform stack, including guides, references, and troubleshooting paths used by engineers and operators.

The role involves conducting needs analysis, interviewing users, mapping tasks, and shaping the interface language—labels and error messages—written as craft. Immediate joining and full-time permanent employment offered.

Qualifications

• Ability to write clear, actionable docs for engineers and operators.
• Experience creating user guides, references, and troubleshooting content.
• Proficiency with information architecture and single-sourcing.

Responsibilities

• Own the documentation estate for the intelligence platform stack.
• Conduct needs analysis via interviews and task mapping.
• Own interface language including labels, empty states, and error messages.

Skills

Technical writing

Information architecture

Audience analysis

Interviewing users

Single-sourcing

UI copywriting

Tools

Markdown

Docs pipelines

Mermaid/diagrams

GitHub PRs

Job description

Technical Content Writer jobs in Delhi at CryptoMize are open on a rolling, always-hiring basis — full-time, permanent, with immediate joining. This is the documentation seat for a real platform stack: user guides, online help, developer references and UI text for the intelligence platforms operators work in daily, plus methodology documentation for OSINT and forensics teams. The pipeline is docs-as-code — documentation lives in version control, moves through review like code, and ships on the engineering cadence. If you are a technical writer who wants material that matters and a bar to match, below is the complete job description — responsibilities, requirements, the seniority path, and the selection process.

What you will actually do:

• Own the documentation estate for the intelligence platform stack — guides, references, and troubleshooting paths that engineers and operators actually use
• Run the needs analysis properly: engineer and operator interviews, task mapping, and structures built from how users fail rather than how products are organized
• Own the interface language: labels, empty states, and error messages — the words a system speaks, written as craft

Skills that matter:

Simplifying complex concepts without dumbing them down, Information architecture for documentation sets, Audience analysis, Technical interviewing, Single-sourcing and content reuse discipline, UI microcopy craft.

Tools you will use:

Markdown docs-as-code pipelines, Static-site documentation generators, Mermaid / draw.io-class diagramming, GitHub review workflow for docs pull requests.

Location: New Delhi (HQ), E4, Vasant Vihar. Type: full-time permanent. Availability: immediate, rolling intake. Compensation: discussed at screening.